Bug 137854
Description
Nakai
2004-11-02 08:44:08 UTC
Created attachment 106062 [details]
A sample document, Red Hat Japan press release is pasted.
Created attachment 106079 [details]
Is this any better? It should be using Kochi Gothic now...
Created attachment 106081 [details]
an expected screenshot with Kochi Gothic
I just did select all and changed the font for those to Kochi Gothic.
Fix will be in 1.1.2-11 Comment #2: Yes, it seems to work. Great! Closing. Created attachment 108332 [details]
screenshot with OOo-1.1.2-17.6.EL4
Reopened. I tested OOo-1.1.2-17.6.EL4. and it breaks this fix again.
Created attachment 108333 [details]
Screenshot from fresh 2004-12-10 RHEL4 Desktop install with ttfonts-ja and OOo 1.1.2-17.6.EL4
Ok, regression is observed when ttfonts-zh_CN is installed and doc is viewed. Ok, the real issue here is that OOo is not recognizing the Kochi fonts (either Gothic or Mincho) as Japanese-enabled fonts, however since the zh_CN/zh_TW and Korean fonts have localized font names, OOo is able to detect that and prefers them to the non-localized "kochi" names. I'll have to look into how to detect coverage ranges from the font itself, but I don't think this can get done for RHEL4 GA. I lied, a fix will be in 1.1.2-18. 1.1.2-18.6.EL4 is in dist-4E Tested with 1.1.2-18.6.EL4, the attached document does not seems to be broken anymore. However, the font chosen for the display is not Kochi Gothic but MS font. Should it be using the Kochi Gothic font? Is this the acceptable behaviour? Yes, because it's an original font name which was used in the document. and OOo just use the Kochi font for the alternative font. Closing. |