From 5ee800c123dc50acda63e464265a07b29cbdcf81 Mon Sep 17 00:00:00 2001 From: Werner Lemberg Date: Mon, 28 Apr 2025 13:47:51 +0200 Subject: [PATCH] * docs/CHANGES: Updated. --- docs/CHANGES | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/docs/CHANGES b/docs/CHANGES index b334dbb63..6a6eaf973 100644 --- a/docs/CHANGES +++ b/docs/CHANGES @@ -2,11 +2,19 @@ CHANGES BETWEEN 2.13.3 and 2.14.0 (2025-Mmm-DD) I. IMPORTANT CHANGES - - Bitmap-only TrueType fonts now ignore FT_LOAD_NO_BITMAP flag and - proceed loading bitmaps instead of giving an error. This behavior - is documented and implemented for other bitmap-only fonts. The - flag was always meant to suppress the bitmap strikes in favor of - outlines, not to ban them completely. + - A new configuration macro `FT_CONFIG_OPTION_USE_HARFBUZZ_DYNAMIC` + is available to load the HarfBuzz library dynamically (in addition + to the standard static and dynamic linking modes); both meson and + autotools support have been updated accordingly (but not CMake + yet). Using this new feature makes it possible to avoid the + circular dependency between HarfBuzz and FreeType. + + A side effect of this change is that FreeType no longer uses + HarfBuzz header files (if HarfBuzz support is activated). To make + this work, we now require at least HarfBuzz version 2.6.8, + released in June 2020. + + This code was contributed by Behdad Esfahbod. - The auto-hinter got new abilities. @@ -28,6 +36,12 @@ CHANGES BETWEEN 2.13.3 and 2.14.0 (2025-Mmm-DD) The central algorithm and the foundation of this feature was Craig White's GSoC 2023 project. + - Bitmap-only TrueType fonts now ignore FT_LOAD_NO_BITMAP flag and + proceed loading bitmaps instead of giving an error. This behavior + is documented and implemented for other bitmap-only fonts. The + flag was always meant to suppress the bitmap strikes in favor of + outlines, not to ban them completely. + III. MISCELLANEOUS