Behdad Esfahbod

> In case we need some more flags, which wouldn't surprise me, something like the following could make sense: > > 1. Divide flags in to primary and secondary categories....

Further thoughts / investigation: - TupleVariationStore has an inherent 64kb limit on each glyph's data. Apparently @justvanrossum et al are already hitting that limit in my current design. - ItemVariationStore...

Thanks Skef. I'm not comfortable with that level of bit fiddling. Also, the number of datasets or the number of rows within a dataset of an IVS is its internal...

Here's a new data-structure that is optimized for this use-case. It's similar to ItemVariationStore, but stores deltas for multiple values at the same time (with same major/minor). My proposal is...

Then the design of `VARC` table would be: ``` struct VARC { uint16_t major; uint16_t minor; Offset32To coverage; Offset32To CFF2IndexOf glyphRecords; }; ``` ``` struct VarCompositeGlyphRecord { VarComponentGlyphRecord[] components; };...

> I would say this is still fairly important, especially for characters like punctuation that may occur in either visual order. Not sure this requires more bits, though: my strawman...

> MarkFilteringSets bumped minor GDEF version to 2, IIRC. Yes, because a new field was added to GDEF header. My point was that GSUB/GPOS versions weren't bumped just because of...

A major version bump is heavyhanded here. A minor version bump would not help old clients.

Unless we duplicate all lookup types with new lookup-type numbers...

I expect that we add the flag, and in a few years it can be used widely. That's like pretty much any other "minor" update. This feature mainly applies to...