bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font


From: lilypond
Subject: Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Date: Mon, 25 Jul 2011 20:57:33 +0000


Comment #27 on issue 1752 by address@hidden: redesigning G clef in our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752

How do you like it?

I would never notice the difference between the old and new glyphs.

Adding \override Staff.Clef #'style = xx complicates Lilypond.
An alternate font also adds complication.

Today, if I wanted to, I could   \set Staff.clefGlyph = #"clefs.petrucci.g"
I would support simply adding the glyph with a name that reminds us it is proposed as an improvement, intended to fit well with the rest of the Feta font. Then you could convince people of its worth by making beautiful scores with
  \set Staff.clefGlyph = #"clefs.G_proposed"




reply via email to

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