On Wed, May 13, 2009 at 7:40 AM, Mats Bengtsson <mats.bengts...@ee.kth.se> wrote: > Quoting "Carl D. Sorensen" <c_soren...@byu.edu>: > >> >> >> >> On 5/12/09 11:14 PM, "Andrew Hawryluk" <ahawry...@gmail.com> wrote: >> >>> I think I have figured out issue 708: >>> http://code.google.com/p/lilypond/issues/detail?id=708 >>> Before I submit a patch, how do I decide which LP version this goes >>> under for convert-ly? >> >> You will want to see where the keySignature syntax changed. > > No it's not that simple. The solution proposed in the bug tracker is really > only relevant for scores older than version 2.0 (I haven't checked exactly > which 1.9 version the change happened), when the internal representation for > accidentals changed to be able to handle quarter tones. In version 1.8 and > earlier, the alteration +1 meant sharp and -1 meant flat, whereas from > version 2.0 to version 2.10, +1 meant semi-sharp, +2 meant sharp, -2 meant > flat and so on. ... > However, in version 2.11.6, the next change happened to the internal > representation of alterations. From then, a sharp is represented by +1/2, a > flat by -1/2 and so on. For all the people who had already used the macros > SHARP, FLAT, DOUBLE-FLAT and so on, this didn't cause any problems, but for > those who had kept the numeric representation, you all of a sudden end up > with a "missing glyph" error if you for example specify +2 or -2.
Excellent. Thanks for the helpful background! I can piece together the rest of the info I need from convertrules.py. Andrew _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
