After some investigation and reading Comments on Debian-Bug-Report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385798 it seems like openoffice simply is always using freetype-autohinter instead of respecting fontconfig-settings.
Turning on autohinter in ~/.fonts.conf causes, that GNOME-Apps and OOo are looking the same when using new freetype (but worse as if bytecode-interpreter is enabled).
So it seems like old freetype-lib in combination with openoffice uses bytecode-interpreter, new freetype not (why, I don't know).
After some investigation and reading Comments on Debian-Bug-Report http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 385798 it seems like openoffice simply is always using freetype-autohinter instead of respecting fontconfig- settings.
Turning on autohinter in ~/.fonts.conf causes, that GNOME-Apps and OOo are looking the same when using new freetype (but worse as if bytecode- interpreter is enabled).
So it seems like old freetype-lib in combination with openoffice uses bytecode- interpreter, new freetype not (why, I don't know).