lilypond-devel
[Top][All Lists]
Advanced

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

Re: varC clefs in 2.19


From: James
Subject: Re: varC clefs in 2.19
Date: Fri, 30 May 2014 10:26:56 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

On 30/05/14 10:24, James wrote:
On 29/05/14 23:11, address@hidden wrote:
I was just looking over the "changes" page for the current development version (2.19.x) and the section with the new clef glyphs caught my eye. The example given for; \clef "varC" *seems* to be alto clef only.

Yes that seems right from the file changes.

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=476c0adbf748f1adcb6927a6197d13f3790c8a9b

scm/parser-clef.scm is the file that (I think) determines the position.


This clef in any position is a 'C' clef as it marks middle C. I'm sure it must be possible to redefine the clef's position somehow, but this strikes me as an oversight, especially with all the other clef transpositions which are readily available.
Seems to be a documentation oversight actually if you look at the diff for the file parser-clef.scm there _is_ a tenor version.

I'm not a programmer, but I seem to remember trying to document these other clefs in that are in this file more coherently in, say, the appendix. I just never got fully around to it.

However can you see if this 'tenor' version is what you wanted?

James

Sorry for replying to my own post. I forget sometimes that not everyone necessarily reads the code or cares about looking in the code tree in git

Assuming you can understand these files I am referring to then it should be obvious, but just in case (and so I apologize if I am patronizing you) you should be able to use

\clef "tenorvarC"

James



reply via email to

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