Issue 17404 - Traditional Chinese Characters cannot be properly appeared in 'Load URL' and 'Font Name' in Toolbars
Summary: Traditional Chinese Characters cannot be properly appeared in 'Load URL' and ...
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC2
Hardware: PC Windows 2000
: P3 Trivial with 2 votes (vote)
Target Milestone: OOo 1.1.4
Assignee: stefan.baltzer
QA Contact: issues@gsl
Keywords: oooqa
: 32381 (view as issue list)
Depends on:
Reported: 2003-07-25 14:43 UTC by ykliang
Modified: 2005-02-10 15:26 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Screen shot (69.66 KB, image/jpeg)
2004-03-29 04:31 UTC, chanls
no flags Details
Screenshot: A Japanese font name is partly corrupted (33.65 KB, image/jpeg)
2004-05-08 22:54 UTC, tuomo
no flags Details
Screenshot: In the dropdown list, Japanese font names are displayed (38.13 KB, image/jpeg)
2004-05-08 22:57 UTC, tuomo
no flags Details
Screenshot: Japanese fonts displayed as unreadable squares in Option (59.01 KB, image/jpeg)
2004-05-10 15:09 UTC, tuomo
no flags Details
chinese and korean UI fontlist (5.78 KB, application/vnd.sun.xml.writer)
2004-08-02 08:36 UTC, stephan_schaefer
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ykliang 2003-07-25 14:43:28 UTC
Traditional Chinese Characters cannot be properly appeared in 'Load URL' and
'Font Name' in Toolbars.
Comment 1 mci 2003-09-16 11:38:23 UTC
reassigned to

@us: Hi us, i think this is something for you... :)
Comment 2 stefan.baltzer 2003-10-23 15:05:04 UTC
SBA-> Yu-Kang: 
(1) What IME do you use?
(2) Please be more specific than "not properly". Maybe a screenshot
can help. Thank you.
Target set to OOo 2.0.
Comment 3 chanls 2004-03-29 04:31:48 UTC
Created attachment 14134 [details]
Screen shot
Comment 4 chanls 2004-03-29 04:34:54 UTC
I experience the same problem with OOo 1.1.1 RC3.  The Chinese font name cannot
be displayed properly in the main screen.  I use Windows XP and Chinese (Taiwan)
is set for the language of non-unicode program.

I attached a screen shot as a reference.
Comment 5 tuomo 2004-05-08 22:52:45 UTC
I've got a problem that is apparently related to this.

With 1.1.2rc on Windows XP Japanese version, Japanese (kanji) font names are
broken in the box on the object bar. Non-ascii characters look like meaningless
squares. I suspect the same phenomenon exists about Chinese and Korean font names.

When I click the box, I can see and select Japanese font names in the dropdown
list that are correctly displayed. Inputting with Japanese fonts by Windows IME
and selecting/changing fonts are OK. 

This may be not a critical issue, but correct displaying of font names on top
would be more user-friendly to handle Japanese documents. 

The current Japanese localized build of 1.1.0 doesn't have this issue.
Comment 6 tuomo 2004-05-08 22:54:43 UTC
Created attachment 15096 [details]
Screenshot: A Japanese font name is partly corrupted
Comment 7 tuomo 2004-05-08 22:57:28 UTC
Created attachment 15098 [details]
Screenshot: In the dropdown list, Japanese font names are displayed
Comment 8 tuomo 2004-05-09 21:55:54 UTC
Though this font issue has been categorized into sw component, it appears not
only in Writer but also in Calc and Impress. I think it should be considered as
a generic user interface problem of OOo.
Comment 9 lohmaier 2004-05-09 22:55:52 UTC
The problem is the font used for the user-interface that doesn't contain the
necessary glyphs/characters.

Go to Tools|Options -> OOo -> Fonts, check [x] apply replacement table and
replace "Andale Sans UI" (type that in since it probably won't be in the list of
available fonts) by a font of which you know that it contains the necessary
glyphs and choose [x] always.

You may as well try the option "use system font for user interface"
(Tools|Options -> OOo -> Accessibility) before setting up the fontreplacement.

The localized version of OOo probably doesn't show this problem because OOo
tries some other fonts first. (The list of fonts and the order in which they are
checked is defined in share/registry/data/org/openoffice/VCL.xcu)

The replacement is intended to be locale-dependant (but apparently this doesn't
work properly in this case). (Perhaps this even is not possible on windows?-
don't know)

At leas on linux one of these fonts will be used for the UI for zn_TW:
Andale Sans UI;AR PL Mingti2L Big5;AR PL KaitiM Big5;PMingLiU;MingLiU;Kai;Arial
Unicode MS;Ming;gnu-unifont;Interface User;WarpSans;Geneva;Tahoma;MS Sans
System;Sans Serif
(These are the fonts that OOo should try for chinese taiwan (zn_TW) - but you
write that chinese_Taiwan is set for non-unicode programs, so OOo might not be
aware of that? - I don't know how locales work on windows)

anyway, the problem is not the input or working with these characters, but the
UI-Font. reassigning to gsl
Comment 10 tuomo 2004-05-10 15:08:00 UTC
tuomo->cloph: I appreciate your detailed instruction. That helped me a lot.

To my surprise, just one click to check "Use system font for user interface"
resolved the problem. I wish this option would be on by default, unless there
are any side effects.

The issue could be also worked around by applying replacement table, but I had
difficulty selecting a proper font while Japanese font names were displayed as
unreadable squares in the list. This behavior differs from the font list on the
object bar, which is displayed well.
Comment 11 tuomo 2004-05-10 15:09:02 UTC
Created attachment 15128 [details]
Screenshot: Japanese fonts displayed as unreadable squares in Option
Comment 12 lohmaier 2004-05-13 22:21:37 UTC
The problem in the replacement-list is the same issue - the display-font doesn't
contain the necessary characters.
Comment 13 tuomo 2004-05-31 13:34:53 UTC
I've learned in the comments on issue 16683 that the system UI font will be used
by default in OOo 2.0. If I understand correctly, the UI font change is expected
to fix this issue, too.
Comment 14 ulf.stroehler 2004-07-20 18:31:33 UTC
US->SSA: I guess we should enhance the VCL.xcu about native font name entries as
we did for the japanese OO.o users group.
For OO.o 2.0 the "Use desktop font" is set to default, which circumvents most of
the problems but for the 1.1.x time frame the community would still have to live
with this uggly representation.
Would this be feasible to fix for you in a 1.1.3 time frame?

@submitter: could you support development and provide a list of native chinese
font names with their corresponding western name. Preferred in an OO.o text
document file (*.sxw) and attach it to this issue? Thanks in advance for your
Comment 15 stephan_schaefer 2004-08-02 08:36:49 UTC
Created attachment 16877 [details]
chinese and korean UI fontlist
Comment 16 stephan_schaefer 2004-08-02 08:47:21 UTC
ssa->hdu: please add the attached localized UI fontnames to VCL.xcu
Comment 17 ulf.stroehler 2004-08-02 11:01:53 UTC
*** Issue 32381 has been marked as a duplicate of this issue. ***
Comment 18 2004-08-19 16:25:44 UTC
Ok, in thevclppbugs6 these localized names were added to VCL.xcu's default font
zh-cn: 宋体 (SimSun) 新宋体 (NSimSun)
zh-tw: 新細明體 (PMingLiU) 細明體(MingLiU)
ko-kr: 굴림 (Gulim) 굴림체 (GulimChe)
Comment 19 ulf.stroehler 2004-09-03 14:00:26 UTC
Adjusting target.
Comment 20 2004-09-17 08:00:44 UTC
reopening for reassignment
Comment 21 2004-09-17 08:01:20 UTC
Comment 22 2004-09-17 08:02:14 UTC
hdu->sba: please verify in cws vclppbugs6
Comment 23 stefan.baltzer 2004-10-01 10:18:51 UTC
SBA: Verified in CWS vclppbugs6.
Comment 24 2004-11-01 02:47:41 UTC
Add hli in cc list .
Comment 25 stefan.baltzer 2005-02-10 15:26:17 UTC
SBA: OK in 680m78. Closed.