Behdad Esfahbod
Behdad Esfahbod
> In fact, I think this is extremely cumbersome to use. Since the "varied feature" needs to list everything that applies at that point. In other words, the current design...
> * We should probably have clarified whether the location values are designspace or userspace coordinates. :-/ I don't actually know what the answer is to that. userspace I would...
> userspace I would say. `wght=800` etc are userspace values. as in user-facing values.
Doesn't make sense to me without first figuring out governance.
> By far, the biggest hurdle for breaking the 64K glyph limit is in OTL tables: to support 32-bit GIDs in GPOS, GSUB and GDEF would entail a very major...
There's two aspects to nested lookups that need clarification: 1. The `LookupFlags` used. Is clear now. There was a `MicrosoftDocs` issue about it. The nested-lookup's lookup flags shall prevail, 2....
On Sun, Sep 20, 2020 at 9:08 PM Dave Crossland wrote: > In https://lists.aau.at/pipermail/mpeg-otspec/2018-April/000030.html > @behdad wrote, > > What I was hinting at was that maybe we should register...
I disagree and object to this. Legacy APIs should figure out what they do by themselves, not put junk forward into a format that will be carried for decades.
> 1. The Spec to specify that, font API implementations should automatically hide the derived instance or generate a compatible but artificial name for derived instances, if its name does...
A *really* bad case is the `MERG` table because it looks as if it works, but doesn't at all when you account for full complex positioning. It was done hastily,...