On Thu, 31 Dec 2009 19:40:25 +0900, Norbert Preining <[email protected]> wrote: > Package: fontconfig > Version: 2.8.0-1.1 > Severity: normal
> Any suggestion how to go back to what was selected before (I did not
> change anything else font related in the mean time).
Having a pile of unrelated fonts share the same family name is a fairly
intractable problem; it really would be best if we just went back and
renamed them.
And, 6x13 is the hardest one to match as it sits between many similar
sized fonts. (6x12, 7x13, 7x14 and the 12x13 Japanese font).
fc-match won't quite show what you want as it doesn't apply the screen
DPI to the selection process, you'd want to use xfd -fa to test the full
Xft (or cairo) pattern.
I've managed to force a match using the following patterns:
$ fc-match -v fixed-12.5:semicondensed
or
$ xfd -fa fixed-9.5:semicondensed
I've also discovered a potential hack you can stick in your .fonts.conf
file. Because the 12x13ja font wasn't edited by Markus Kuhn, it doesn't
contain the broad language coverage that 6x13 enjoys. You can use this
to force selection of Markus' faces by adding:
<match target="pattern" >
<test name="family"><string>fixed</string></test>
<edit name="lang" >
<string>ab</string>
</edit>
</match>
to your .fonts.conf file. 12x13ja doesn't provide all of the glyphs
necessary for Abkhazian while 6x13 does. Then it's just a matter of
getting the right size, which you can do by either adjusting the
advertised DPI for your screen or by selecting a 10 point font at the
default of 96 dpi.
I'm not entirely sure how this has changed since 2.6.0, but frankly
bitmap fonts aren't a priority in fontconfig, and that they work at all
is something of a minor miracle. I'd encourage you to disable bitmap
fonts and get used to anti-aliased text on you screen :-)
--
[email protected]
pgpHfAKO9JGfU.pgp
Description: PGP signature
