OpenType text shaping engine. There are two code trees in existence today:is an
The old FreeType, Pango, and Qt, is available here. It is not actively developed or maintained, and is extremely buggy. All users are encouraged to switch over to the new as soon as possible. There are no release tarballs of old whatsoever.tree, derived from
For tarball releases of the new here. At the same place you will also find Win32 binary bundles that include libharfbuzz DLL, hb-view.exe, hb-shape.exe, and all dependencies.codebase, look
The API is not expected to change incompatibly, but we cannot guarantee that until1.0.0 is released. Other than that, we consider it very stable, and the API that comes with hb.h is unlikely to change. API in hb-ft.h and other peripheral headers are more likely to through reviews before 1.0.
If you are not sure whether Pango or this.is right for you, read
On Linux, install the development packages for FreeType, Cairo, and GLib. For example, on Ubuntu / Debian, you would do:
- sudo apt-get install gcc g++ libfreetype6-dev libglib2.0-dev libcairo2-dev
whereas on Fedora, RHEL, CentOS, and other Red Hat based systems you would do:
- sudo yum install gcc gcc-c++ freetype-devel glib2-devel cairo-devel
If you are using a tarball, you can now proceed to running configure and make as with any other standard package. That should leave you with a shared library in src/, and a few utility programs including hb-view and hb-shape under util/.
- sudo apt-get install autoconf automake libtool pkg-config ragel gtk-doc-tools
and on Fedora, RHEL, CentOS:
- sudo yum install autoconf automake libtool pkgconfig ragel gtk-doc
To get a better idea of where State of Text Rendering.stands in the text rendering stack you may want to read
Both development and user support discussion around harfbuzz at lists freedesktop org mailing list. Some of the developers frequent the #harfbuzz channel on freenode IRC server. If you write to the mailing list, you are guaranteed to get an answer. The same is not necessarily true about the IRC channel, or if you write to individual developers. Feel free to write to the list to tell us how you are using , or how well it has been suiting your project's needs.happens on the
To report bugs or submit patches, you can either use bugzilla, or the mailing list. Bugzilla is preferred, since we can track the issue until it has been fixed.
For a comparison of old vs new this.memory consumption see
See past and upcoming HarfBuzz Hackfests
You can monitor various aspects of the project using the following online services:
- The code is replicated on GitHub; pull requests are responded to,
- With each commit, all tests are run on Travis CI,
- Public API / ABI changes are tracked across releases on Upstream Tracker,
If your application uses ICU here that uses to provide the ICU API. The C++ API is not ABI compatible, but the C API is. This library has not been tested seriously. If you use it, please report your experience to the mailing list.library, there is a replacement library called icu-le-hb