Bug 57860

Summary:	qt 3.1.x vs XFree 4.3 Truetype support - workaround
Product:	[Unmaintained] kdelibs	Reporter:	J <info>
Component:	qt	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description J 2003-04-29 22:05:31 UTC

Version:           qt 3.1.2-21 (using KDE KDE 3.1.1)
Installed from:    SuSE RPMs
OS:          Linux

At least in Suse8.2 Truetype rendering is broken. The problem does show up even without kde, just call qtconfig and see ugly glyphs (needs good LCD display > 15" and better turn anti-alias off). It is possible to overcome the problem (I use qt 3.1.2-21 since a while) ...

In /etc/X11/XF86Config change

from: Load "freetype"
to:     Load "xtt"

This works fine when a new KDE profile is created. 

AN OLD TRUETYPE RELEATED KDE BUG:

If you have an old profile you may need to edit kdeglobals (and/or other config files) manually: search for entries like "Arial [xxxx]", delete them and reconfigure KDE with kconfig. The [xxxx]  suffixes to font names seem to be vendor names and can cause lots of trouble and maybe they even are a design problem of XFree/Qt/KDE.

Why shouldn't users reconfigure their X-Server without causing the KDE configuration to be broken?

Comment 1 J 2003-04-30 10:15:35 UTC

Sorry, I forgot to say that you should delete the ~/.qt folder because qt seems to 
remember some font-settings and gets confused after reconfiguring the X-Server.

Comment 2 J 2003-06-06 21:43:18 UTC

The SuSE font rendering problem is probably gone afterr installing in X-libs update 
from SuSE's online-update service. 
 
The [xxx] font vendor is still a problem. My X-Font-Server (KDE 3.1.1) for expample 
has the same font-file exported as Wingdings [misc] whereas on my local machine 
(KDE 3.1.2) the name is Wingdings [Microsoft].

Comment 3 Dirk Mueller 2003-06-09 22:53:29 UTC

yeah, unfortunately this changed in an incompatible way with Qt 3.1. not much 
we can do about it anymore :(