Bug 102351
Summary: | [RHEL3 update] substitute font isn't correct anymore | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Akira TAGOH <tagoh> | ||||||
Component: | openoffice.org | Assignee: | Dan Williams <dcbw> | ||||||
Status: | CLOSED ERRATA | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3.0 | CC: | eng-i18n-bugs | ||||||
Target Milestone: | --- | Keywords: | i18n | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | openoffice.org-1.1.2-21.2.EL3 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2005-04-26 06:49:38 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: | 101028 | ||||||||
Attachments: |
|
Description
Akira TAGOH
2003-08-14 08:40:50 UTC
doh, correctly we just need to add the substitute font for Laxi Sans so that it's a default font for us right now. should we substitute "Nimbus Roman No9 L" because it is our body default text? However OO 1.0 has the problem that if we substitute single width font to double width font, the width of substitute will not be correct. However OO 1.1 solved the problem on that. Are we planning to update that in either release? Well, I've added the substitute entry for Nimbus Roman No9 L, it helps to show the Japanese characters then. but it seems that the printing doesn't work on this. Does the japanese display after substitution looks only to you? I checked and ja glyphs to me is sort of clumped together because the width is not correct. This problem still appears on RHEL3. However OOo 1.1 fixed a lot. except oocalc. if I type Japanese on oocalc, oocalc shows Japanese as the empty square. changing the font to the appropriate one is always required to show Japanese on oocalc. You're saying that Japanese looks like little squares in the document, but that the UI font is correct? What font would you suggest should be the default font for Japanese locales using RHEL 3 with OOo 1.0? Thanks, Dan Created attachment 96824 [details]
Screenshot for oocalc with Japanese locale
Created attachment 96825 [details]
Screenshot for oowriter with Japanese locale
Well, yes. I've attached the screenshot. you can know the problem what happened on Japanese locale. I would explain some stuff. - oowriter Actually I type Japanese on oowriter, but it looks like the space. though this problem is fixed in 1.1.x, what the freak on Japanese, Nimbus Roman No9 L doesn't have Japanese glyphs. so if we can't upgrade OOo to 1.1.x for RHEL3, we will have to make a substitute font for Nimbus Roman No9 L to Kochi Mincho. - oocalc As I said this problem still appears on even 1.1.x, because the default font doesn't have Japanese glyphs. also the default font can't be changed easily by the configuration. OO 1.1.1 fixed on the oocalc problem as well. Let me know if you guys have any plans on building 1.1.1 on future RHEL3 updates. Otherwise this bug can be closed. We should be able to fix this with RHEL3 U4 Does this still happen for 1.1.2 in FC3? That's probably what will get released for RHEL3 at some near future point... For japanese: # LANG=ja_JP.UTF-8 oowriter + The substitute font is good. It able to substitute as soon as it starts # LANG=ja_JP.UTF-8 oocalc - It does not have substitute font at start up (Using Nimbus Sans L) # LANG=ja_JP.UTF-8 impress + The substitute font is good. It able to substitute as soon as it starts oocalc still not very ideal for international users. Tested with openoffice.org-1.1.2-21.2.EL3, this has been fixed. Tried on all CJK locales. Fixed in: RHEL3: 1.1.2-22.2.2.EL3 An advisory 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/RHSA-2005-375.html |