Re: * Unify fetaDynamic and fetaNumber into one fetaText encoding (issue248041)

[Simon Tatham]

Han-Wen Nienhuys <address@hidden> wrote:

> Can you have a look at the latest master?  I changed some conventions;
>  it would be good to adopt them in your font package.
> 
> Basically:
> 
> - Use just 1 design size (20)
> - The font should be called gonville-20.otf (Gonville-20 for family,
> full name, etc.;  I left weight empty)
> - The brace font should be called gonville-brace.otf

I've updated my web site. The new version of Gonville (r8904) uses
the naming convention you describe here.

I've kept all the design sizes for the moment, so that my existing
hacky mechanism for dropping Gonville into earlier versions of
Lilypond continues to work, since I anticipate that people will
continue to use them for a while.

(The new version also has redrawn tails for semiquavers and below,
since several people complained about the previous ones.)

> For handling the text, we may need some additional tweaks, but since
> editing the font name in fontforge drops the LIL* tables, I gave up
> there.

I can arrange to provide the intermediate build products if they're
any help to you: .sfd files, files containing the LIL* table data,
and the Fontforge commands I use to convert those into the output
font files. The build script currently doesn't preserve all of that,
but I could make it do so easily enough. Shout if you'd find that
useful.

If you let me know what if any tweaks are required, I'll probably be
happy to upload another tweaked version to my website.

Cheers,
Simon
-- 
for k in [pow(x,37,0x13AC59F3ECAC3127065A9) for x in [0x195A0BCE1C2F0310B43C,
0x73A0CE584254AB23D5A0, 0x12878657EA814421CC92, 0x7373445BB3DA69996F4A,
0x77A7ED5BC3AA700E80B2, 0xE9C71C94ED87ADCF7367, 0xFE920395F414C1A5DB50]]:
 print "".join([chr(32+3*((k>>x)&1))for x in range(79)]) # <address@hidden>