Open hober opened 4 years ago
This relates to #20 I think. We should really think about what we want the web platform representation of a font to be and how various formats might map to that (and ideally canonicalize along the way).
The API shape has moved away from providing anything but common properties and the full blob. It no longer assumes tables, although properties are described in terms of tables.
@inexorabletash wrote (emphasis mine):
The API shape has moved away from providing anything but common properties and the full blob. It no longer assumes tables, although properties are described in terms of tables.
I think this issue should stay open so long as the API exposes something that client code will assume is parsable as OpenType.
Many MacOS and iOS fonts are not OpenType fonts. Requiring browsers to synthesize fake OpenType font tables for underlying non-OpenType fonts seems unfortunate.