Thomas wrote:
> The question is: Should there be a way to supply name, description
> and class information for non-standard glyphs in a fashion similar to
> classes.json and glyphnames.json? I think that especially class
> information would be beneficial so that applications can find out
> which glyphs can be used in which role.
>
> ...
>
> Would this be a sensible addition to the metadata file?
Yes, it seems like an eminently sensible addition to me. I will draft up
some details in the next revision to the SMuFL specification.
Daniel
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Steinberg Media Technologies GmbH, Frankenstrasse 18b, D-20097 Hamburg, Germany
Phone: +49 (40) 21035-0 | Fax: +49 (40) 21035-300 | 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]>
Locked
