Update on forcing autohinting per font | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Hi,
it was noticed in https://bugzilla.redhat.com/show_bug.cgi?id=705348 that the
most straightforward way to force autohinting for a particular font:
<match target="font">
<test name="family" compare="eq">
<string>Your Font</string>
</test>
<edit name="autohint" mode="assign">
<bool>true</bool>
</edit>
</match>
MAY CAUSE PROBLEMS in Qt applications (more precisely, force autohinting also
for other fonts which should use the bytecode interpreter), especially if your
font is one of the fonts pulled in for locale coverage (e.g. the Lohit fonts).
Instead, the following snippet is safe to use:
<match target="font">
<test qual="first" name="family" compare="eq">
<string>Your Font</string>
</test>
<edit name="autohint" mode="assign">
<bool>true</bool>
</edit>
</match>
Note the added qual="first" attribute. Please ALWAYS USE THIS QUALIFIER when
forcing autohinting for a specific font.
(I wasn't aware of this issue myself before this bug report came up. Thanks to
Akira Tagoh for the qual="first" fix.)
Kevin Kofler
_______________________________________________
fonts mailing list
fonts@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/fonts
http://fonts.fedoraproject.org/
[Home] [Fedora Users] [Fedora Legacy List] [Fedora Maintainers] [Fedora Desktop] [Red Hat 9 Bible] [Fedora Bible] [Fedora SELinux] [Big List of Linux Books] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools]