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

[Graham Percival]

On Sun, Jul 24, 2011 at 11:43:02PM +0000, address@hidden wrote:
> 
> >However, I am aghast that the "font switching architecture" is going
> >nowhere.  As far as I understand it,
> >  1. we can switch to a different OTF font.  (aka "gonville")
> 
> Everything that i see on this topic is here
> http://lilypond.org/doc/v2.14/Documentation/notation/replacing-the-notation-font.html
> and it seems like an ugly hack...  I wouldn't call that "we support
> choosing different fonts".

Look at
  Documentation/included/gonville.ly
and tell how #(add-music-fonts ...)  fails to be "we support
choosing different fonts".

> >In order to address the difference of opinion, we have two proposals.  The
> >first is to allow an override to switch the glyphs.  Trevor is strongly
> >against it; it would lead to a multiplicity of overrides.  The
> >second is to
> >create a new font with the new glyph.
> 
> Is it worth it?  I mean, that would be the biggest code duplication
> i've ever imagined - to have two fonts that differ with one glyph
> only!

I'm not talking about that.  I'm talking about letting James make
his own copy of the feta font, sticking it on a website like
gonville, and installing it himself on his computer.

I doubt that he'll go to that bother, because that would be silly
just for one glyph -- but the point is that we would give him (or
other users) the *ability* to do this.  Once that's done, it'll be
much easier for people to use whatever version of the font they
want, or even combine different versions of fonts or something,
and happiness will increase.

> >Absent the new architecture, my recommendation is to wait on this patch
> >until 2.16 is out, and then apply the patch *without* the override
> >capability to 2.17.

I'm not convinced we need to wait.

> (obviously) I don't like this solution because it makes my work lie
> on a shelf for a few months and do nothing but collect dust.
> 
> Can we accept the style override as a temporary solution?

No.

> Sooner or later we'll implement font changing architecture and
> we'll then move to the more elegant solution.

I have yet to hear somebody look gonville support and give me a
convincing reason why it doesn't support metafont as well as otf.
Until somebody spends 30 minutes looking at this, I see no reason
to fuss about a patch collecting dust.

Cheers,
- Graham