-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Freitag, 1. Februar 2008 schrieb Nicolas Sceaux:
> When typesetting ancient music, one may want to produce two editions:
> eventually one with original clefs, as found in the manuscripts, and an
> other one with new fashioned clefs. It is also custom in the later case
> to print first the ancient clef (which bears some extra meaning, for
> instance which particular instrument should play that part), then the
> modern one, at the beginning of a piece.
>
> The attached patch adds this first-clef grob property. May I apply it?
> I understand that it may not be preferable to add code that presumably
> would be useful to a single person... 

Actually, we're already two ;-) 
I'm transcribing some old pieces by Schubert, who wrote the vocal voices using 
soprano/alto/tenor clef, while modern typesetting practice uses only the 
treble clef for these voices. Now, I want to make two editions, one with the 
original clefs, the other with modern clefs (but the original clefs as 
incipits). So, you see, I'm having exactly the same problem.

I thought about using tags, but that's really messy and prone to breaking 
(since there is no "else" part in the tag, so you can either remove one part 
or not remove it, but not have something else instead).

Cheers,
Reinhold


- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHpJ7vTqjEwhXvPN0RAuewAJ0Y4f2IWjCo/wk5AZJFPB+bYy0+kQCfVgbQ
36Bl5xldpbnJxEtiHWMBzRQ=
=ycK8
-----END PGP SIGNATURE-----


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to