This is with Wolverine.
Fire up KDE and fire up konqueror. The default is non anti-aliased
fonts. Make sure this is the case to observe the ugly fonts.
Go to http://slashdot.org/
Look at the article headings - the font is very poor and ugly. Characters
run into one another and the whole thing is blocky.
Even without anti-aliased fonts, Linux can do much much better than
I wouldn't recommend putting on anti-aliasing by default because it is
Tim Waugh suggested that this could be because I don't have 100dpi-fonts
installed. I've checked, and I do have them installed.
This is not the same issue as the Abiword issue either (as a recap, if
Abiword is installed, then Netscape renders ugly blocky fonts).
can you please do a chkfontpath --list?
Current directories in font path:
Got the culprit.
rpm -e XFree86-ISO8859-7-Type1-fonts
And the fonts look OK again. Very strange - they are low in the
fontpath pecking order.
This should be fixed in 2.1-10 (it sets the correct charset for your language).
Created attachment 14563 [details]
Shows gross font problem with XFree86-ISO8859-7-Type1-fonts installed
Sorry I have to re-open.
Not fixed with qa0401.
Take a look at the .jpg I just uploaded. It shows two
xmag's of Konqueror rendering slashdot.org.
One xmag is with XFree86-ISO8859-7-Type1-fonts
installed and the other is without. Guess which is
which :-) As we can see, the fonts rendered with that
package installed are very very poor.
But wait. There is more. I just tracked down _another_
set of fonts, which when installed, cause ugly font
rendering. The faulty fonts are this time from "abiword".
Damn Abiword fonts! They also make Netscape render
very ugly fonts.
It would be great if a full install of RH7.1 manages
to still render pleasant fonts. I really do think
that these ugly font issues make Linux look pretty
lousy to newcomers.
This was perhaps related: #13889.
Also, Abiword: #18855
Still bust in RH7.2beta3
At _least_ the poxy Abiword fonts are still causing trouble.
rpm -e abiword made web browsing tolerable again :-)
*** This bug has been marked as a duplicate of 18855 ***