Bug 133086

Summary:	freetype2 kerning failures
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Hans-Peter Jansen <hpj>
Component:	X11 Applications	Assignee:	Mike Fabian <mfabian>
Status:	RESOLVED FIXED	QA Contact:	Stefan Dirsch <sndirsch>
Severity:	Normal
Priority:	P5 - None	CC:	coolo, hpj
Version:	Final
Target Milestone:	---
Hardware:	i386
OS:	Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	This is rendered with freetype2-2.1.10 as delivered with 10.0. This is rendered with freetype2-2.1.9 on 10.0 enable kerning as noticed on freetype ML freetype2 20051119 cvs spec apiname patch

Description Hans-Peter Jansen 2005-11-09 20:27:57 UTC

While setting up 10.0 for an office environment I noticed ugly font rendering everywhere compared to 9.3, resulting from kerning failures. See attached sceenshots.

Investigating the issue, I came across this:
http://lists.nongnu.org/archive/html/freetype-devel/2005-09/msg00027.html

Unfortunately, changing this seems to not have any visual impact.

I recompiled freetype2-2.1.9 for 10.0, and the visual impression is back en par with 9.3 as expected. 

The changelog from 2.1.9 to 2.1.10 is pretty scary quantitatively, any ideas on how to get 2.1.10 play nicely?

Besides this, I noticed, that the bytecode interpreter is enabled again while deprecating it in the comment above. Consequently the related link
http://www.freetype.org/freetype2/2.1.3-explained.html is currently unavailable.

BTW: the 2.1.10 rpm changelog notes:
* Mon Jul 04 2005 - meissner@suse.de
- Use system zlib.

while freetype-2.1.10/include/freetype/config/ftoption.h says:
/* #define  FT_CONFIG_OPTION_SYSTEM_ZLIB */

Comment 1 Hans-Peter Jansen 2005-11-09 20:29:59 UTC

Created attachment 56884 [details]
This is rendered with freetype2-2.1.10 as delivered with 10.0.

Comment 2 Hans-Peter Jansen 2005-11-09 20:30:57 UTC

Created attachment 56885 [details]
This is rendered with freetype2-2.1.9 on 10.0

Comment 3 Hans-Peter Jansen 2005-11-09 20:33:32 UTC

Created attachment 56886 [details]
enable kerning as noticed on freetype ML

Comment 4 Hans-Peter Jansen 2005-11-20 21:52:26 UTC

Okay, forget about zlib note above: I noticed the config option in the make call.

Here's an update: I get the best result with current cvs freetype2, but had a hard time to get it going (because of missing symbols). Therefor I attach the spec and patch for those, who want to experiment themself. Feedback welcome.

Comment 5 Hans-Peter Jansen 2005-11-20 21:59:06 UTC

Created attachment 57819 [details]
freetype2 20051119 cvs spec

Comment 6 Hans-Peter Jansen 2005-11-20 21:59:39 UTC

Created attachment 57820 [details]
apiname patch

Comment 7 Mike Fabian 2006-04-24 16:47:17 UTC

I can see no differences whatsoever when applying a patch like the one in comment #3
to the freetype2 package currently in SuSE Linux 10.0 RC1.

When testing with a command like

    ftstring -m "VAea"  10 /usr/X11R6/lib/X11/fonts/truetype/arial.ttf &

kerning seems to work, and on top of that work exactly the same way with
and without that patch.

I.e. there seems to be nothing to fix for SuSE Linux 10.1 anymore.

Therefore I am closing this bug as FIXED (for SuSE Linux 10.1).