* [font] Saturate synthetic bold and glyph origin arithmetic #6154 made hb_position_t arithmetic saturate and #6296 did the same for synthetic_glyph_extents(), but the rest of hb_font_t still used plain signed arithmetic: - changed() computed the embolden strength with abs (x_scale), which overflows for INT32_MIN, and converted the float product to int without a range check. A strength of INT32_MIN could also not be negated later on, for negative scales. - get_font_[hv]_extents(), the advance, origin and contour point getters added the strength with += and could overflow. - add_offset(), subtract_offset() and apply_offset() overflow when they apply a large origin, and so do the origin fallbacks in apply_glyph_[hv]_origins_with_fallback(). - em_multf() converted its float result to hb_position_t without a range check, which is undefined for a value such as an ascender above the em at a scale close to INT32_MAX. Use hb_saturate_add(), hb_saturate_sub() and hb_clamp_to() in these places, and keep the strength away from INT32_MIN so that negating it stays defined. Results that fit do not change. The shift variables that were int are now hb_position_t, since the saturating helpers deduce one type and int32_t is not int everywhere. Tested with test-font under UBSan: the new tests fail on the base commit at hb-font.hh:365, :848, :1154 and :1167, and pass here. Assisted-by: Claude * [test] Cover plural origins and synthetic slant saturation Review feedback: the plural origin getters and the slant clamp in get_glyph_contour_point were not covered by the tests, so removing their saturation would still pass. test_synthetic_bold_saturates now also calls hb_font_get_glyph_h_origins and hb_font_get_glyph_v_origins once each and checks both coordinates for INT32_MAX. A new test_synthetic_slant_saturates sets a slant of 1 on a contour point one short of INT32_MAX in both axes and checks that x saturates to INT32_MAX. Verified by mutation: replacing the plural hb_saturate_add calls with plain addition makes the first test fail (the value wraps), and dropping the hb_clamp_to in the slant path makes the second fail (x comes out as -2). Full meson test -C build: 270 ok, 0 fail, 7 skipped (subset+repack, missing repacker dependency; same as the baseline run for this PR). Assisted-by: Claude * [font] Apply the synthetic slant shift before clamping get_glyph_contour_point clamped the slant shift to hb_position_t before adding it to x. When x and the shift have opposite signs and partly cancel, clamping first changes the result: a contour point at x = -2000000000, y = 2000000000 with a slant of 2 should land at x = 2000000000, but came out as 147483647, because the shift was clamped to INT32_MAX before the addition. Add the shift first and clamp the sum instead. The existing saturation case is unchanged: hb_clamp_to widens to double to do the clamp, so an out-of-range sum still saturates instead of hitting an undefined float-to-int conversion. The new test_synthetic_slant_cancelling covers the cancelling case. Verified by mutation: restoring the clamp-first order makes it fail with 147483647, the reported value. Full meson test -C build: 270 ok, 0 fail, 7 skipped, same as baseline. Assisted-by: Claude
HarfBuzz
HarfBuzz started as a text shaping engine but has grown into a
full font platform — the ffmpeg of text shaping. It primarily
supports OpenType, but also Apple Advanced Typography.
HarfBuzz shapes the majority of text on modern screens.
HarfBuzz is optimized for robustness, correctness, and performance — in that order. Achieve all.
Try it live at harfbuzz-world.cc — an interactive playground for shaping, subsetting, rasterization, vector output, and GPU rendering, all running in your browser.
Here is a quick map of its components:
Core libraries
| Library | Description |
|---|---|
| libharfbuzz | Text shaping, draw API, paint API. Highly configurable (see CONFIG.md). Optional integration backends compiled in: hb-ft (FreeType), hb-coretext (macOS), hb-uniscribe (Windows), hb-directwrite (Windows), hb-gdi (Windows), hb-glib, hb-graphite2. |
| libharfbuzz-subset | Font subsetting and variable-font instancing. |
Auxiliary libraries
| Library | Description |
|---|---|
| libharfbuzz-icu | ICU Unicode integration. |
| libharfbuzz-cairo | Cairo rendering integration. |
| libharfbuzz-gobject | GObject/GI bindings. |
Rendering libraries
| Library | Description |
|---|---|
| libharfbuzz-raster | Glyph rasterization to bitmaps, including color fonts. Uses hb-draw and hb-paint. |
| libharfbuzz-vector | Glyph output to vector formats (currently SVG), including color fonts. Uses hb-draw and hb-paint. |
| libharfbuzz-gpu | Encodes glyph outlines for GPU rasterization (Slug algorithm). Provides shader sources in GLSL, WGSL, MSL, and HLSL. Live demo. |
Notable missing feature: font hinting (including autohinting) is not implemented. For hinted rasterization, use FreeType or Skrifa.
For simplified builds, amalgamated sources are available:
harfbuzz.cc (just libharfbuzz), harfbuzz-subset.cc (just
libharfbuzz-subset), or harfbuzz-world.cc (everything, driven
by a custom hb-features.h). For a live in-browser playground
plus a worked example of the world.cc single-file build, see
harfbuzz-world.cc.
Command-line tools
| Tool | Description |
|---|---|
| hb-shape | Shape text and display glyph output. |
| hb-view | Render shaped text to an image. |
| hb-subset | Subset and optimize fonts. |
| hb-info | Display font metadata. |
| hb-raster | Render glyphs to bitmap images. |
| hb-vector | Render glyphs to vector formats (SVG). |
| hb-gpu | Interactive GPU text rendering. |
The canonical source tree and bug trackers are available on github. Both development and user support discussion around HarfBuzz happen on github as well.
For license information, see COPYING.
API stability
The API that comes with hb.h will not change incompatibly. Other, peripheral,
headers are more likely to go through minor modifications, but again, we do our
best to never change API in an incompatible way. We will never break the ABI.
The API and ABI are stable even across major version number jumps. In fact, current HarfBuzz is API/ABI compatible all the way back to the 0.9.x series. If one day we need to break the API/ABI, that would be called a new library.
As such, we bump the major version number only when we add major new features, the minor version when there is new API, and the micro version when there are bug fixes.
Documentation
For user manual as well as API documentation, check: https://harfbuzz.github.io
Download
Tarball releases and Win32/Win64 binary bundles are available on the github releases page.
Development
For build information, see BUILD.md.
For custom configurations, see CONFIG.md.
For testing and profiling, see TESTING.md.
For using with Python, see README.python.md. There is also uharfbuzz.
For cross-compiling to Windows from Linux or macOS, see README.mingw.md.
To report bugs or submit patches please use github issues and pull-requests.
Developer documents
To get a better idea of where HarfBuzz stands in the text rendering stack you may want to read State of Text Rendering 2024. Here are a few presentation slides about HarfBuzz over the years:
- 2026 – HarfBuzz at 20!
- 2016 – Ten Years of HarfBuzz
- 2014 – Unicode, OpenType, and HarfBuzz: Closing the Circle
- 2012 – HarfBuzz, The Free and Open Text Shaping Engine
- 2009 – HarfBuzz: the Free and Open Shaping Engine
More presentations and papers are available on behdad's website. In particular, the following studies are relevant to HarfBuzz development:
- 2025 – AAT layout caches
- 2025 – OpenType Layout lookup caches
- 2025 – Introducing HarfRust
- 2025 – Subsetting
- 2025 – Caching
- 2025 –
hb-decycler - 2022 –
hb-iter - 2022 – A C library written in C++
- 2022 – The case of the slow
hb-ft>h_advancefunction - 2022 – PackTab: A static integer table packer
- 2020 – HarfBuzz OT+AAT "Unishaper"
- 2014 – Building the Indic Shaper
- 2012 – Memory Consumption
Name
HarfBuzz /hærfˈbɒːz/
From Persian حرف (Harf: letter) and باز (Buzz: open). Transliteration of the Persian calque for OpenType.
As a noun: The Open Source text shaping engine.
As an adjective: Insincerely talkative; glib. A nod to the GNOME project where HarfBuzz originates from.
The logo shows حرفباز in the IranNastaliq font, on a Damascus steel background.
Background: Originally there was this font format called TrueType. People and companies started calling their type engines all things ending in Type: FreeType, CoolType, ClearType, etc. And then came OpenType, which is the successor of TrueType. So, for my OpenType implementation, I decided to stick with the concept but use the Persian translation. Which is fitting given that Persian is written in the Arabic script, and OpenType is an extension of TrueType that adds support for complex script rendering, and HarfBuzz is an implementation of OpenType text shaping.
Users
HarfBuzz is used in Android, Chrome, ChromeOS, Firefox, Flutter, GNOME, GTK+, KDE, Qt, LibreOffice, OpenJDK, XeTeX, Adobe Photoshop, Illustrator, InDesign, Microsoft Edge, Amazon Kindle, PlayStation, Godot Engine, Unreal Engine, Figma, Canva, QuarkXPress, Scribus, smart TVs, car displays, and many other places.
