The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: It was the FontPath all the time
by Eric Laffoon on Thursday 15/Mar/2001, @17:40
|
I peel your fain... er... feel you pain. ;-)
I didn't quite go that far but I failed to comprehend that xfs and xft load seperate font collections. Seems a bit weird and less than efficeint. Then again it's interesting to have font servers running like that. I found XftConfig a long way from my other config file.
However my system NEVER looked so good so it was worth it!!!
BTW anyone get Corel Draw's font server working with this menagerie?
|
[
Reply To This | View ]
|
Re: It was the FontPath all the time
by Arnd Bergmann on Friday 16/Mar/2001, @04:42
|
Damn, it was not the FontPath. I just thought that if the article is so specific about it, there has to be some meaning behind it.
Anyway, I still can't select non-antialiased fonts in KDE. The most obvious symptoms of this are that in Konsole, you can only choose a font called 'fixed', which can be replaced by anything in XftConfig or is automatically replaced by the alphabetically (!) first font otherwise.
The same happens to the font settings in Control Center when you try to get back to defaults or have a fresh installation.
I have fixes for both symptoms in kdelibs, but the real problem is somewhere deeper.
Does anyone actually have non-AA fonts in kde2.1/Qt2.3/XFree86-4.0.2-branch or does is work in another version?
|
[
Reply To This | View ]
|
Re: It was the FontPath all the time
by Ravi on Friday 16/Mar/2001, @07:25
|
The problem is with Xft. Xft has a bug related to choosing fixed width fonts. Please look at http://lists.kde.org/?l=kde-devel&m=98399428807752&w=2
which contains a fix for your problem.
Ravi
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|