* Fix manuals in section 3 so they get built and installed.
* Rework GSUB/GPOS script parsing to avoid crashing when presented
with broken fonts.
* Add a few more example configuration files to /etc/fonts/conf.d
from the debian packaging.
Fix memory leak of patterns rejected by configuration (#2518)
Create prototype $PREFIX/etc/fontconfig/conf.d directory and populate
it with a few sample files. These samples are unused as the file
names don't start with numbers.
Update documentation.
Fontconfig 2.2.99 contains a few minor bug fixes plus the addition of
polite type warnings for the config file. This latter change could use a
bit of exposure to existing config files to see if it whines about
legitimate configurations.
changes:
2.2.97
Fc-cache sleeps before exiting to ensure filesystem timestamps are well
ordered.
Added Punjai orthography.
The timestamp in fonts.conf is gone now. Too many problems.
The default font path includes all of the X fonts; use selectfont/rejectfont
to eliminate bitmaps, as shown in the sample local.conf file.
<include> configuration elements may now reference a directory. Files
in that directory matching [0-9]* are loaded in UTF-8 collating sequence order.
<selectfont> configuration added to control which fonts are used.
fontformat font pattern elements built from the FT_Get_X11_Font_Format
function in newer versions of FreeType.
'capability' list constructed from gsub/gpos and silf values in TrueType
files.
Multi-lingual names (style, family, fullname) extracted and stored with
parallel <foo>lang properties marking language.
2.2.98
Share object name strings (Michael Meeks)
Eliminate a couple of codepoints from Russian orthography (John Thacker)
Add synthetic emboldening configuration changes (Jakub Pavelek)
Change FcFontSetSort to ignore language after fonts with the requested
languages have been found. (Owen Taylor)
Add some RedHat font configuration changes (Owen Tayler).
Add full Unicode case folding support to case-ignoring string functions
(Keith Packard)
Remove Han characters from Korean orthography (Tor Andersson)
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
changes:
2004-06-30 Keith Packard <keithp@keithp.com>
* README:
* configure.in:
* fontconfig/fontconfig.h:
Update for 2.2.96
2004-06-30 Keith Packard <keithp@keithp.com>
Provided by: Lubos Lunak <l.lunak@suse.cz>
* src/fccfg.c: (FcConfigUptoDate):
However FcConfigUptoDate() doesn't seem to work. See the attached
patch. First there's an obvious misplaced parenthesis making it
return always false, and second, even this call fails to detect font
changes (e.g. adding a new font to
/usr/X11R6/lib/X11/fonts/truetype). The patch should fix that as
well. The problem seems to be triggered by my fonts.conf specifying
only /usr/X11R6/lib/X11/fonts , and therefore config->configDirs
doesn't include subdirs, unlike config->fontDirs.
2004-06-03 Keith Packard <keithp@keithp.com>
* fontconfig/fontconfig.h:
Remove comma at end of FcResult enum definition.
2004-05-29 Keith Packard <keithp@keithp.com>
* INSTALL:
Add steps to md5sum release
in particular this fixes a problem where no font matches can be found
by gtk2 apps. This should fix the problem where even the gtk-demo
program fails run.
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
built-in or not into a separate builtin.mk file. The code to deal
checking for built-in software is much simpler to deal with in pkgsrc.
The buildlink3.mk file for a package will be of the usual format
regardless of the package, which makes it simpler for packagers to
update a package.
The builtin.mk file for a package must define a single yes/no variable
USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether
to use the built-in software or to use the pkgsrc software.
practically verbatim with the "1.0.1" release that's in XFree86 4.3.x.
There have in fact been only function additions to the fontconfig API
since 2.0, so fontconfig has never actually had a bump in the shared
library major. Therefore, allow "fontconfig>=1.0.1" as the base
requirement.
Even 2.0.9 is not good enough for newer fontconfig; for example,
gtk2 won't buildlink correctly (and will use older X version of
include/freetype2/freetype/ftbdf.h) and libfontconfig needs
FT_Get_BDF_Property which is not defined.
No PKGREVISION bump is needed, because would not even build in
first place.
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
have some defaults for fonts.conf (/usr/X11R6/lib/X11/fonts/TTF
and /usr/X11R6/lib/X11/fonts/Type1).
I didn't bump PKGREVISION, because in many cases this will be the
same as if it configure figured it out.
I also considered adding TrueType and freefont, but they aren't
included with default XFree86 installation. Also, I didn't include
other font directories, because fontconfig's directory says it's
for outline fonts (.pf*, .tt* and .ot*) and to use local.conf or
~/.fonts.conf for bitmap fonts.
This closes PR #22927 where fontconfig's fc-cache has missing
directories causing font information caches to not be built (using
defaults).
Lots more documentation installed, fontconfig-config replaced
with pkgconfig file.
Changelog covered some versions only:
Release 2.2.0:
* Change version number to 2.2.0
Prerelease 2.1.94:
* BDF property support for foundry and width (Juliusz Chroboczek)
* Clean up GCC warnings (Colin Walters)
Prerelease 2.1.93:
* Use Type1 FontInfoRec to get more detailed weight information
* Run fc-cache from source tree to try and resolve LFS install issues
* Fix fontconfig-user.html generation (was getting smashed)
* Debian build files are in CVS now
* Fixes to build on Windows
* Compute monospacing by looking at glyphs instead of trusting font
* Get widths and more detailed weight from TrueType OS/2 table
* Global cache was re-statting a lot of files.
* Yet more RPM fixes from RedHat
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
Fontconfig is a library for configuring and customizing font access.
Fontconfig can:
* discover new fonts when installed automatically, removing a common
source of configuration problems.
* perform font name substitution, so that appropriate alternative fonts
can be selected if fonts are missing.
* identify the set of fonts required to completely cover a set of
languages.
* have GUI configuration tools built as it uses an XML-based
configuration file (though with autodiscovery, we believe this need is
minimized).
* efficiently and quickly find the fonts you need among the set of fonts
you have installed, even if you have installed thousands of fonts,
while minimzing memory usage.
* be used in concert with the X Render Extension and FreeType to
implement high quality, anti-aliased and subpixel rendered text on a
display.
Fontconfig does not:
* render the fonts themselves (this is left to FreeType or other
rendering mechanisms).
* depend on the X Window System in any fashion, so that printer only
applications do not have such dependencies.
Approved by wiz.
