Fontconfig Development Snapshots

Fontconfig 2.13.92

Fontconfig 2.13.91

Speaking more for flatpak rework, fontconfig relies on font paths to determine cache filename and the path is used to generate MD5. this means fontconfig re-generates caches when paths are changed even if they have same fonts. This affects the performance a lot on Flatpak applications because they share fonts from host on different paths and then re-generating caches at first run. So we put and UUID into .uuid at a font directory as an unique indentifier, and generate caches with it instead of MD5. However this affects the reproducible builds now because UUID is randomly generated and it is impossible to predict. So we've reverted this and implemented new one to share caches. it can be done in configuration now:

<remap-dir as-path="/usr/share/fonts">/run/host/fonts</remap-dir>

which means mapping a path "/usr/share/fonts" to /run/host/fonts. when accessing a font under /run/host/fonts, fontconfig will be going to find out a cache of name MD5("/usr/share/fonts") instead of MD5("/run/host/fonts"). So what if having own fonts under /usr/share/fonts ? To address this, fontconfig extends dir element to give a salt to allow generating different cache name:

<dir salt="unique identifier">/usr/share/fonts</dir>

This change allows to deal with a set of different fonts in same paths between hosts and containers say.

<reset-dirs/> removes all of fonts directories where added by dir elements. this is useful when you want to override fonts directories without modifying fonts.conf.

Fontconfig 2.12.93

Fontconfig 2.12.92

Fontconfig 2.12.91

Fontconfig 2.11.95

Fontconfig 2.11.94

Fontconfig 2.11.93

Fontconfig 2.11.92

Fontconfig 2.11.91

Fontconfig 2.10.95

Fontconfig 2.10.94

Fontconfig 2.10.93

The bits are available here. The ChangeLog since 2.10.92 is available here.

Fontconfig 2.10.92

The bits are available here. The ChangeLog since 2.10.91 is available here.

Fontconfig 2.10.91

The bits are available here. The ChangeLog since 2.10.2 is available here.

Fontconfig 2.9.92

The bits are available here. The ChangeLog since 2.9.91 is available here.

Fontconfig 2.9.91

Various bug fixes and feature enhancements is included. the summary of the changes since 2.9 is:

The bits are available here. The ChangeLog since 2.9.0 is available here.

Fontconfig 2.2.96

FcConfigUpToDate had some bugs rendering it useless. Thanks to Lubos Lunak for fixes. Also, picky C compilers whined about a spurious comma in an enum. The bits are available here. The ChangeLog since 2.2.95 is available here.

Fontconfig 2.2.95

Fontconfig was using MIN/MAX/ABS macros that happened to come from FreeType. FreeType 2.1.8 (wisely) prefixes those names with FT_ now. Fontconfig was changed to have it's own versions of these macros (FC_MIN/FC_MAX/FC_ABS) to avoid problems in the future. A few other minor changes are included in this release. The bits are available here. The ChangeLog since 2.2.94 is available here.

Fontconfig 2.2.94

Fontconfig 2.2.93 was packaged with a broken version of libtool. That's the only change for fontconfig 2.2.94. The bits are available here.

Fontconfig 2.2.93

Fontconfig 2.2.93 is the third snapshot in the 2.3 release cycle. The bits are available here The ChangeLog since 2.2.92 is available here.

Fontconfig 2.2.92

Fontconfig 2.2.92 is the second snapshot in the 2.3 release cycle. The bits are available here The ChangeLog since 2.2.90 is available here

Fontconfig 2.2.90

Fontconfig 2.2.90 is the first snapshot in the 2.3 release cycle. The bits are available here