summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/harfbuzz-ng/src/hb-ot-shaper-khmer-machine.hh
Commit message (Collapse)AuthorAgeFilesLines
* Update Harfbuzz to version 8.2.2Eskil Abrahamsen Blomfeldt2023-11-011-7/+7
| | | | | | | Pick-to: 5.15 6.2 6.5 6.6 Task-number: QTBUG-118615 Change-Id: Ifdf6023781c7202bc07f7cfb821c8cfefd2720a8 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
* Update Harfbuzz to 7.0.1Eskil Abrahamsen Blomfeldt2023-03-011-1/+1
| | | | | | | | | | | Note: 6.4.x update has to be done in a separate commit because it did not get the update to 6.0.0, so the cherry-pick will not apply. Pick-to: 6.2 6.5 Task-number: QTBUG-111535 Change-Id: I9d4aae98f8267827ec983ca89b1310006c6aee78 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
* Update Harfbuzz to version 6.0.0Eskil Abrahamsen Blomfeldt2023-01-311-0/+428
Note: This requires an update to the tst_qtextlayout test, because the test assumed that the Arabic string would always yield a run of two glyphs. This was a side effect of how Harfbuzz handled Qt's test font, which has zero font tables and cannot be used for shaping. With the Harfbuzz update, the Arabic text here yields a single cluster instead, which actually makes more sense, so the test has been made a bit more robust to support both cases. Pick-to: 6.2 6.5 Task-number: QTBUG-110338 Change-Id: I93d4cf8e3046dc93224e144d4c81d86bef4918d1 Reviewed-by: Lars Knoll <lars@knoll.priv.no> Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>