Issue 53590 - Asian font names not displayed with original font in font name display pane
Summary: Asian font names not displayed with original font in font name display pane
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-08-22 00:43 UTC by yukikawara
Modified: 2013-02-07 22:03 UTC (History)
4 users (show)

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


Attachments
Document formatted with OO 1.1.3 using a Japanese font name. (SBA, tell me a way I can send the font I've used. You'll then note that it reproduces bug #53806, too (unlike the other Japanese fonts I have)) (5.53 KB, application/vnd.sun.xml.writer)
2005-09-28 05:58 UTC, yukikawara
no flags Details
Document formatted with OO 1.1.3 using a Japanese font name. (SBA, tell me a way I can send the font I've used. You'll then note that it reproduces bug #53806, too (unlike the other Japanese fonts I have)) (5.53 KB, application/vnd.sun.xml.writer)
2005-09-28 06:13 UTC, yukikawara
no flags Details
Document formatted with OO 1.1.3 using a Japanese font name. (SBA, tell me a way I can send the font I've used. You'll then note that it reproduces bug #53806, too (unlike the other Japanese fonts I have)) (5.53 KB, application/vnd.sun.xml.writer)
2005-09-28 06:13 UTC, yukikawara
no flags Details
Screenshots showing display in different OOo versions and applications (193.61 KB, application/vnd.oasis.opendocument.graphics)
2007-01-21 15:29 UTC, Rainer Bielefeld
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description yukikawara 2005-08-22 00:43:16 UTC
Japanese fonts are no more displayed with their Japanese names in the font list;
only with their roman letter ones. I've labeled it as a defect because it's a
degression from version 1.1.3. The names were then displayed twice - one in
roman letters and one in Japanese, for every Japanese font, even with the l10n
French pack as the only one installed.

I don't know if the problem is linked, but one of these fonts right now falls
back to the system's default font in the list and when applied to some text. It
wasn't doing that with version 1.1.3. I suppose that if there was a Japanese
font that doesn't have an English name entry (but only a Japanese one),
OpenOffice would be quite confused on how to call it now...

This happens under locale ja_JP.UTF-8, by the way.
Comment 1 stefan.baltzer 2005-08-22 10:23:23 UTC
SBA->yukikawara: Please attach the font in question or (if it is several
megabytes) insert a link where it can be downloaded from. Thank you.

Set keyword "needmoreinfo".
Comment 2 stefan.baltzer 2005-08-22 10:25:39 UTC
SBA-yukikawara: ...and please tell more about the Linux system you use. Thank you.
Comment 3 yukikawara 2005-08-26 01:00:00 UTC
sba->  pelase see bug #53806, that I just filed in. I think the problem might
not be linked, after all.

But this one still remains... Have I given enough information for it ?

I have just tried installing other fonts; MS Gothic and MS Mincho still have
their name twice (one with roman letters, the others with Japanese characters),
but all the other Japanese fonts now only have the roman name, which sometimes
isn't precise enough for the Japanese to understand what font it actually is.
(Example : Hiragino Mincho W8 (weight 8, japanese name) gets displayed as
"HiraginoMin") It's too bad, OpenOffice was the only Linux software I've found
so far that had a step forward for that.
Comment 4 yukikawara 2005-09-20 19:30:06 UTC
I really think this should be fixed for the next release.

All documents I made with version 1.1.3 have their font formatting gone in the
2.0 Beta, because I used Japanese font names. I need to format them again :(
I think the common Japanese user is going to be pissed off by this...
Comment 5 stefan.baltzer 2005-09-23 12:46:08 UTC
SBA->yukikawara: Please attach a document that shows the symptom. Thank you.
I put HDU on c/c.
Comment 6 yukikawara 2005-09-28 05:24:13 UTC
sba (or hdu), I don't think the document alone would be of any help since you
don't have the Japanese font in question... Can I send the font to you by email
? (It's too big to make an attachment...)
Comment 7 yukikawara 2005-09-28 05:58:02 UTC
Created attachment 29956 [details]
Document formatted with OO 1.1.3 using a Japanese font name. (SBA, tell me a way I can send the font I've used. You'll then note that it reproduces bug #53806, too (unlike the other Japanese fonts I have))
Comment 8 yukikawara 2005-09-28 06:13:53 UTC
Created attachment 29957 [details]
Document formatted with OO 1.1.3 using a Japanese font name. (SBA, tell me a way I can send the font I've used. You'll then note that it reproduces bug #53806, too (unlike the other Japanese fonts I have))
Comment 9 yukikawara 2005-09-28 06:16:18 UTC
Ouch, sorry for this... The server went on a 505 mood...
Comment 10 yukikawara 2006-01-14 17:22:47 UTC
Is this bug ever going to get considered ?

sba or HDU, I'm just waiting for your blessing to send you the problematic
Japanese font (which also produces bug #53806).
Comment 11 Rainer Bielefeld 2007-01-21 15:26:34 UTC
I checked with "1.1.4 (German) WIN XP: [645m52 (Build 8824)]" and found no
problem at all.

I checked with "2.0.2  German version WIN XP: [680m5(Build9011)]" and can
confirm the problem. Not only Japanese, but generally Asian fonts seem to be
affected; I tested with attachment for  Issue 53593.
It's not only a WRITER problem, you see the malfunction also in other OOo
applications CALC, DRAW, IMPRESS (pls. see screenshots!).

I checked with "2.1.0  German version WIN XP: [680m6(Build9095)]" and found,
that the font name display works better, but not always correctly  (pls. see
screenshots!).
Comment 12 Rainer Bielefeld 2007-01-21 15:29:00 UTC
Created attachment 42358 [details]
Screenshots showing display in different OOo versions and applications
Comment 13 Raphael Bircher 2011-10-04 22:21:43 UTC
Assigned the issue to the default contact

rbircher > sba: feel free to reassigne it to your self.

As I read in the comments, the problem seems still alive. The Bug is priorised as P4, so it seems not so a bad issue.