Re: wrong transposition of horn

[Erik Sandberg]

On Sunday 26 September 2004 11.05, Werner LEMBERG wrote:
> Sigh.  It seems that I'm not able to write what I really want.
> Another try.  I know that I can tune the clefs, but this isn't my
> problem.  Please concentrate on the process of transposing!  All music
> I enter in LilyPond is written as it sounds, including Horn (so I
> basically write Horn in C).  This is fine for the full score, and
> indeed almost all full scores from today are scores in C.  For
> creating the horn parts, I use
>
>   \transpose f c'
>
> to get a horn part in F, and here is the problem: Horn parts converted
> to bass clef are written a fifth higher, but according to the
> classical rules it should be a fourth lower.  My suggested property
> controls \transpose, not the clefs: Notes found in bass clef should be
> transposed an octave down additionally.

I think I now understand what you mean. Am I right if your wish is 
semantically equivalent to telling lilypond to automatically convert all 
occurrences of \clef F to \oldBassClef when transposing?

In this case, I don't agree with you. IMHO it's not a good idea to recycle 
information about clefs between different transpositions of the same music. 
Why don't you use something like this:

sounding = \relative c { c1 | f,1 }

inScore = <<{\clef G s1 \clef F s1 } \sounding >>
inPart = <<{\clef G s1 \oldBassClef s1 } \transpose f c' \sounding >>

(or even better, use \tag somehow)

Erik