Bug 407826

Summary:	freetype subpixel hinting should be detected at runtime
Product:	[openSUSE] openSUSE 11.0	Reporter:	Anshul Jain <anshulajain>
Component:	KDE3	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium	CC:	anshulajain, wstephenson
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.0
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Screenshot of QT3 and QT4 apps

Description Anshul Jain 2008-07-10 05:45:37 UTC

The font rendering for QT4 apps on the KDE3 variant of Opensuse 11.0 is very poor. I've installed the subpixel enabled patches and it renders the QT3 applications very well. However, the QT4 apps (Yast) looks very very jagged and even after tweaking the settings through qtconf and selecting Tahoma fonts, it is definetly not rendered even correctly.

There is a bug report on Trolltech which says that Qt4 dosen't look for the subpixel patches at runtime...rather at build time and this is slated to be fixed for Qt 4.5. I have the Qt4.5 repo enabled to automatically update once the fix is released for Opensuse 11.0. Has this bug been fixed...or is there a workaround?

-Anshul

Comment 1 Will Stephenson 2008-07-11 15:16:28 UTC

Please attach a screenshot.

Comment 2 Mike Fabian 2008-07-11 17:19:43 UTC

> There is a bug report on Trolltech which says that Qt4 dosen't look
> for the subpixel patches at runtime...rather at build time and this is
> slated to be fixed for Qt 4.5.

Yes, see also bug #378801.

Comment 3 Anshul Jain 2008-07-14 12:22:31 UTC

Created attachment 227610 [details]
Screenshot of QT3 and QT4 apps

Comment 4 Anshul Jain 2008-07-14 12:23:54 UTC

Attached is a screenshot of my system with Qt3 apps perfectly subpixeled and Qt4 (Yast) dosen't pick up the rendering.

-Anshul

Comment 5 Mike Fabian 2008-07-15 12:53:21 UTC

Yes, this is really a duplicate of bug #378801.


*** This bug has been marked as a duplicate of bug 378801 ***