From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] freetype: Update to version 2.12.1
Date: Thu, 05 May 2022 15:26:31 +0000 [thread overview]
Message-ID: <9dc43ad8-68e1-b2d9-35fe-457f43885c83@ipfire.org> (raw)
In-Reply-To: <20220504195100.2945046-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4717 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from version 2.11.1 to 2.12.1
> - Update of rootfile
> - Changelog
> CHANGES BETWEEN 2.12.0 and 2.12.1
> I. IMPORTANT BUG FIXES
> - Loading CFF fonts sometimes made FreeType crash (bug introduced in
> version 2.12.0)
> - Loading a fully hinted TrueType glyph a second time (without
> caching) sometimes yielded different rendering results if TrueType
> hinting was active (bug introduced in version 2.12.0).
> - The generation of the pkg-config file `freetype2.pc` was broken if
> the build was done with cmake (bug introduced in version 2.12.0).
> II. MISCELLANEOUS
> - New option `--with-librsvg` for the `configure` script for better
> FreeType demo support.
> - The meson build no longer enforces both static and dynamic
> versions of the library by default.
> - The internal zlib library was updated to version 1.2.12. Note,
> however, that FreeType is *not* affected by CVE-2018-25032 since
> it only does decompression.
> CHANGES BETWEEN 2.11.1 and 2.12.0
> I. IMPORTANT CHANGES
> - FreeType now handles OT-SVG fonts, to be controlled with
> `FT_CONFIG_OPTION_SVG` configuration macro. By default, it can
> only load the 'SVG ' table of an OpenType font. However, by using
> the `svg-hooks` property of the new 'ot-svg' module it is possible
> to register an external SVG rendering engine. The FreeType demo
> programs have been set up to use 'librsvg' as the rendering
> library.
> This work was Moazin Khatti's GSoC 2019 project.
> II. MISCELLANEOUS
> - The handling of fonts with an 'sbix' table has been improved.
> - Corrected bitmap offsets.
> - A new tag `FT_PARAM_TAG_IGNORE_SBIX` for `FT_Open_Face` makes
> FreeType ignore an 'sbix' table in a font, allowing applications
> to access the font's outline glyphs.
> - `FT_FACE_FLAG_SBIX` and `FT_FACE_FLAG_SBIX_OVERLAY` together
> with their corresponding preprocessor macros `FT_HAS_SBIX` and
> `FT_HAS_SBIX_OVERLAY` enable applications to treat 'sbix' tables
> as described in the OpenType specification.
> - The internal 'zlib' code has been updated to be in sync with the
> current 'zlib' version (1.2.11).
> - The previously internal load flag `FT_LOAD_SBITS_ONLY` is now
> public.
> - Some minor improvements of the building systems, in particular
> handling of the 'zlib' library (internal vs. external).
> - Support for non-desktop Universal Windows Platform.
> - Various other minor bug and documentation fixes.
> - The `ftdump` demo program shows more information for Type1 fonts
> if option `-n` is given.
> - `ftgrid` can now display embedded bitmap strikes.
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/freetype | 3 ++-
> lfs/freetype | 4 ++--
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/freetype b/config/rootfiles/common/freetype
> index ceb06b4d6..e7d8e9ff9 100644
> --- a/config/rootfiles/common/freetype
> +++ b/config/rootfiles/common/freetype
> @@ -51,6 +51,7 @@
> #usr/include/freetype2/freetype/fttrigon.h
> #usr/include/freetype2/freetype/fttypes.h
> #usr/include/freetype2/freetype/ftwinfnt.h
> +#usr/include/freetype2/freetype/otsvg.h
> #usr/include/freetype2/freetype/t1tables.h
> #usr/include/freetype2/freetype/ttnameid.h
> #usr/include/freetype2/freetype/tttables.h
> @@ -59,7 +60,7 @@
> #usr/lib/libfreetype.la
> #usr/lib/libfreetype.so
> usr/lib/libfreetype.so.6
> -usr/lib/libfreetype.so.6.18.1
> +usr/lib/libfreetype.so.6.18.3
> #usr/lib/pkgconfig/freetype2.pc
> #usr/share/aclocal/freetype2.m4
> #usr/share/man/man1/freetype-config.1
> diff --git a/lfs/freetype b/lfs/freetype
> index 8a308d70d..5233f7bb8 100644
> --- a/lfs/freetype
> +++ b/lfs/freetype
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 2.11.1
> +VER = 2.12.1
>
> THISAPP = freetype-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 15cc03e7b8ba93b2f240b0eee3f1cc07bca77d9ef67a1971d44d6c061a0dff2b13737fa417f7f2dc4e7e6df660223325931f69a107a6b2eaf14425fc71b7ca7b
> +$(DL_FILE)_BLAKE2 = c4737dc0c6e44e0a911545d604fdb2e8e8b3f5185d3f5dfe4e4561ee2d75b3e5a31afcbb2089306fec4b31ba10324a6ec6499c3735b2b7591c71e96fee4ed278
>
> install : $(TARGET)
>
prev parent reply other threads:[~2022-05-05 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 19:51 Adolf Belka
2022-05-05 15:26 ` Peter Müller [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=9dc43ad8-68e1-b2d9-35fe-457f43885c83@ipfire.org \
--to=peter.mueller@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