Bug 163990

Summary: OpenOffice doesn't use the font byte code even when enabled in /etc/sysconfig
Product: [openSUSE] SUSE Linux 10.1 Reporter: Philipp Wollermann <philipp>
Component: OpenOffice.orgAssignee: Jan Holesovsky <kendy>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None CC: suse-beta
Version: Beta 9   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot showing the wrong font rendering in OO.org

Description Philipp Wollermann 2006-04-06 08:02:21 UTC 
I use the MS Webfonts (Verdana, etc.) and Tahoma in my KDE system and configured BYTECODE_BW_MAX_PIXEL = 18 with the yast /etc/sysconfig editor. Anti-aliasing is still enabled in KDE, I told OpenOffice to anti-alias the fonts beginning with font-size 18 pixels and higher. The fonts look perfect now in KDE and all apps, but OpenOffice does not use the byte code interpreter, so the menu fonts look very pixeled. The fonts in the document view are rendered correctly. I attached a screenshot. I'm running current factory.
Comment 1 Philipp Wollermann 2006-04-06 08:04:11 UTC 
Created attachment 76809 [details]
Screenshot showing the wrong font rendering in OO.org
Comment 2 Petr Mladek 2006-04-06 13:05:17 UTC 
It looks like a problem with KDE integration. Kendy, could you look at it?
Comment 3 Jan Holesovsky 2006-04-06 14:55:04 UTC 
Hmm, will try.

Reference: http://en.opensuse.org/Optimal_Use_of_Fonts_on_SuSE
Comment 4 Sebastien ROHAUT 2006-04-14 09:09:10 UTC 
Oh this issue seems to be the same :

https://bugzilla.novell.com/show_bug.cgi?id=160802
Comment 5 Michael Meeks 2006-04-28 10:35:06 UTC 
A dup sadly, if the font rendering infrastructure could do a better job of keeping metrics intact while changing various properties like this - life would be good.

*** This bug has been marked as a duplicate of 118131 ***