Laurence Penney

I think this is covered by the note in the [Amstelvar documentation](https://github.com/TypeNetwork/fb-Amstelvar/tree/master/documentation): “Axes with collections of extreme deltas often create wild contours as the deltas add up in ways not...

> The Google decoder implementation just ignores the fields: That’s a shame and means the fields are useless. In principle, unknown major version fields should always fail, shouldn’t they?

Note that there is acceptance of the need to be able to express ["immediately after N" or "immediately before N"](https://github.com/fonttools/fonttools/issues/3168#issuecomment-1610148086), meaning the value (in normalised coordinates) 1/16384 more or less...

> Btw. I don't think we need this idea for _output_ locations. Output locations don't need to be unique, only input locations. In the example above (which "pins" a particular...

I’m happy to restrict it to -1 and 1 for now. If there’s a compelling use case for specifying normalized values, we can open it up.

In [OpenType Feature File Specification Additions for Variable Values: Public Review](https://github.com/adobe-type-tools/feature_file_change_review/?tab=readme-ov-file) Adobe uses the concise suffixes "+" and "-" to indicate the smallest possible value above and below. > When...

Technically, the VariationStore structure has a field `length` of type uint16 (rather than the VariationStore itself being uint16).

Thanks for this. I’ll make it wider right away. The reason it is an \ is that it’s an easy way to handle long fields via h-scroll. A \ can...

Hey, this is an old screenshot. I actually fixed this on May 21 5254adba8850ef8925314c242a26c06a951aacbd

Let me know if a) is still important.