On Fri, Oct 31, 2008 at 8:57 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>
> > If noone objects, I'm going to fix this so that we have something
> > sane.
>
> This is fixed now.
>
Hi Werner,
The fingerings were in fact Artur Schabel's from his complete edition of the
Beethoven piano sonatas (p
On Tue, Sep 30, 2008 at 8:19 PM, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Given the problems with the current GUI shell and python
> incompatibilities on macos, I think it makes sense to rebuild the
> shell using python 2.4, and as a fat binary. Then the installer will
> include its own python
Look good, just one nitpick.
http://codereview.appspot.com/4848/diff/806/615
File lily/page-breaking.cc (right):
http://codereview.appspot.com/4848/diff/806/615#newcode227
Line 227: ly_symbol2scm ("is-part-last"), scm_from_bool (last),
A really minor naming nitpick, but you have is-last and is-
On 2008/11/03 00:36 +0100, Valentin Villenave wrote:
> having the snippet's translations in a different place than the actual
> snippets is really a PITA, especially when it comes to updating both
> the descriptions and the source code.
Agreed.
> Do you know if the LSR interface
> could accept
2008/11/3 John Mandereau <[EMAIL PROTECTED]>:
> Werner, we should junk input/new/revised ASAP: as Neil and Valentin
> already explained, if you want a snippet to be added to LSR, please
> write it in input/new and ask us to update LSR.
John, if I may,
having the snippet's translations in a diffe
On 2008/11/02 22:36 +, Neil Puttock wrote:
> 2008/11/2 Werner LEMBERG <[EMAIL PROTECTED]>:
>
> > OK. Yes, John, I want a space :-)
>
> Hehe, I've just had a look at makelsr.py, and it just needs an extra `\n'. :)
Ah, I wondered why the mao you wanted an extra space and not a blank
line :-P
2008/11/2 Werner LEMBERG <[EMAIL PROTECTED]>:
> OK. Yes, John, I want a space :-)
Hehe, I've just had a look at makelsr.py, and it just needs an extra `\n'. :)
Before I push this change, are there any other formatting aspects
which you don't like?
Cheers,
Neil
___
> The LSR database tarball is only updated once a day, so the changes
> will appear in the next update; texidoc and input/new alterations are
> effective immediately.
OK.
> BTW, if you want a space after %begin verbatim, you'll have to ask
> John to alter makelsr.py, since the formatting is auto
2008/11/2 Werner LEMBERG <[EMAIL PROTECTED]>:
> OK. Thanks for updating the LSR snippets; however, you've missed a
> bunch of changes to the lilypond code in the snippets themselves --
> I've mainly edited the files to reduce the widths. Please recheck.
The LSR database tarball is only updated
> Werner, as Valentin says, it would be much easier if you send changes
> directly to us. In the case of translated texidocs, you can amend
> them yourself, since they live in input/texidocs.
OK. Thanks for updating the LSR snippets; however, you've missed a
bunch of changes to the lilypond cod
Trevor Daniels schrieb:
Eyolf
More comments on Ancient now seem unlikely. T
Oops, I totally forgot about it. I would like to review this, but I am
not really fast at the moment. I might just start next week, or would it
be better to wait for the next version?
Greetings
Till
__
On 11/2/08 11:08 AM, "Neil Puttock" <[EMAIL PROTECTED]> wrote:
> 2008/11/2 Trevor Daniels <[EMAIL PROTECTED]>:
>
> Weirdly, defining-predefined-fretboards-for-other-instruments.ly has
> gone awol, so I've had to add it to input/new again.
That's my fault. My git repository got messed up some
2008/11/2 Neil Puttock <[EMAIL PROTECTED]>:
> Nearly there, once I've fathomed out Werner's changes.
Thanks for handling it; I have hardly any time since I'm LilyPonding
my full score (I've merely enough time to check the mailing list while
compiling :-)
Cheers,
Valentin
__
2008/11/2 Trevor Daniels <[EMAIL PROTECTED]>:
>
> Neil, you wrote Sunday, November 02, 2008 2:33 PM
>
>> If you add a file to input/new, you must wait for an LSR update before
>> referencing the snippet in the docs, since @lilypondfile looks in
>> input/lsr for the generated file.
>
> Sorry Neil -
2008/11/2 Neil Puttock <[EMAIL PROTECTED]>:
> I think we're witnessing the first stages of LSR anarchy. :)
I believe this particular kind of anarchy is called "free software" :-)
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Neil, you wrote Sunday, November 02, 2008 2:33 PM
If you add a file to input/new, you must wait for an LSR update before
referencing the snippet in the docs, since @lilypondfile looks in
input/lsr for the generated file.
Sorry Neil - mea culpa. I knew what I should do, and placed the
@lilyp
2008/11/2 Valentin Villenave <[EMAIL PROTECTED]>:
> 2008/11/2 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> I hope this is OK with you; I don't have time to add the stuff by
>> myself to the LSR.
>
> ... or you can send Neil or me a mail ;-)
I think we're witnessing the first stages of LSR anarchy. :)
Hi guys,
If you add a file to input/new, you must wait for an LSR update before
referencing the snippet in the docs, since @lilypondfile looks in
input/lsr for the generated file.
I'm happy to do an update whenever required; just let me know when you
want one. :)
Carl:
If you want to thank a us
2008/11/2 Werner LEMBERG <[EMAIL PROTECTED]>:
> I hope this is OK with you; I don't have time to add the stuff by
> myself to the LSR.
... or you can send Neil or me a mail ;-)
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
h
Folks,
I've created a new directory `input/new/revised' which holds revised LSR
snippets, and which should be added to the LSR so that they get
re-imported. Currently, it contains six snippets with some added
German translations; they have been trimmed horizontally to fit into
the PDF page widt
20 matches
Mail list logo
