 | | | Serious font problems | Serious font problems 2002-05-07 - By Jason L Tibbitts III
Back
I have a nice RPM of True Type fonts that I use, mostly gleaned from
various Windows machines. I 've used this package since 7.1 and I 've
had no problems. But with a fresh Valhalla installation I 'm having
some troubles:
1) KDE won 't antialias those fonts. It will antialias _some_ fonts,
like Utopia (Which is a Type1 font) so XFT is at least partially
working. It displays them without antialiasing just fine.
2) xterm mangles these fonts. Under 7.1 and 7.2 I can type xterm -fa
'andale mono ' and get a lovely xterm. Under 7.3 I get squished
garbage. I get pretty much the same equished garbage when I run
xterm with any TrueType font.
Note: I 've read the release notes; this seems unrelated to the
paragraph about antialiased fonts there.
Also note: this is not related to the
match
any size < 14
any size > 8
edit antialias=false;
bit in XftConfig; that is commented out. In fact, things are busted
with the same XftConfig that worked fine in 7.2. This doesn 't seem to
be a freetype problem, because I backed down to Freetype 2.0.5 that I
used with 7.2 and things are still busted.
The fonts.dir and fonts.scale files in
/usr/share/fonts/default/TrueType seem to be fine.
.xftcache doesn 't seem to be the problem; I deleted it and recreated
it without change.
I copied back the Xft libraries from a 7.2 machine without change.
I ran xterm with XFT_DEBUG=7 and the results are vastly different.
On a 7.1 or 7.2 machine, the last bit before the xterm opens is:
Match Pattern 17 of 32
core: False
outline: True
scalable: True
slant: 0
weight: 100
family: "Andale Mono "
style: "Regular "
file: "/usr/share/fonts/default/TrueType/Andalemo.TTF "
index: 0
encoding: "iso8859-1 "
size: 14
spacing: 100
charwidth: 11
rgba: 1
render: True
antialias: True
pixelsize: 19.0568
On the 7.3 machine (remember, same XftConfig), I get:
XftFontMatch after X resource substitutions Pattern 13 of 16
family: "andale mono " "LuciduxMono " "Lucidux Mono " "mono "
size: 14
weight: 200
charwidth: 4
spacing: 100
slant: 0
encoding: "iso8859-1 "
render: True
core: False
antialias: True
rgba: 0
minspace: False
pixelsize: 19.0568
The absense of "file " may be telling, but I don 't really understand
what 's going on.
I recall seeing a report like #2 above on the Xfree (or Xpert) list,
and the answer was that the X package needed updating from what was in
Skipjack. But there doesn 't seem to be anything newer than what 's
Valhalla.
I 'm really at a complete loss. Any assistance is appreciated.
- J <
|
|
|