https://bugzilla.novell.com/show_bug.cgi?id=393748 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=393748#c9 Felix Miata <mrmazda@ij.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #9 from Felix Miata <mrmazda@ij.net> 2008-05-26 11:37:09 MDT --- (In reply to comment #2 from Mike Fabian)
In KDE, you use Hinting style "Medium". Don’t do that, use Hinting style "Full" otherwise the byte code interpreter will not be used and you get blurry fonts.
What you call blurry I call legible. Those skinny things you like need to be much bigger for me to see them.
Use reasonable hinting settings!
For me, that means no byte code interpreter, or whatever it takes to make SUSE render fonts that look the way they do on a Mac. I've been perfectly happy through several versions of SUSE with medium hinting, and can't remember ever liking full hinting. All that is tangential to this bug, which I am reopening because the presence or absence of albw.ttf and/or arial.ttf in the font path should not cause Epiphany and Firefox 3 menu fonts to be different or not from the menu fonts used by KDE, Opera, Konq3 & SeaMonkey 1.1.x. All gtk & qt apps running under KDE should use whatever fonts are specified in the KDE control panel, and they should all match each other, not be different, like Epiphany & FF3 are now. No one, regardless of his or her hinting preference, should be forced to not have agfa-fonts or the full complement of msttcorefonts installed in order to have menu fonts match among all gtk & qt applications. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.