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

[lilypond]

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

I'm changing it because it doesn't look good.  There is enough
"not-goodness" that it warrants the change in my opinon.

The notehead seems to be a bit more primary, but it's too simple to be
considered.
So yes, i agree - we should be very careful when changing this glyph.

As we have seen in the discussion on -devel, there are people who
didn't like the current treble clef even before i suggested the
change.
Perhaps they didn't feel like changing it themselves, so they decided
not to make the fuss.

Maybe let's use a solution similar to choosing between one- and
double-lined breve notehead?
(http://lilypond.org/doc/v2.15/Documentation/notation-big-page#durations)

Hmm, i hope that you'll like the updated suggestion better.


I'm not sure if i agree that these should really line up (examine
engraved clefs attached above), but the revised version of my
suggestion partially addresses this.


It is bigger in the new proposal, how do you like it?