| commit | 4cfc6d8e173e800df086d7be078da2e8c5cfca19 | [log] [tgz] |
|---|---|---|
| author | Ben Wagner <bungeman@chromium.org> | Thu Aug 31 13:54:34 2023 -0400 |
| committer | Behdad Esfahbod <behdad@behdad.org> | Thu Aug 31 22:49:42 2023 +0300 |
| tree | 053b8d847843563cf33b3fbe80e89450776fef06 | |
| parent | 4668b43e2cbc9d2ae19a9e9b53ad694da35240a1 [diff] |
Specify tuple_variations_t special member functions Building with clang complains about the use of `tuple_variations_t`'s implicit copy constructor and copy assignment operator, since automatic generation of these is deprecated when declaring a non-default destructor. This is a good warning because it isn't obvious that copies were being made instead of the object being moved and this struct should be moved and not copied. Declare all the special member functions, defaulting the moves and deleting the copies. After making `tuple_variations_t` move only, an issue is revealed in `hb_vector_t::push` which has been requiring that objects be copyable. Remove the old non-emplacing `push` now that this works with all existing objects and make a single `push` which is more like `std::vector::emplace_back` since that is somewhat what the newer `push` is attempting to do.
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, Photoshop, Illustrator, InDesign, and other places.
For bug reports, mailing list, and other information please visit:
For license information, see COPYING.
For user manual as well as API documentation, check: https://harfbuzz.github.io
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.
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:
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.
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.
