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

[lilypond]

Updates:
        Labels: font

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

2011/7/11  <address@hidden>:

> Comment #13 on issue 1752 by percival.music.ca: redesigning G clef in our
> Feta font
> http://code.google.com/p/lilypond/issues/detail?id=1752

> Unless absolutely every single person prefers the new clef, I have serious
> concerns about changing it.  This sounds like a Critical regression to me.

?!?

> Comment #14 by percival.music.ca:
> wait, let me rephrase that: it wouldn't be a Critical regression because  
> it
> would be a deliberate change.
> However, [...]

Whew.

> Besides, I really think that supporting the old clef would not be a great
> deal of work -- and that work would be beneficial to all future font work.

Ok, i agree that if there will be anyone not satisfied with the change, we  
should make it possible to choose old clef.  Do you think that approach  
similar to choosing between one- and double-lined breve would be  
sufficient? (see  
http://lilypond.org/doc/v2.15/Documentation/notation/writing-rhythms#durations)   
If so, i can investigate it.
Still, i hope that my revised proposal will be accepted by people that  
didn't like the original suggestion; most of them didn't give their  
opinions on the new suggested shape yet.

>  I mean, if you actually made a separate "Oscypek" font, which was  
> optional,
> then I would be 100% comfortable pushing patches from you (to that font)
> completely blindly.  No user discussion, no review, etc.  You could make
> whatever changes to that font you wanted.
> (caveats: I'd need to get agreement from other developers, and your  
> patches
> would still need to compile.  And you might want to survey users anyway.
> But you would be working from a position of strength (i.e. you would have
> the final say about what went into Oscypek), instead of trying to reach
> consensus with everybody for every single change!)

Yes, i thought about this, too.  However, until we encounter a font issue  
that couldn't be agreed upon, i don't think it's needed.  Firtsly, i'm  
happy with the current discussion (and i think that my revised proposal is  
indeed better than the original one - thanks to your feedback!).  Secondly,  
if i see something that is - in my opinion - wrong (i'm not talking about  
personal style preferences), i'd prefer to fix it for everyone, not only  
include an optional switch.
Nevertheless, designing fonts in different styles interests me, so sooner  
or later it will be good to do what you say.

thanks,
Janek