missing a terminator caused a document generation fail.

FcPattern isn't compatible to the older.

and get back the behavior.

Nick Alcock authored Dec 13, 2014 and Akira TAGOH committed Dec 15, 2014

The SGML for these functions exists, and they are named as manpages,
but because they are not mentioned in fontconfig-devel.sgml, no
documentation is ever generated, and installation under --enable-docs
fails.

(The documentation I have written in fontconfig-devel.sgml is boilerplate
so I can get the manpages generated. It's probably wrong.)

All color fonts are designed to be scaled, even if they only have
bitmap strikes.  Client is responsible to scale the bitmaps.  This
is in constrast to non-color strikes...

Clients can still use FC_OUTLINE to distinguish bitmap vs outline
fonts.  Previously FC_OUTLINE and FC_SCALABLE always had the same
value.  Now FC_SCALABLE is set to (FC_OUTLINE || FC_COLOR).

Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=87122

Only adds "color" to pattern if FreeType version supports color.

Based on patch from Jungshik Shin.

As reported on the mailing list by Tanel Liiv.  Found using American Fuzzy Lop.

https://bugs.freedesktop.org/show_bug.cgi?id=86950

Patch from Tom Yan

https://bugs.freedesktop.org/show_bug.cgi?id=85225

This reverts commit c6aa4d4b.

This issue has been fixed in poppler and we no longer need to patch it out in fontconfig.

https://bugs.freedesktop.org/show_bug.cgi?id=82876

This reverts commit a5a384c5.

I don't remember what I had in mind for "We will use this property later.", but
the change was wrong.  If a font pattern doesn't have any value for element,
it must be interpretted as "it matches any value perfectly.  And "perfectly"
must have a score of 0 for that to happen.

This was actually affecting bitmap fonts (in a bad way), as the change made
an outline font to always be preferred over a (otherwise equal) bitmap font,
even for the exact size of the bitmap font.  That probably was never noticed
by anyone, but with the font range support this has become clear (and worked
around by Akira).  To clean that up, I'm reverting this so I can land the
rest of patches for bug 80873.

https://bugs.freedesktop.org/show_bug.cgi?id=80873#c10

https://bugs.freedesktop.org/show_bug.cgi?id=82432

Bug 82358 - FcAtomicLock fails on OS X on network mounts
https://bugs.freedesktop.org/show_bug.cgi?id=82358

Ouch!

https://bugs.freedesktop.org/show_bug.cgi?id=82099

https://bugs.freedesktop.org/show_bug.cgi?id=82228

https://bugs.freedesktop.org/show_bug.cgi?id=82220
https://bugs.freedesktop.org/show_bug.cgi?id=82228

We should remove this alias mess.

Rest of Part of https://bugs.freedesktop.org/show_bug.cgi?id=81453

Adds new API:

	FcWeightFromOpenType()
	FcWeightToOpenType()

Such that Regular is closer to Medium than to DemiLight

Part of https://bugs.freedesktop.org/show_bug.cgi?id=81453
Also hooks up FC_WEIGHT_BOOK to fcfreetype.c.

Previously, if the patten didn't request, eg, style, then the style
and stylelang were fully copied from the font, even though the pattern
had a stylelang.  Eg:

$ fc-match 'Apple Color Emoji:stylelang=en'
Apple Color Emoji.ttf: "Apple Color Emoji" "標準體"

This change both fixes that and makes the code much more readable.  Now:

$ fc-match 'Apple Color Emoji:stylelang=en'
Apple Color Emoji.ttf: "Apple Color Emoji" "Regular"

Regex matching was disabled in f6244d2c

That's the correct BCP 47 code.

iconv support was turned off by default in f30a5d76.
Some fonts, like Apple Color Emoji, only have their English
name in a MacRoman entry.  As such, decode MacRoman ourselves.

This reverts commit fd5667b4.

This was wrong, as pointed out by Akira on the list.
We want symlinks to final destination.

From:
https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-fontconfig/fontconfig-2.11.0-symlinks-fix.patch

Don't add duplicate lang from FC_LANG if the pattern already has.

https://bugs.freedesktop.org/show_bug.cgi?id=81186

Fixes https://bugs.freedesktop.org/show_bug.cgi?id=81228

test-migration.c:17:5: warning: pointer targets in passing argument 1 of 'FcStrDirname' differ in signedness