Ben Kiel
Ben Kiel
That sounds/seems fine. I would venture to guess that the last item (Trailing periods and spaces) may be a breaking change. For the `(` & `)` rule; I'm not sure...
(@madig I'm assuming you may PR this change?)
That PR looks good to merge, but I'll let others chime in there. Thank you for doing the spec update!
Agreed on closing the previous issue and starting a focused discussion, this has been dragging out too long (I know I am guilty here). I believe one thought was to...
@typoman it's not neutral when the kerning is stored as writing direction, it leads to abiguity (for example see [this comment](https://github.com/unified-font-object/ufo-spec/issues/16#issuecomment-493050133)). Trust me, I used to think that storing kerning...
And, to be very clear, any change to how kerning is encoded would mean a new file, like `hkerning.plist`, so the two would not be mixed.
It's a given that UFO is a source format, not a binary format. It allows a bunch of things that aren't valid in font binaries (floats in glyph coordinates, identifiers,...
I wanted to fill in the context of why the Adobe FEA syntax was chosen 16 years ago. At the time there wasn't a fully featured, documented, feature syntax that...
See context here: https://github.com/unified-font-object/ufo-spec/issues/115
I'm going to open this again as a thing to _possibly_ consider for UFO4, but here is my current thinking on this: For this kind of thing, having a `contour.lib`...