GitLab

The utility programs don't use any freetype interfaces, so they
don't need to directly refer to freetype headers or libraries.

This header file needs to be included at the end of every file that
exports any freetype symbols.

This avoids requiring the freetype development files when cross compiling

When allocation for the node attributes fail, clean up the node allocation
and report failure.

For Version 2.5.0, (same for previous version 2.4.2), in source file fccfg.c,
on line 700,

Original:
      ret = FcStrCmpIgnoreCase (left.u.s, right.u.s) == 0;

Should change to:
      ret = FcStrStrIgnoreCase (left.u.s, right.u.s) == 0;

I think this is just a mistake when copy-n-paste similar codes in the same
function. Apparently, return for "Not_contain" should be just the inverse of
"Contain", not the same as "Equal".

Because conf.d is where most people look first.  And the comment at the top
of the README file says conf.d/README too.

Fix a couple of longstanding problems with fontconfig on Windows that
manifest themselves especially in GIMP. The root cause to the problems is in
Microsoft's incredibly stupid stat() implementation. Basically, stat()
returns wrong timestamp fields for files on NTFS filesystems on machines
that use automatic DST switching.

See for instance http://bugzilla.gnome.org/show_bug.cgi?id=154968 and
http://www.codeproject.com/datetime/dstbugs.asp

As fccache.c now looks at more fields in the stat struct I fill in them all.
I noticed that fstat() is used only on a fd just after opening it, so on
Win32 I just call my stat() replacement before opening instead...
Implementing a good replacement for fstat() would be harder because the code
in fccache.c wants to compare inode numbers. There are no (readily
accessible) inode numbers on Win32, so I fake it with the hash of the full
file name, in the case as it is on disk. And fstat() doesn't know the full
file name, so it would be rather hard to come up with a inode number to
identify the file.

The patch also adds similar handling for the cache directory as for the fonts
directory: If a cachedir element in fonts.conf contains the magic string
"WINDOWSTEMPDIR_FONTCONFIG_CACHE" it is replaced at runtime with a path under
the machine's (or user's) temp folder as returned by GetTempPath(). I don't
want to hardcode any pathnames in a fonts.conf intended to be distributed to
end-users, most of which who wouldn't know how to edit it anyway. And
requiring an installer to edit it gets complicated.

This reverts commit b6079229.

Conflicts:

	src/Makefile.am

Xft still uses the macros that are in fcprivate.h. Document those macros and
include fcprivate.h in the published header files.

FcConfigGetFonts returns the internal font set used by the library which
must not be freed by the application or 'bad things' will happen.

The behaviour of FcFontMatch and FcFontSetMatch is hard to understand without
knowing that they call FcFontRenderPrepare.

Several functions had no indication of what the return value would be,
mostly these were allocation failure returns.

docbook2man has fixed output file names; place output in a subdirectory to
avoid collisions.

It was redundant and out-dated.

Conf files had an initial comment mentioning the files' name.
This was outdated and wrong in most cases.  There's no real use in that.

Times, Helvetical, and Courier are already handled in 30-metric-aliases.conf.
Remove them here and add a comment instead.

These two names are typos of the correct names. Instead of simply changing
them, the correct thing to do is leave them in the library, add the correct
functions and mark them as deprecated so any source packages will be updated.

This requires bumping the minor version of the library (for adding APIs)
instead of bumping the major version of the library (for removing APIs).

<parameter>ls</function> needed to be <parameter>ls</parameter>.

Just adding the .fncs versions doesn't get these files generated.

These functions no longer exist.

without updating anything.

The old per-user cache filename is no longer used.

FcStrCopyFilename constructs a canonical path for any argument, including
expanding leading ~ and editing '.' and '..' elements out of the resulting
path.