boring-expansion-spec
boring-expansion-spec copied to clipboard
harfbuzz
Better-Engineered Font Formats; Part 1. Boring Expansion
Wasm proposals should probably address https://www.theverge.com/24148033/satya-nadella-microsoft-security-memo
Now that `VARC` table has conditional components, it's desirable to be able to negate an entire `ConditionSet`. My proposal is to make `ConditionSet` a legacy thing, and add `Condition`s that...
The `DMAP` proposal has been around. It's supposed to be a "delta map" on top of `cmap`, such that collections can share `cmap` and encode their differences in a separate...
Is there any interest in supporting font variations in `MATH` table? At high level, I think there are two aspects for font variations regarding `MATH` table: 1. `MATH` in variable...
The `'rvrn'` feature is used for one to one glyph substitution at defined design-space threshold. https://learn.microsoft.com/en-us/typography/opentype/spec/features_pt#tag-rvrn This is only enabling GSUB type 1 lookups. Wouldn't it be useful to to...
If multiple axes have the same `axisTag`, at most one must be non-hidden, and such non-hidden axis must come first. There's no further requirements on the ranges and default values...
As discussed on the MPEG list. I propose bumping the minor version: ``` Type | Name | Description -- | -- | -- uint16 | majorVersion | Major version of...
I think I understand how we got to the current variable composite proposal. Roughly: 1. The variable composites specification extends the current glyf composites mechanism. 2. Leaving variable composites in...
