Tal Leming
Tal Leming
> Strongly disagree. It should be {unicodeInt: glyphName}, where unicodeInt could be ncoded as a hex string (plists don't like ints as dict keys after all). Oops, yeah, I had...
I prefer the hexified int.
[Here's the relevant part of the GLIF spec.](http://unifiedfontobject.org/versions/ufo3/glyphs/glif/#unicode) This is refreshing my memory on the development of the `` element… We had a couple of things that we had to...
> If you mean how do determine from a cmap which is the primary unicode, then yes, that can not be done unambiguously. Yes. That's what I mean.
If we structured the plist as `{ name : [hex string, …]}` we could preserve the "primary" indication by saying that the first is the primary. To avoid duplicate code...
> It would be nice if UVS (Unicode Variation Sequences) were supported Do you have any suggestions for how to do this? I don't know much about these.
Could someone open another issue for Unicode Variation Sequence support? I don't want the discussion of that to be hard to find in the future.
> would be very useful to publish, alongside the official specification, a series of "mini-specifications" for the various proposals This is a great idea. My initial idea was "you publish...
I've done a lot of work with using glyph names to indicate feature states and behavior. Pretty much every fancy OpenType font that I've written code for has had a...
> Is it maybe to keep the data there for tools that use it? I think that was more or less my idea. Since any group could be used as...