True, but I usually avoid command line stuff. I'm on Windows XP.
Also, I learned a little bit by looking at the code. Not enough to do
anything with it, mind you.
Tim Reeves
Graham Percival <[EMAIL PROTECTED]>
07/09/2008 12:49 PM
To
Tim Reeves <[EMAIL PROTECTED]>, Han-Wen Nienhuys
<[EMAIL PROTECTED]>
cc
lilypond-user@gnu.org
Subject
Re: changelog (was: Arbitrary changes?)
Or you could have done what I suggested to Haipeng, and ran
convert-ly -s --from=2.11.50
to see a list of all these changes. No looking at source code required.
Cheers,
- Graham
On Wed, 9 Jul 2008 10:58:30 -0700
Tim Reeves <[EMAIL PROTECTED]> wrote:
> It took me a couple of minutes to scan through the source code (of
> convert-ly.py) as Han-Wen suggested and find the changes in 2.11.51,
> so as a convenience to others, here they are:
>
> \\octave changed to \\octaveCheck
> arpeggioUp changed to arpeggioArrowUp
> arpeggioDown changed to arpeggioArrowDown
> arpeggioNeutral changed to arpeggioNormal
> setTextCresc changed to crescTextCresc
> setTextDecresc changed to dimTextDecresc
> setTextDecr changed to dimTextDecr
> setTextDim changed to dimTextDim
> setHairpinCresc changed to crescHairpin
> setHairpinDecresc changed to dimHairpin
> sustainUp changed to sustainOff
> sustainDown changed to sustainOn
> sostenutoDown changed to sostenutoOn
> sostenutoUp changed to sostenutoOff
>
> Funny thing is, the only ones I use are the cresc and dim ones, and I
> don't see what was gained by those changes, but no big deal - I'd
> have to look them up the next time used them anyway most likely.
>
>
> Tim Reeves
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
