harfbuzz-ng
Folders and files
Name | Name | Last commit date | ||
---|---|---|---|---|
parent directory.. | ||||
Name: harfbuzz-ng Short Name: harfbuzz-ng URL: http://harfbuzz.org Version: 2.6.4-739 CPEPrefix: cpe:/a:harfbuzz_project:harfbuzz:2.6.4 Date: 20200407 Revision: 0d5695983e8bf3184ecd4cb92f737b9dfe5d6d25 Security Critical: yes License: MIT License File: src/COPYING Description: This is harfbuzz-ng, a new implementation of harfbuzz with a different API from the old one. This copy of harfbuzz is usually updated by running $ third_party/harfbuzz-ng/roll-harfbuzz.sh from your Chromium ./src directory. This should update your checkout by putting the new upstream HarfBuzz ToT commit hash top level DEPS file. In cases added or deleted files have been detected in HarfBuzz' src directory, a step in the script will fail and you should edit the BUILD.gn file accordingly and continue the roll manually. Chromium-local cherry picks or patches can be done by pushing new branches to refs/heads/chromium/ of [1]. The set of HarfBuzz OWNERS has write rights to this part of the tree. We suggest to follow a pattern of naming branches needed for Chromium revisions by the chromium milestone number. For example, if a cherry-pick is needed for M65, push to "refs/heads/chromium/m65" and reference the new commit in DEPS. Take a look at https://chromium-review.googlesource.com/c/chromium/src/+/937502 for an example. Currently we are intentionally not building the following files from HarfBuzz. Specifically, we are not building hb-coretext any longer, as we rely on HarfBuzz' built-in AAT shaping. dump-indic-data.cc dump-khmer-data.cc dump-myanmar-data.cc dump-use-data.cc hb-coretext.h hb-coretext.cc hb-directwrite.cc hb-directwrite.h hb-fallback-shape.cc hb-null.hh hb-ot-color-sbix-table.hh hb-ot-color-svg-table.hh hb-ot-color.cc hb-uniscribe.cc hb-uniscribe.h test-unicode-ranges.cc