Behdad Esfahbod
Behdad Esfahbod
> To help those familiar with VarFonts1.0 to understand VarFonts2.0, we should be explicit that the Default instance (all axes at normalized 0), in general: > > * requires variation...
> I have not jumped that ship yet. My stance so far is that: font designer is responsible to make sure default instance is identical to shapes in `glyf` table....
> Note that VarFonts1.0 tried enforcing this by saying peakCoord cannot be 0. However, it failed. Because if a deltaSet has no active coord, then its scalar becomes 1.0 and...
> Default instance (all axes at normalized 0), in general: > > * requires variation processing I'm leaning towards declaring that if a font has avar2 we must process variations...
I've moved the VarFonts2.0 model discussion to https://github.com/be-fonts/boring-expansion-spec/issues/43.
In the beyond-64k work I'm removing lsb from hmtx entries for glyphs beyond 64k.
> https://typo.social/@justvanrossum/109805730176978858 URL doesn't work. Is there a typo there?
To be done after LookupFlag extension https://github.com/be-fonts/boring-expansion-spec/issues/26. Allocate two bits from LookupFlag extension (leave the existing OpenType free LookupFlags intact). The two new bits will be: * `UseGlyphSkipSet` * `UseGlyphStopSet`...
cc @mhosken @jfkthame