Bug#188928: openoffice.org uses the bytecode interpreter for antialiasing.

[Maurizio Colucci <seguso.forever@tin.it>]

Package: openoffice.org


BACKGROUND:

The Debian libfreetype6 package activates the bytecode interpreter at
compile time. This results in better font rendering when antialiasing
is disabled, and worse rendering when antialiasing is enabled. The
alternative is to disable the interpreter and to enable the autohinter
module, which is better with antialiased fonts.

Since I use antialiasing, I have disabled the bytecode interpreter in
freetype2, by editing /etc/fonts/local.conf.


THE PROBLEM:

 This works in KDE but not in openoffice, which is still using the
bytecode interpreter. I guess this is because openoffice was linked
statically with libfreetype.so.6.3.3, which had been compiled with the
interpreter activated.

REQUEST:

I would like to be able to use openoffice with autohinting
(i.e. without the bytecode interpreter).

SUGGESTED FIX:

Maybe you could link dynamically to libfreetype.so.6.3.3, in order to
let me choose whether to use the autohinter or the interpreter?

It would be nice if debconf asked me whether I want to use the
bytecode interpreter or the autohinter.

Maurizio