> Hello all,
>
> Here is a python script for FontForge to generate the very basic metadata, as discussed earlier.
> (@Laurent: couldn’t wait…;-) )
>
>
http://www.codeshare.io/KWPDG>
> It must be called from the font’s directory but could be easily modified to be invoked from within FontForge.
>
> Robert
Robert,
Thanks for sharing that code! Very concise and gets the job done.
There's only one problem (Daniel, if you could please chime in on
this). The metadata glyph names end up being the _unicode_ names, not
the _human-friendly_ names (like "noteheadBlack").
Is this an issue? I can see developers of notation applications
choosing one over the other, but, since this is about standardizing
things, I think we need to decide which way it's going to be. I guess
it's not important if this script isn't made publicly available.
Otherwise, it needs addressing.
I guess I'm wondering if the glyph names can be the human-friendly
names, since they are already mapped to a unicode character within the
font. Seems redundant to have its name referencing the same unicode
location. Maybe it's just me. Any thoughts?
I have created a small mapping script that addresses this issue. It
converts the unicode glyph names, as found in "Bravura.otf", to the
human-friendly names, like is found in "bravura_metadata.json". It
uses "glyphnames.json" which is graciously provided on the SMuFL site.
The issue here is that it requires the above script to know where it
is located. Easy to do, but for now must be done manually.
Regards,
Abraham
#############################################################
This message is sent to you because you are subscribed to
the mailing list <
[hidden email]>.
To unsubscribe, E-mail to: <
[hidden email]>
To switch to the DIGEST mode, E-mail to <
[hidden email]>
To switch to the INDEX mode, E-mail to <
[hidden email]>
Send administrative queries to <
[hidden email]>
.:| Leigh Verlag |:.
Music Font Design & Engraving