public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] harfbuzz: Update to version 8.0.1
Date: Tue, 18 Jul 2023 13:12:34 +0200	[thread overview]
Message-ID: <20230718111237.7626-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4614 bytes --]

- Update from version 7.3.0 to 8.0.1
- Update of rootfile
- Changelog
    Overview of changes leading to 8.0.1
	- Build fix on 32-bit arm.
	- More speed optimizations:
	  - 60% speedup in retaingids subsetting SourceHanSans-VF.
	  - 38% speed up in subsetting (beyond-64k) mega-merged Noto.
	  - 16% speed up in retain-gid (used for IFT) subsetting of NotoSansCJKkr.
    Overview of changes leading to 8.0.0
	- New, experimental, WebAssembly (WASM) shaper, that provides greater
	   flexibility over OpenType/AAT/Graphite shaping, using WebAssembly embedded
	   inside the font file. Currently WASM shaper is disabled by default and needs
	   to be enabled at build time. For details, see:
	    https://github.com/harfbuzz/harfbuzz/blob/main/docs/wasm-shaper.md
	  For example fonts making use of the WASM shaper, see:
	    https://github.com/simoncozens/wasm-examples
	- Improvements to Experimental features introduced in earlier releases:
	  - Support for subsetting beyond-64k and VarComposites fonts.
	  - Support for instancing variable fonts with cubic “glyf” table.
	- Many big speed optimizations:
	  - Up to 89% speedup loading variable fonts for shaping.
	  - Up to 88% speedup in small subsets of large (eg. CJK) fonts (both TTF and
	    OTF), essential for Incremental Font Transfer (IFT).
	  - Over 50% speedup in loading Roboto font for shaping.
	  - Up to 40% speed up in loading (sanitizing) complex fonts.
	  - 30% speed up in shaping Gulzar font.
	  - Over 25% speedup in glyph loading Roboto font.
	  - 10% speed up loading glyph shapes in VarComposite Hangul font.
	  - hb-hashmap optimizations & hashing improvements.
	- New macro HB_ALWAYS_INLINE. HarfBuzz now inlines functions more aggressively,
	   which results in some speedup at the expense of bigger code size. To disable
	   this feature define the macro to just inline.
	- New API:
	  +HB_CODEPOINT_INVALID
	  +hb_ot_layout_get_baseline2()
	  +hb_ot_layout_get_baseline_with_fallback2()
	  +hb_ot_layout_get_font_extents()
	  +hb_ot_layout_get_font_extents2()
	  +hb_subset_input_set_axis_range()

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

diff --git a/config/rootfiles/common/harfbuzz b/config/rootfiles/common/harfbuzz
index a03367254..882d8b907 100644
--- a/config/rootfiles/common/harfbuzz
+++ b/config/rootfiles/common/harfbuzz
@@ -44,15 +44,15 @@
 #usr/lib/libharfbuzz-cairo.la
 #usr/lib/libharfbuzz-cairo.so
 usr/lib/libharfbuzz-cairo.so.0
-usr/lib/libharfbuzz-cairo.so.0.60730.0
+usr/lib/libharfbuzz-cairo.so.0.60801.0
 #usr/lib/libharfbuzz-subset.la
 #usr/lib/libharfbuzz-subset.so
 usr/lib/libharfbuzz-subset.so.0
-usr/lib/libharfbuzz-subset.so.0.60730.0
+usr/lib/libharfbuzz-subset.so.0.60801.0
 #usr/lib/libharfbuzz.la
 #usr/lib/libharfbuzz.so
 usr/lib/libharfbuzz.so.0
-usr/lib/libharfbuzz.so.0.60730.0
+usr/lib/libharfbuzz.so.0.60801.0
 #usr/lib/pkgconfig/harfbuzz-cairo.pc
 #usr/lib/pkgconfig/harfbuzz-subset.pc
 #usr/lib/pkgconfig/harfbuzz.pc
@@ -129,6 +129,7 @@ usr/lib/libharfbuzz.so.0.60730.0
 #usr/share/gtk-doc/html/harfbuzz/api-index-7-0-0.html
 #usr/share/gtk-doc/html/harfbuzz/api-index-7-1-0.html
 #usr/share/gtk-doc/html/harfbuzz/api-index-7-3-0.html
+#usr/share/gtk-doc/html/harfbuzz/api-index-8-0-0.html
 #usr/share/gtk-doc/html/harfbuzz/api-index-full.html
 #usr/share/gtk-doc/html/harfbuzz/apple-advanced-typography-api.html
 #usr/share/gtk-doc/html/harfbuzz/buffers-language-script-and-direction.html
@@ -232,3 +233,4 @@ usr/lib/libharfbuzz.so.0.60730.0
 #usr/share/gtk-doc/html/harfbuzz/why-do-i-need-a-shaping-engine.html
 #usr/share/gtk-doc/html/harfbuzz/why-is-it-called-harfbuzz.html
 #usr/share/gtk-doc/html/harfbuzz/working-with-harfbuzz-clusters.html
+
diff --git a/lfs/harfbuzz b/lfs/harfbuzz
index bfc40dba3..9c706f61e 100644
--- a/lfs/harfbuzz
+++ b/lfs/harfbuzz
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 7.3.0
+VER        = 8.0.1
 
 THISAPP    = harfbuzz-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 7b1f6fb0c4c7483ff7a7c27f613b8579af30a304432e1a4e157aec4344449aed93e68443df1f2bc741be6780a6b2214d54804e2df9a20d83c8256b5f98c7fcda
+$(DL_FILE)_BLAKE2 = e69305e5cddee2f9a928ab38b6904cc3e6fbafb319ad268047178667639a2a361576051a9a6443352b51adca47bb8998ca5c533afe12eac456c3170e171c1839
 
 install : $(TARGET)
 
-- 
2.41.0


             reply	other threads:[~2023-07-18 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 11:12 Adolf Belka [this message]
2023-07-18 11:12 ` [PATCH] meson: Update to version 1.2.0 Adolf Belka
2023-07-18 11:12 ` [PATCH] ninja: Update to version 1.11.1 Adolf Belka
2023-07-18 11:12 ` [PATCH] sdl2: Update to version 2.28.1 Adolf Belka

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=20230718111237.7626-1-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