Bugzilla – Bug 160802
Tahoma ttf font looks ugly in OOo 2.0.2
Last modified: 2006-04-24 21:30:25 UTC
In Suse Linux 10.0 Beta 4 and more (didn't tested before Beta 4), Fonts looks horrible, ugly, awful (choose the correct term). Try this from KDE : install, for example, Tahoma font from MS (it work with other font of course). Then use this font as the default font for KDE, size 8 or 9. Exclude anti-aliasing from 8pt to 17pt. Go to "GTK Styles and Fonts" and choose this font for GTK apps. Then launch OpenOffice.org. In Options, Display, use the system font for UI, and choose to anti-alias fonts from 17 pixels. Click OK. Ho ! Horrible, awful. Look at the snapshot ! I put to compare : gFTP, OpenOffice.org and Control Center for KDE, just to compare UI fonts. It should be the Same ! Tried form Gnome, same result. I put a second snap from SUSE 10.0 and default OpenOffice.org 2.0 from install repository. It's perfect. So, it seems there is a very big problem with fonts in OpenOffice.org. It's the only app which seems to have this problem.
Created attachment 75019 [details] From Suse 10.1 Beta 8 and OpenOffice.org 2.0.2 : awful
Created attachment 75021 [details] Snap from SUSE 10.0 and OpenOffice.org 2.0 from SUSE : perfect
At least I made another test. I removed OOo 2.0 packages from SL 10.1 and installed OOo 2.0.2 (french version) downloaded from fr.openOffice.org. I have exactly the same result. Is freetype staticaly linked with OOo and bytecode interpreter disabled ?
I made some others tests. his time under Gnome. Same problem. To be sure, I installed an older OpenOffice.org (m125) : no problems ! Can you explain that ?
Ok, this patch seems to repair OOo 2.0.2 but expected only in OOo 2.0.3 ! I modified Product to SUSE Linux 10.1 because maintainer of OOo2.0 doesn't seem to read this issue. I repeat : OOo 2.0.2 is unusuable as is. Can you add this patch to your release ? http://qa.openoffice.org/issues/show_bug.cgi?id=61841 Thanks
committed fix to ooo-build-2-0-2 - it will miss RC1 I think though. Sebastian - I committed the up-stream patch; unfortunately for my Tahoma I get no better behavior :-) I guess this is simply because /etc/fonts/fonts.conf doesn't enable the bitmaps for that font - however; even poking at the XML that's supposed to enable that I get no joy so ...
We have now for RC1: ------------------------------------------------------------------- Wed Apr 5 19:11:06 CEST 2006 - pmladek@suse.cz - updated ooo-build to version 2.0.2.5: * use fontconfig to enable/disable bitmaps * pressing escape when context menu is displayed crasher ------------------------------------------------------------------- Fri Mar 31 14:22:43 CEST 2006 - pmladek@suse.cz - updated ooo-build to version 2.0.2.4: * import of VBA stream hangup * lots new constants for VBA excel * lots fixes in Atk bridge * i18n support within pasting to Calc * bin the obsolete LD_PRELOAD of libgcj [#153386] - added some NLD9 specific fixes (affects only build on NLD9): * marked the compat desktop files GNOME only * substituted the bin suffix in the compat desktop files * enabled openclipart * packaged missing directories So, can we mark this as FIXED?
No. I'm sorry to say that in OpenOffice.org 2.0.2-14 the problem is not fixed at all. Fonts looks ugly when anti-aliasing is disabled, exactly like when bytecode interpreter is disabled, and not only with tahoma...
Ok, I have some news. I made some tests with OOo 2.0.2 and fonts in SUSE 10.1 RC1. Of course I have the same problem. But it seems it occurs only with tahoma truetype font ! I tried with Arial, Verdana, Times New Roman, etc and it works perfecty. I also tried to desactivate font hinting in KDe control center : tahoma font then looks as ugly as in OpenOffice.org 2.0.2. So the problem is that font hinting is not enabled for OOo only for Tahoma. Any idea ?
This bug is related in OOO 2.0.2 issues as issue 62459 in openoffice.org bug database. http://www.openoffice.org/issues/show_bug.cgi?id=62459 No workaround at this time :( I'm searching for some references to tahoma fonts under VCL.xcu file from 00o 2.0.2 and compare it with the same file from 2.0.0/2.0.1 release. I'm also searching references to tahoma in source code. I'm surprised to see that I'm the only guy in bugzilla who has this problem !
Same issue here : https://bugzilla.novell.com/show_bug.cgi?id=163990
New tests this evening (in France). I made a backup of VCL.xcu ( in /usr/lib/ooo-2.0/share/registry/data/org/openoffice ) and copied here the VCL.xcu from OpenOffice.org 2.0.0. And it works ! So the issue is related to tahoma configuration under this file. I put theses two files in attachement.
Created attachment 78502 [details] CVL.xcu from OOo 2.0.0
Created attachment 78503 [details] VCL.xcu from OOo 2.0.2
Ooops... Bad idea. In fact I forgot to says "Use system font" to OOo. So VCL.xcu didn't made any change. I use Arial or verdana as replacement for Andale Sans UI. It works.
*** This bug has been marked as a duplicate of 118131 ***