2.3.1:
This bug fix release corrects a regression in font emboldening introduced
in 2.3.0. Another bug against font appearance in 2.3.0 has been reported
but not yet resolved - since no progress was being made on it, I decided
to stop holding back the release of the fix we have.
2.3.0:
Notable changes in this release include:
- Subpixel LCD text rendering improvements
- Dropped support for building against versions of freetype2, fontconfig &
libXrender that pre-dated pkgconfig support.
- Raised minimum required versions to freetype2 2.1.6 & fontconfig 2.5.92.
plus of course assorted bug fixes and build configuration improvements.
2.2.0:
This release removes the deprecated xft-config script now that pkg-config
is well-established as it's replacement. It also updates the xft pkg-config
file to reduce unnecessary linking in users of libXft, but may cause issues if
used with versions of pkg-config older than the pkg-config 0.22 release from
2007.
It also includes the usual recent set of build configuration improvements and
janitorial cleanups.
Migrate to xorg macros 1.3 & XORG_DEFAULT_OPTIONS
Set Xft.h version numbers from configure.ac
Split NEWS & README, update both
Add generated Xft.h to .gitignore
libXft 2.1.14
Header cleanup (bug#4703)
Fix install of generated Xft.h when builddir != srcdir
Janitor: Correct make distcheck and sparse warnings.
Added fake bold support (#1579, Novell #38202/223682).
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
version is now 2.1.13 (from 2.1.2). ChangeLog:
commit 19240d3605b5f1e88ca5509afffd48acdb7e1c5f
Revert "Drop Requires, use Requires.private instead."
This reverts commit a1c78ce68c5f2106c38b6cb93a6b22420e1a80ab.
Unfortunately this doesn't work on old pkg-config, which made
Requires.private completely useless. That's fixed in 0.22, but...
commit a1c78ce68c5f2106c38b6cb93a6b22420e1a80ab
Drop Requires, use Requires.private instead.
Users of libXft don't need to link with fontconfig, freetype and
Xrender directly if they don't use them.
commit 541c6194d986e7849ee9541a9fd60b0724647a44
Bug #14232: Fix XftDrawRect when Render not supported.
commit 8a7f3d450c1f339f429dbce55df523d026c92375
Register objects used by libXft.
libXft uses XFT_MAX_GLYPH_MEMORY without first registering with
fontconfig.
commit 8ae5ea8c75a7850fa0aca0acc3962b6263f55094
XftFontOpenInfo: Use of uninitialised value of size 8 (bug 11200)
This is due to XftFontInfoFill using the binary representation of the
XftFontInfo to generate fi->hash.
With 64-bit pointers there is padding between .hash and .file in struct
_XftFontInfo. This padding is not initialized, and the hash uses these
bytes.
This will interfere with finding "a matching previously opened font" in
XftFontOpenInfo, and XftFontInfoEqual, which uses memcmp, will have
similar problems.
This fix makes no assumptions about the sizes and alignment of
members of struct _XftFontInfo by using memset. (It also makes
no assumptions about what FcPatternGet* does to its output parameter
when it returns FcResultNoMatch.)
- XftFontOpenInfo: Use of uninitialised value of size 8 (bug 11200)
- libXft was using XFT_MAX_GLYPH_MEMORY without first registering
with fontconfig.
- Include <ftsynth.h> if FT_GlyphSlot_Embolden() shall be called.
First two from GIT, last one by me.
Bump rev.
Xft (2.0) provides a client-side font API for X applications. It uses
Fontconfig to select fonts and the X protocol for rendering them. When
available, Xft uses the Render extension to accelerate text drawing.
When Render is not available, Xft uses the core protocol to draw
client-side glyphs. This provides completely compatible support of
client-side fonts for all X servers.
Xft (2.0) hides most of the underlying system details so that developers
can confidently use its API to access client-side fonts in any X
environment.
