Hello, ________________________________________ From: bug-lilypond-bounces+james.lowe=datacore....@gnu.org [bug-lilypond-bounces+james.lowe=datacore....@gnu.org] on behalf of lilyp...@googlecode.com [lilyp...@googlecode.com] Sent: 23 July 2011 23:38 To: bug-lilypond@gnu.org Subject: Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Comment #23 on issue 1752 by carl.d.s...@gmail.com: 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. ----- OK so can't we have another clef in the already extensive glyph list? http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font#clef-glyphs We already have a clefs.G_change why not a 'clefs.G_original' or something else. I (and others) can then use this clef instead of an override. Why is this going to be unmaintainable? James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
