public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] harfbuzz: Update to version 12.1.0
Date: Sun,  5 Oct 2025 14:35:56 +0200	[thread overview]
Message-ID: <20251005123556.3411189-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20251005123556.3411189-1-adolf.belka@ipfire.org>

- Update from version 11.4.5 to 12.1.0
- Update of rootfile
- Changelog
    12.1.0
	- Build fixes with GCC 15 on some 32 bit platforms.
	- Fix misaligned pointer use.
	- New API, `hb_ot_layout_lookup_collect_glyph_alternates()`, to collect glyph
	  substitutions from single and alternate substitution lookups in one call,
	  instead of getting substitutions one by one using
	  `hb_ot_layout_lookup_get_glyph_alternates()`.
	- New API
	  +hb_ot_layout_lookup_collect_glyph_alternates()
    12.0.0
	- The major feature of this release is that the Variable Composites /
	  Components (`VARC` table) addition to the ISO OpenFontFormat has graduated
	  from experimental, and is now enabled by default. It can be disabled at
	  compile time by defining the `HB_NO_VAR_COMPOSITES`z macro.
	  `VARC` table is a new way to store glyph outlines, that allows for better
	  shape reuse, and can reduce font file size for Chinese, Japanese, Korean, and
	  some other scripts drastically. Some font design tools provide a similar
	  feature to designers, known as "smart components". This technology brings the
	  same idea to the compiled font file. For the format specification, see:
	  https://github.com/harfbuzz/boring-expansion-spec/blob/main/VARC.md
	  Test fonts can be found at:
	  https://github.com/notofonts/noto-cjk-varco/releases/tag/v0.003
	  The Fontra font editor already supports this technology.
	  Note that this new format involves just the HarfBuzz draw API and does not
	  affect shaping.
	- Correctly handle `markFilteringSet` lookup field during subsetting.
	- Deduplicate features during subsetting.
	- Disable “more” buffer messages that give more verbose output when using
	  buffer messages callbacks, as it has a performance overhead. Users/tools that
	  need the more verbose messages should define `HB_BUFFER_MESSAGE_MORE` to 1
	  when building HarfBuzz.
	- Shaping and instancing optimizations.
	- Fix subsetting issues when building with GCC 12.
    11.5.1
	- Optimized partial-instancing of fonts with a large number of axes. Now over
	  two times faster.
	- Fix C++ STL atomics implementation.
    11.5.0
	- Update to Unicode 17.0.0.
	- Subsetter optimizations.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 config/rootfiles/common/harfbuzz | 8 ++++----
 lfs/harfbuzz                     | 4 ++--
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/config/rootfiles/common/harfbuzz b/config/rootfiles/common/harfbuzz
index 94c051fae..b58d64035 100644
--- a/config/rootfiles/common/harfbuzz
+++ b/config/rootfiles/common/harfbuzz
@@ -47,16 +47,16 @@ usr/include/harfbuzz/hb-script-list.h
 #usr/lib/cmake/harfbuzz/harfbuzz-config.cmake
 #usr/lib/libharfbuzz-cairo.so
 usr/lib/libharfbuzz-cairo.so.0
-usr/lib/libharfbuzz-cairo.so.0.61145.0
+usr/lib/libharfbuzz-cairo.so.0.61210.0
 #usr/lib/libharfbuzz-gobject.so
 usr/lib/libharfbuzz-gobject.so.0
-usr/lib/libharfbuzz-gobject.so.0.61145.0
+usr/lib/libharfbuzz-gobject.so.0.61210.0
 #usr/lib/libharfbuzz-subset.so
 usr/lib/libharfbuzz-subset.so.0
-usr/lib/libharfbuzz-subset.so.0.61145.0
+usr/lib/libharfbuzz-subset.so.0.61210.0
 #usr/lib/libharfbuzz.so
 usr/lib/libharfbuzz.so.0
-usr/lib/libharfbuzz.so.0.61145.0
+usr/lib/libharfbuzz.so.0.61210.0
 #usr/lib/pkgconfig/harfbuzz-cairo.pc
 #usr/lib/pkgconfig/harfbuzz-gobject.pc
 #usr/lib/pkgconfig/harfbuzz-subset.pc
diff --git a/lfs/harfbuzz b/lfs/harfbuzz
index 6d6333051..8aa54359c 100644
--- a/lfs/harfbuzz
+++ b/lfs/harfbuzz
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 11.4.5
+VER        = 12.1.0
 
 THISAPP    = harfbuzz-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = a4a392c238857c414ee7659926a8e5c857e35079d47f65d69713b1c77c0e12b12ad34b432dbf339a3aed2160e7f23e1403d5036d66e47c9748b9eda3b95484a2
+$(DL_FILE)_BLAKE2 = 126fd2f5028a2b99652dfca2948b43bf83f6ff498e067d561adbd686b24b4b496153cb6acc8ede412bd0ac407e08422fb40b0224206a7c45736969c10b62cfaa
 
 install : $(TARGET)
 
-- 
2.51.0



      reply	other threads:[~2025-10-05 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 12:35 [PATCH] core199: Ship harfbuzz Adolf Belka
2025-10-05 12:35 ` Adolf Belka [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251005123556.3411189-2-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox