Bug#320458: xlibs-data: ugly TTF rendering is an xserver-xorg/freetype bug
Package: xlibs-data
Version: 6.8.2.dfsg.1-9
Followup-For: Bug #320458
I agree with previous posters that this is an xserver-xorg bug, and
not an xlibs-data bug.
Cause of the bug: disabled bytecode interpreter in the xorg's own
freetype causes TTF's from msttcorefonts to be ugly-rendered for core
protocol clients like xemacs(xaw) or tkabber(tk).
How to verify:
According to the sources of libfreetype6, bytecode interpreter module,
"ttinterp.c" defines, among other things, symbol 'Interp'.
Doing "nm /usr/lib/libfreetype.a | grep Interp" shows that indeed it
does.
Now, let's check 'libfreetype6.a" from xserver-xorg:
"nm /usr/X11R6/lib/modules/fonts/libfreetype.a | grep Interp" show
that bytecode interpreter is not enabled/compiled in.
Then again, in the xserver-xfree from stable, bytecode interpreter is
present (check is the same as above). Thus, downgrade to
xserver-xfree86 from stable fixes the problem (I did exactly that).
Strange thing is, according to the file
./debian/tmp/usr/X11R6/lib/X11/config/xorgsite.def from the xorg's
source package, bytecode interpreter should be enabled. See line:
"#define Freetype2BuildDefines -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER"
However, for some reason this setting fail to propagate to proper
place during build stage.
It would be nice if this is fixed :)
TIA
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.4-1-686
Locale: LANG=ru_UA.KOI8-U, LC_CTYPE=ru_UA.KOI8-U (charmap=KOI8-U)
-- no debconf information
Reply to: