lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [patch] first-clef property


From: Juergen Reuter
Subject: Re: [patch] first-clef property
Date: Sat, 2 Feb 2008 01:48:19 +0100 (CET)

Hmmh, maybe I do not understand correctly, but wouldn't it be possible to get equivalent behavior with tagged music? I mean, put both \clef commands ('\clef "soprano"' and '\clef "treble"') into the code, put different tags on each of them, and then "turn" them "on/off" or switch between the two editions by filtering the music for the proper tags.

Anyway, wouldn't it be nicer to have some kind of scheme macro that expands to code that prints an incipit? Your "first clef" could then be just part of the incipit that the macro creates. And maybe the clef's name either could passed as argument to the scheme macro. Or, alternatively, you set an, say, "original-clef" property that the macro recognizes and accordingly acts upon.

Greetings,
Juergen

On Fri, 1 Feb 2008, Nicolas Sceaux wrote:

Hi,

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.

I use a customized version of the \clef command, which allows specifying
two clefs, eg. \clef "soprano/treble". If some option is set, it behaves
like \clef "soprano", otherwise it behaves like \clef "treble", except
at the beginning of the first line, where a little soprano clef is
printed before the treble clef. The first-clef property makes it
possible to detect when it is the beginning of the 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... but this patch is very tiny :-)
And I've seen some posts showing interest for this kind of feature.

Nicolas






reply via email to

[Prev in Thread] Current Thread [Next in Thread]