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

[lilypond]

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

> I am *not* in favor of including the clef style override in lilypond --  
> it's a hack
> that is not extensible and not maintainable in the long term.

I agree, though if we must have the option of switching between old & new,  
I think a parser-clef.scm entry would make more sense.