#18278 closed enhancement (fixed)
harfbuzz-8.0.1
Reported by: | Bruce Dubbs | Owned by: | Bruce Dubbs |
---|---|---|---|
Priority: | normal | Milestone: | 12.0 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New major version.
Change History (7)
comment:1 by , 21 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 21 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
follow-up: 4 comment:3 by , 21 months ago
Summary: | harfbuzz-8.0.0 → harfbuzz-8.0.1 |
---|
Overview of changes leading to 8.0.1 Wednesday, July 12, 2023
- Build fix on 32-bit arm.
- More speed optimizations:
- 60% speedup in retaingids subsetting SourceHanSans-VF.
- 38% speed up in subsetting (beyond-64k) mega-merged Noto.
- 16% speed up in retain-gid (used for IFT) subsetting of NotoSansCJKkr.
Overview of changes leading to 8.0.0 Sunday, July 9, 2023
- New, experimental, WebAssembly (WASM) shaper, that provides greater flexibility over OpenType/AAT/Graphite shaping, using WebAssembly embedded inside the font file. Currently WASM shaper is disabled by default and needs to be enabled at build time. For details, see:
https://github.com/harfbuzz/harfbuzz/blob/main/docs/wasm-shaper.md
For example fonts making use of the WASM shaper, see:
- Improvements to Experimental features introduced in earlier releases:
- Support for subsetting beyond-64k and VarComposites fonts.
- Support for instancing variable fonts with cubic “glyf” table.
- Many big speed optimizations:
- Up to 89% speedup loading variable fonts for shaping.
- Up to 88% speedup in small subsets of large (eg. CJK) fonts (both TTF and OTF), essential for Incremental Font Transfer (IFT).
- Over 50% speedup in loading Roboto font for shaping.
- Up to 40% speed up in loading (sanitizing) complex fonts.
- 30% speed up in shaping Gulzar font.
- Over 25% speedup in glyph loading Roboto font.
- 10% speed up loading glyph shapes in VarComposite Hangul font.
- hb-hashmap optimizations & hashing improvements.
- New macro HB_ALWAYS_INLINE. HarfBuzz now inlines functions more aggressively, which results in some speedup at the expense of bigger code size. To disable this feature define the macro to just inline.
- New API:
+HB_CODEPOINT_INVALID +hb_ot_layout_get_baseline2() +hb_ot_layout_get_baseline_with_fallback2() +hb_ot_layout_get_font_extents() +hb_ot_layout_get_font_extents2() +hb_subset_input_set_axis_range()
follow-up: 5 comment:4 by , 21 months ago
Replying to Xi Ruoyao:
Overview of changes leading to 8.0.0 Sunday, July 9, 2023
- New, experimental, WebAssembly (WASM) shaper, that provides greater flexibility over OpenType/AAT/Graphite shaping, using WebAssembly embedded inside the font file. Currently WASM shaper is disabled by default and needs to be enabled at build time. For details, see:
https://github.com/harfbuzz/harfbuzz/blob/main/docs/wasm-shaper.md
For example fonts making use of the WASM shaper, see:
Thanks for documenting this and the other changes.
From that wasm-examples site this appears to be primarily for Urdu Nastaliq, but also usable for egyptian hieroglyphics and perhaps, based on the example fonts) Devanagari.
However, the README.md file says: "The Harfbuzz WASM shaper is an experimental technology. Feel free to play with it, but don't expect to use it in your fonts any time in the next few years..."
follow-up: 6 comment:5 by , 21 months ago
Replying to ken@…:
Replying to Xi Ruoyao:
Overview of changes leading to 8.0.0 Sunday, July 9, 2023
- New, experimental, WebAssembly (WASM) shaper, that provides greater flexibility over OpenType/AAT/Graphite shaping, using WebAssembly embedded inside the font file. Currently WASM shaper is disabled by default and needs to be enabled at build time. For details, see:
https://github.com/harfbuzz/harfbuzz/blob/main/docs/wasm-shaper.md
For example fonts making use of the WASM shaper, see:
Thanks for documenting this and the other changes.
From that wasm-examples site this appears to be primarily for Urdu Nastaliq, but also usable for egyptian hieroglyphics and perhaps, based on the example fonts) Devanagari.
However, the README.md file says: "The Harfbuzz WASM shaper is an experimental technology. Feel free to play with it, but don't expect to use it in your fonts any time in the next few years..."
It is disabled by default anyway. Does it need some external dependency?
comment:6 by , 21 months ago
Replying to Xi Ruoyao:
Replying to ken@…:
Replying to Xi Ruoyao:
Overview of changes leading to 8.0.0 Sunday, July 9, 2023
- New, experimental, WebAssembly (WASM) shaper, that provides greater flexibility over OpenType/AAT/Graphite shaping, using WebAssembly embedded inside the font file. Currently WASM shaper is disabled by default and needs to be enabled at build time. For details, see:
https://github.com/harfbuzz/harfbuzz/blob/main/docs/wasm-shaper.md
For example fonts making use of the WASM shaper, see:
Thanks for documenting this and the other changes.
From that wasm-examples site this appears to be primarily for Urdu Nastaliq, but also usable for egyptian hieroglyphics and perhaps, based on the example fonts) Devanagari.
However, the README.md file says: "The Harfbuzz WASM shaper is an experimental technology. Feel free to play with it, but don't expect to use it in your fonts any time in the next few years..."
It is disabled by default anyway. Does it need some external dependency?
It needs wasm-micro-runtime, I've added the external dependency into the book.
Updated at commits