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

[lilypond]

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

I'm not sure if my replies to previous comments were properly sent... If  
you didn't get them, check issue webpage.

2011/7/11  <address@hidden>:

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

> I agree with James -- why the change?

> I'd like to see an alternate method of working here.  Janek, could you  
> work
> on a framework to easily switch between different scores?  i.e. maybe
> something like
>  \layout { \context Staff
>    \set Font = #'Cheddar
>  }
> ?  The idea is that we'd keep Feta/Parmesan the same, but you could define
> your own font (maybe Oscypek ?)

:D

> and use whatever decisions you wanted to make.

> I think I remember seeing something on -user or -devel about a "modern
> composition font", which would also benefit from this approach.

Yes, this sounds like a good approach.
However i'm afraid that i won't have time in the near future to spend on  
this (tweaking clef code already took too long).  So, there are two  
possibilities for now: either my changes will be applied to the default  
Lily clef (*), or they will be lost (i.e. i'll keep them in my local  
repository and - sadly - not even use them, because maintaining a special  
branch/repositiory just for this purpose will be too confusing).  That's  
why i'm quite determined to get my suggestion accepted as the new default  
clef.

(*) and the current clef will become an extra glyph that can be choosed  
using \override Staff.Clef #'style = #'old or something like that  
(hopefully).

cheers,
Janek