Behdad Esfahbod
Behdad Esfahbod
I think this is stepping into the internals of ItemVariationStore again. I like separation of concerns.
I suggest you keep optimization ideas out of the spec. They don't belong here.
`glyf` table version is stored in the `head` table.
Basically `head.glyphDataFormat` is the `glyf` table version.
> aha! So no issues with backwards compatibility that you are aware of? The `avar2` and `glyf1` proposals should not have any back-compat issue. The beyond-64k proposal is a bit...
cc @lorp
``` struct GenerailzedRegion { Array15Of= 1; }; struct Base { uint8 version; F2DOT14 peakCoord; F2DOT14 startCoord; // only if version >= 1 F2DOT14 endCoord; // only if version >= 1...
All new offsets are based off their own start address.
> If the high bit of `regionCount` is set, the current `VariationRegionList` is followed by: > > ``` > Array16Of > ``` The indices looked up in this array are...
> struct Base { > uint8 version; > F2DOT14 peakCoord; > F2DOT14 startCoord; // only if version >= 1 > F2DOT14 endCoord; // only if version >= 1 > uint8...