[narfi@dhcp-104-6 Mail]$ rpm -q XFree86 XFree86-xfs kdebase drakxtools
XFree86-4.2.0-8mdk
XFree86-xfs-4.2.0-8mdk
kdebase-2.2.2-86mdk
drakxtools-1.1.7-91mdk
I installed 8.2 beta4, with English as a primary language and Japanese,
Icelandic and German as secondary languages.
I've upgraded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
the /usr/X11R6/lib/X11/fonts/drakfont/ttf and usr/X11R6/lib/X11/fonts/drakfont/type1
directories are missing from /etc/X11/XftConfig
(add it and everything will be fine). AA fonts are handled to the new Xft extension,
so your xfs settings have no
On Fri, 8 Mar 2002, H. Narfi Stefansson wrote:
Critial point in setup: I'm using anti-aliasing in KDE
I get the same problem, regardless if I use anti-aliasing or not.
I have a directory (~/fonts) that contain a lot of ttf fonts, mostly the
classics verdana, tahoma, courier new, etc. I added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 08 March 2002 21:44, you wrote:
I get the same problem, regardless if I use anti-aliasing or not.
Than it is not the same problem I think. The latest problem fixed in
drakfont is possibly not on cooker mirrors yet:
Can it be that your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 08 March 2002 21:49, you wrote:
I believe this was my 3rd report about the matter, but I didn't know where
hmm..seems I'm not reading well either, because this is the first time I see it:)
So you can confirm that it fixes your problem?
On Fri, 8 Mar 2002, Danny Tholen wrote:
I get the same problem, regardless if I use anti-aliasing or not.
Than it is not the same problem I think. The latest problem fixed in
drakfont is possibly not on cooker mirrors yet:
Can it be that your fonts are *.TTF (Capitals)? If so, try renaming
Danny Tholen [EMAIL PROTECTED] writes:
the /usr/X11R6/lib/X11/fonts/drakfont/ttf and usr/X11R6/lib/X11/fonts/drakfont/type1
directories are missing from /etc/X11/XftConfig
(add it and everything will be fine). AA fonts are handled to the new Xft extension,
so your xfs settings have no
