Jany Belluz

Currently there's a hackish way to achieve that (and have the data put into the final fonts by fontmake) by putting Glyphs.app custom parameters in the instance's element (which is...

> I only proposed including them as xml elements because it conceptually fit with the other 5 or so localized name elements I see; in that case I would say...

I do have a feeling that the elided fallback name should be Regular even for the Italic VF, because in the Italic VF, "Italic" is not elidable, and the VF...

As a comment for the meeting, we're still interested in having this, if only for the sake of allowing better roundtrip with glyphsLib when concerned with background layers. In case...

I can think of 2 other use-cases at least for this in glyphsLib, where Glyphs.app has more information about components and guidelines than what fits in standard fields of the...

I started some work in this pull request: https://github.com/unified-font-object/ufo-spec/pull/124

Yes, that sounds like a good idea to separate the two. For example in glyphsLib we're storing open tabs (called "display strings") in a lib key, and that creates some...

Also worth noting: in the plan above, the changes to the UFO format are opt-in, for users who don't care about them, they could not use the new .fea syntax...

I think a naming convention would be good, but I also think that the layer names should not encode information about the contents or the purpose of the layer. I...

I realize that I actually haven't addressed your question of variable color font in my example "ufo-specific" convention. Maybe we could have inside the various `public.variations.wght100` glyphs that represent variations...