general/freetype2
2
0
Fork 0
mirror of git://git.sv.nongnu.org/freetype/freetype2.git synced 2026-01-19 04:52:09 +00:00
Code Issues Projects Releases Wiki Activity

* docs/CHANGES: Updated.

Browse Source
This commit is contained in:
Werner Lemberg
2025-04-28 13:47:51 +02:00
parent 3c40134946
commit 5ee800c123
1 changed files with 19 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/CHANGES
View File

@@ -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