From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4.1) Gecko/20031114 Description of problem: OOo 1.1.1 has shown Japanese characters with Anti-Aliased font. it's really great. but some glyphs on GUI such as the menu and the dialog etc etc are missing so that OOo selects the wrong fonts to show the characters. it looks to me OOo is using Korean fonts to show Japanese. in fact when I removed ttfonts-ko package, OOo doesn't show Japanese anymore even if ttfonts-ja has been installed, and other xft-enabled applications show Japanese correctly. However when I change the applications font on gnome-font-properties from Sans to Kochi Gothic say, OOo can show Japanese properly without missing glyphs. Version-Release number of selected component (if applicable): openoffice.org-1.1.1-2 How reproducible: Always Steps to Reproduce: 1.run oocalc on LANG=ja_JP.UTF-8 2. 3. Actual Results: it looks like some glyphs are missing on the menu. Expected Results: the menu should be shown correctly Additional info: this problem happened on even rawhide tree. and I have tried this on 20040407 and 20040408.
Created attachment 99263 [details] a screenshot when OOo is ran normally
Created attachment 99264 [details] a screenshot, which should be shown(the applications font has been changed to Kochi Gothic)
*** Bug 123297 has been marked as a duplicate of this bug. ***
*** Bug 122216 has been marked as a duplicate of this bug. ***
Same problem for the zh_* locale as well.
Created attachment 100362 [details] Screenshot of oowriter in the zh_TW locale
Can you test with 1.1.1-5? It has fixes specifically for UI font in non-English languages.
All CJK have got the correct UI fonts in 1.1.1-5 now! Thanks! However Japanese font is revented to use bitmap again.
Dan, 1.1.1-5 looks better for CJK people, even if OOo uses the bitmap font again for Japanese. so could you push 1.1.1-5 for FC2 updates?
*** Bug 128134 has been marked as a duplicate of this bug. ***
I plan on building 1.1.2-5 for FC2, yes.
Saw 1.1.2-10 in fc2 updates. Thanks Dan. Closing this bug.