[smufl-discuss] Re: SMuFL Metadata generation

[dspreadbury]

Knut wrote:

> The basic part of the font set is laid out more or less according to
> Maestro. However, I’ve attempted to remedy some minor
> inconsistencies in the mapping of Maestro, so a few characters are
> in different places. Some of the Maestro characters have also been
> replaced by different, (in my opinion) more frequently used
> characters. Additionally, I have used the basic type 1 page MacOS
> Roman, and have filled every single code point accessible through
> the standard american keyboard, so there are quite a few extra
> characters compared to the Maestro font.

In that case, I don't think the script we have in mind will necessarily be
of much help. Instead, what I propose is that we make a script that allows
you to add empty glyphs (with appropriate names set in the Note field so
you can tell which is which) at the appropriate code points for each range
defined in the SMuFL specification. You'll be able to uncomment the ranges
that you know you want to populate in your font, and run the script to
create empty glyphs with the right names and code points, so that you can
then copy and paste your existing glyphs into the appropriate place for
SMuFL.

There's no reason I can think of why you shouldn't have the same paths in
multiple glyphs in the font, each with a different code point, so that you
can support each desired use case with a simple OT font; indeed, this is
exactly what Robert's November 2.0 font does.

> Sorry if I seem like a total novice, but where and how exactly do I
> enter the bounding box and anchor values? Directly in a JSON editor?

You don't need to enter anything for the bounding box: that can be derived
automatically by the script. The anchors, however, need to be added
manually: right-click in the glyph window and choose Add Anchor... from
the context menu, then type the appropriate name, and finally drag it into
place. When you run the script to export the metadata, it will go over
each glyph, find the ones that have anchors in them, and export the name
and position of the anchor in the appropriate format in the output JSON.

> I’m assuming the glyph list in the SMuFL documentation pdf is
> compiled using scripts as well? I don’t know if you would be willing
> to share these, but if so, they could be very helpful as well.

Unfortunately it's not easy for us to share any of that, as it's part of a
larger custom toolchain we have built to manage the SMuFL development
process, I'm sorry to say.

Daniel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Steinberg Media Technologies GmbH, Frankenstrasse 18b, D-20097 Hamburg, Germany
Phone: [phone] | Fax: [phone] | www.steinberg.net
President: Andreas Stelling | Managing Director: Hiroshi Sasaki, Hirofumi Osawa
Registration Court: Hamburg HRB 86534
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
#############################################################
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]>