|
From: | James Lowe |
Subject: | RE: Issue 1752 in lilypond: redesigning G clef in our Feta font |
Date: | Sat, 23 Jul 2011 22:44:59 +0000 |
Hello, ________________________________________ From: address@hidden address@hidden on behalf of address@hidden address@hidden Sent: 23 July 2011 23:38 To: address@hidden Subject: Re: Issue 1752 in lilypond: redesigning G clef in our Feta font Comment #23 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. ----- 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
[Prev in Thread] | Current Thread | [Next in Thread] |