[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
From: |
Trevor Daniels |
Subject: |
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font |
Date: |
Tue, 26 Jul 2011 00:49:19 +0100 |
Comment #26 on issue 1752 by address@hidden: redesigning G
clef in
our Feta font
Can we accept the style override as a temporary solution?
No. Carl has given the reasons.
Sooner or later we'll implement font changing architecture and
we'll then move to the more elegant solution. We can set
ourselves a deadline: with 2.18 the Clef #'style = #old override
will be dropped regardless of whether we'll have font changing
architecture or not. How do you like it?
Not at all.
The G clef font was changed 18 months or so ago by
Carl without all this fuss. There was discussion
about the precise shape and a majority eventually
emerged in favour of one shape. The new font was
then pushed, replacing the old. Simple. Easy
Efficient.
This time we have a clear majority in favour of the
new font so why can you not just push it and let us
all get on with life and other LilyPond issues?
Trevor
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1390 / Virus Database: 1518/3787 - Release Date: 07/25/11
- Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, (continued)
- Re: Issue 1752 in lilypond: redesigning G clef in our Feta font,
Trevor Daniels <=
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/25
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/25
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/25
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/27
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/27