On Sun, Dec 28, 2008 at 1:43 PM, Reinhold Kainhofer <reinh...@kainhofer.com> wrote:
> Actually, those definitions are not only meant for musicxml2ly. They do not > depend on anything MusicXML-specific, but rather implement features that are > available in MusicXML, but not yet in LilyPond. They are candidates for future > inclusion into lilypond. In particular, I currently have the following > features implemented, which are not included in lilypond itself: > > - -) \eyeglasses markup: > http://lsr.dsi.unimi.it/LSR/Item?id=435 > - -) \snappizzicato markup (Bartók pizzicato, should actually be an > articulation): > http://lsr.dsi.unimi.it/LSR/Item?id=335 > - -) Tuplet numbers including note durations: > http://lsr.dsi.unimi.it/LSR/Item?id=482 > This code was extended to allow different fractions to be displayed (e.g. > display 7:5 even for \times 6/4) > See the file 23c-Tuplet-Display-NonStandard.xml of the MusicXML test suite: > http://lilypond.org/doc/v2.12/input/regression/musicxml/collated-files > - -) Complex compound time signatures (they take up most of the code). > > > Ideally, all of them would be implemented directly in stock lilypond. Do you > think that any of these should be moved to lilypond's .scm files? I think all of them could be inside lilypond. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
