a7d7715f10
This should get the features on a shape plan after executing it. Initially I wanted to return an array of tags, but then there can be user features that are not enabled globally, so I thought returning hb_feature_t with value and range would be better. There is a TODO since I couldn’t figure out how to get the value and range from the feature mask. But also it may be overkill and a simple boolean indicating wither it is a global feature or not would be enough. I wounder also what should happen to non-user features that are applied selectively, like init or medi, does ot make sense to indicate whether they are global or not? This is inspired by the discussion in: https://github.com/fontforge/fontforge/pull/5522#pullrequestreview-2574321449, but it might be useful to other HarfBuzz users. |
||
|---|---|---|
| .ci | ||
| .circleci | ||
| .github | ||
| docs | ||
| perf | ||
| src | ||
| subprojects | ||
| test | ||
| util | ||
| .clang-format | ||
| .codecov.yml | ||
| .editorconfig | ||
| AUTHORS | ||
| BUILD.md | ||
| CMakeLists.txt | ||
| CONFIG.md | ||
| COPYING | ||
| harfbuzz.doap | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| README.md | ||
| README.python.md | ||
| RELEASING.md | ||
| replace-enum-strings.cmake | ||
| SECURITY.md | ||
| TESTING.md | ||
| THANKS | ||
| xkcd.png | ||
HarfBuzz
HarfBuzz is a text shaping engine. It primarily supports OpenType, but also Apple Advanced Typography. HarfBuzz is used in Android, Chrome, ChromeOS, Firefox, GNOME, GTK+, KDE, Qt, LibreOffice, OpenJDK, XeTeX, PlayStation, Microsoft Edge, Adobe Photoshop, Illustrator, InDesign, Godot Engine, Unreal Engine, and other places.
For bug reports, mailing list, and other information please visit:
For license information, see COPYING.
Documentation
For user manual as well as API documentation, check: https://harfbuzz.github.io
Download
For tarball releases of HarfBuzz, look here. At the same place you
will also find Win32/Win64 binary bundles that include libharfbuzz DLL,
hb-view.exe, hb-shape.exe, and all dependencies.
The canonical source tree is available on github.
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.
If you are not sure whether Pango or HarfBuzz is right for you, read Pango vs HarfBuzz.
Development
For build information, see BUILD.md.
For custom configurations, see CONFIG.md.
For testing and profiling, see TESTING.md.
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 at the Internationalization and Unicode Conference over the years:
- November 2014, Unicode, OpenType, and HarfBuzz: Closing the Circle,
- October 2012, HarfBuzz, The Free and Open Text Shaping Engine,
- October 2009, HarfBuzz: the Free and Open Shaping Engine.
Both development and user support discussion around HarfBuzz happens on the github.
To report bugs or submit patches please use github issues and pull-requests.
For a comparison of old vs new HarfBuzz memory consumption see this.
Name
HarfBuzz (حرفباز) is the literal Persian translation of “OpenType”, transliterated using the Latin script. It also means "talkative" or "glib" (also a nod to the GNOME project where HarfBuzz originates from).
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 complex text shaping.
Packaging status of HarfBuzz
