-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Donnerstag, 18. Dezember 2008 19:37:19 schrieb Han-Wen Nienhuys:
> On Thu, Dec 18, 2008 at 1:14 PM, Reinhold Kainhofer
> <reinh...@kainhofer.com> wrote:
> > Am Donnerstag, 18. Dezember 2008 schrieb Han-Wen Nienhuys:
> >> Can you put your timesig code into a .scm (or .ly) file ?
> >
> > yes and no (i.e. "yes" it should be added to lilypond directly, but "no"
> > not in its current form). Currently it's unfinished (auto-beaming
> > missing) and not really integrated into lilypond. That's why i asked a
> > week ago what would be the best way to add it directly to lilypond:
>
> you could put it in input/ or scm/ and put a note at the top that it
> is just meant for MusicXML2ly.
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?
> In general, mixing languages is not a good idea.
I totally agree. As I said. adding lilypond code in musicxml2ly was just a
workaround for things that were not available in LilyPond itself. I tried to
be as general as possible, so these things can one day (hopefully sooner
rather than later) be moved directly to lilypond.
Cheers,
Reinhold
- --
- ------------------------------------------------------------------
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJV56/TqjEwhXvPN0RAgHOAKDMCg9T0rMEJoxWNsL+g0BQorEt0gCgmbXn
hhLT1qMN9yYj8hjzDgte8CA=
=j/dz
-----END PGP SIGNATURE-----
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
