Red Hat Bugzilla – Bug 64970
default XftConfig prefers substitute fonts over originals
Last modified: 2007-04-18 12:42:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.1 (X11; Linux i686; U;) Gecko/20020417
Description of problem:
The default Xft configuration file, "/etc/X11/XftConfig", tends to
preferentially use substitute fonts even when a proper match is available. For
example, it contains lines like this:
match any family == "Verdana" edit family += "Luxi Sans";
Now, Verdana is a fairly high quality font that many of us have on our systems
by way of Microsoft Windows. The edit above uses "+=", though, which *prepends*
"Luxi Sans" to the family list. Thus, even if Verdana is available, the lower
quality Luxi Sans will be used instead.
These "+=" lines should be changed to "=+", so that the substitute family is
appended rather than prepended. That way, the substitute will only be used if
the original request cannot be found.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Verdana on a Linux box. You can find this on a friendly neighborhood
2. Select Verdana for use in some Xft-enabled application.
Actual Results: Luxi Sans is used where Verdana was requested.
Expected Results: Given that Verdana was installed on the system, and Verdana
was requested, Verdana should have been used.
The tricky part of reproducing the bug is finding a convenient Xft-enabled
application. If you have a decent GNOME2 installation sitting around, the
"gnome-font-properties" capplet is a good one. Click on one of the font
buttons, and select "Verdana" in the font picker dialog. The font button shows
Created attachment 57385 [details]
proposed patch to change selected prepends to appends
Sounds sensible. I've made this change in 4.2.0-9.12. It will appear
in future erratum and rawhide at some point in the future.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.