bfee6839b0
From the commit: + /* For ChainContextFormat2 we cache the LookaheadClassDef instead of InputClassDef. + * The reason is that most heavy fonts want to identify a glyph in context and apply + * a lookup to it. In this scenario, the length of the input sequence is one, whereas + * the lookahead / backtrack are typically longer. The one glyph in input sequence is + * looked-up below and no input glyph is looked up in individual rules, whereas the + * lookahead and backtrack glyphs are tried. Since we match lookahead before backtrack, + * we should cache lookahead. This decisions showed a 20% improvement in shaping of + * the Gulzar font. https://github.com/harfbuzz/harfbuzz/pull/3636 |
||
|---|---|---|
| .ci | ||
| .circleci | ||
| .github/workflows | ||
| docs | ||
| m4 | ||
| perf | ||
| src | ||
| subprojects | ||
| test | ||
| util | ||
| .clang-format | ||
| .codecov.yml | ||
| .editorconfig | ||
| AUTHORS | ||
| BUILD.md | ||
| CMakeLists.txt | ||
| CONFIG.md | ||
| COPYING | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| README.md | ||
| README.mingw.md | ||
| README.python.md | ||
| RELEASING.md | ||
| TESTING.md | ||
| THANKS | ||
| autogen.sh | ||
| configure.ac | ||
| git.mk | ||
| harfbuzz.doap | ||
| meson.build | ||
| meson_options.txt | ||
| mingw-configure.sh | ||
| replace-enum-strings.cmake | ||
README.md
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, LibreOffice, OpenJDK, PlayStation, Qt, XeTeX, 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, though, that document is many years old. 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 my Persian translation of “OpenType”, transliterated using the Latin script. It sports a second meaning, but that ain’t translatable.
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
