The fontconfig patch from Fedora still doesn't fix the problem. I tried that. It seems that somehow, even with the bytecode interpreter turned on in libfreetype6 (as it is in Debian/Ubuntu), OO doesn't use it. I had looked at this in some depth but the water went over my head and I gave up the hunt, just wasn't proving worth the time. So...
I punted and just force-downgraded all the OO packages to 2.0.2-2ubuntu12 (from Dapper) and also pulled libfreetype6_2.1.10-1ubuntu2.2_i386.deb from pool, used ar and tar to extract the contents of ./usr/lib, and moved the library and link to /usr/lib/openoffice/program (mv ./usr/lib/*). This effectively gets my OO from Dapper with the freetype2 library from Dapper (2.1.10). The fonts are now rendered EXACTLY the same as in gedit, nautilus, mozilla, etc. They just look perfectly beautiful again. This problem sure behaves like an interaction problem between the new 2.2.1 freetype2 library and how OO uses it. Seems like the bytecode interpreter is /never/ used, and I just couldn't spend the time to figure it out. PS: I do not use anti-aliasing, I really hate the way that makes clean fonts (like Arial) look fuzzy. -- [Edgy] font hinting does not work with libfreetype6 v. 2.2.1 https://launchpad.net/bugs/54776 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
