Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 118874

Summary: Oo.o using bitmap font for Japanese
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: openoffice.orgAssignee: Dan Williams <dcbw>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: eng-i18n-bugs, wtogami
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.1.1-1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-12 17:07:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 114963    

Description Jens Petersen 2004-03-22 04:56:14 UTC
Description of problem:
Ssia pretty much.  The Japanese menubar in Oo.o apps seems
to be using a bitmap font, it would be really nice if it
could be improved to use a TT or AA font

Version-Release number of selected component (if applicable):
1.1.0

Comment 1 Jens Petersen 2004-03-22 07:59:34 UTC
So actually not just the menus but all Japanese text is in bitmap.

Comment 2 Jens Petersen 2004-04-07 01:45:49 UTC
Appears to be fixed in openoffice.org-1.1.1-1, thanks. :-)

Comment 3 Jens Petersen 2004-04-13 06:47:42 UTC
Erm, sorry that was probably a little premature: there are
problems with missing glyphs in the menus... tagoh said
something about it might be using a Korean font or something
for katakana.

eg: Insert(I) menu appears as "å¥(I)" instead of "æ¿å¥(I)",
and Tools(T) appears as "ãã«(T)" instead of "ãã¼ã«(T)".

So something seems to be wrong.

Comment 4 John Flanagan 2004-05-12 17:07:16 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-189.html