Hi,

anybody knows why Rh's Kde 2.2-10 can't do the antialiasing for fixed font properly??? everything works fine, I have a nice smooth desktop and all fonts are ok, but I'm not able to set the fixed font as "fixed": it always remains the strangest font I've ever seen : "Arioso" unintellegible ang ugly.

I guess it has something to do with fonts and fonts paths : true types or type 1 or anything else... but I can't figure it out. I'm thinking of using Kfontinstaller or something like that, would you recommend it to me?

PLEASE PLEASE PLEASE answer, help me!

el felipe wishes everybody a nice year

Have you tried changing the default fonts in the KDE control center under "look and feel"?

...of course I did, it was the first thing. but after changing it returns to the same value of "Arioso"...

don't know what to do, it seems kfontinstaller isn't able either...

if anyone got a RH 7.2 and solved this little problem please tell me!!!

ciao!

If you do a search of the forums for "fonts" you find a lot of threads about this topic, its quite possible that your question has already been answered.

I also had that problem before. Since it was a standard install box for testing I reinstalled and it went away. I know that may be a possibility for you. On that box, it was a function of the xfs (x font server daemon) not being compatible with the xserver itself when I loaded the fonts. Once I reinstalled, I was using a different xserver (i.e. riva128 as opposed to TNT whatever.)

This is a horrible bug in KDE. What I am about to do is just go ahead and DELETE all my linux fonts and just use the windows ones. They are the only fonts that seem to work well (and look good). I'll let you know how that works.

One of the main problems I think KDE has is that when anti-aliasing is on (Control Center -> Look And Feel -> Fonts) it wont show fonts that cant be anti-aliased limiting the selection waay down (possibly the reason for that Arioso font poping up randomly).

On another computer of mine I tried disabling XFS to see if that helps. To make a long story short, no, it doesnt. I dont recomment trying it.

I hope that KDE 3.0 fixes this problem as it is not an issue with non KDE applications.

I asked in #kde-users on openprojects and all they can suggest is downgrading Qt to 2.3.1...

I havent tried that yet but really do not think that could be the problem...