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

[lilypond]

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



2011/7/25 address@hidden:
> 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"

Ah, i didn't know about this!  Looks like the most elegant and clean  
solution to me.
...However, i was unable to apply this override to a change clef - how it's  
done?

> 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.

No, we already decided that we want it as new default.  Now we're only  
deciding what to do with the old glyph,

>  Then you could convince people of its worth by making beautiful
> scores with
>  \set Staff.clefGlyph = #"clefs.G_proposed"

I don't think this would work.  I had my time for convincing people when we  
discussed new clef shape in thread "font survey: which clef do you prefer?"  
- and i managed to do it :)

cheers,
Janek