Bug 10414

Attached patch is from openSUSE Build.

Author: Mike Fabian

This patch makes the rendering settings from gnome-font-properties work.

For example in case of the antialias option:

Without the patch, cairo will add the antialias option to the
fontconfig pattern only if it is not already there. But the option
might already be in the pattern because a fontconfig setup file in
/etc/fonts or ~/.fonts.conf adds it ot the pattern.

With the patch, cairo first deletes the antialias option from the
pattern unconditionally, then adds its own value of this option.

Same for the other options like rgba, hinting, and hintstyle.

When doing it like this, the settings in gnome-font-properties
are preferred over any rules like

        <match target="pattern">
                <edit name="autohint">
                        <bool>true</bool>
                </edit>
                <edit name="hintstyle">
                        <const>hintfull</const>
                </edit>
                <edit name="antialias">
                        <bool>true</bool>
                </edit>
        </match>

in a fontconfig setup file. I.e. such rules will then only set a
default if nothing is set in gnome-font-properties or if a desktop
different from gnome is used.

If there are rules like

        <match target="font">
                <edit name="autohint">
                        <bool>true</bool>
                </edit>
                <edit name="antialias">
                        <bool>true</bool>
                </edit>
        </match>

in a fontconfig setup file which match on "font" instead of "pattern",
these rules will stil win over the settings in gnome-font-properties.

Therefore, the default systemwide fontconfig setup in /etc/fonts
should avoid using rules matching on "font" for setting options which
can also be changed in gnome-font-properties.

Reference: https://bugzilla.novell.com/show_bug.cgi?id=104365