Issue 16124 - simplified and traditional chinese can't be both displayed
Summary: simplified and traditional chinese can't be both displayed
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC FreeBSD
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: ulf.stroehler
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-26 18:38 UTC by Unknown
Modified: 2003-08-27 17:55 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-06-26 18:38:27 UTC 
Calc in OOo1.1 Beta2 can only display the characters in the current locale.
At the same time it can't print (and export to pdf) those, too.

It does work with OOo 1.0.3, though.

I put an example sheet at http://www.roklein.de/example.sxc
(note: it uses the Arphic Kaiti M font in Big5 and GB charset)
Comment 1 oc 2003-08-08 15:05:51 UTC 
Hi Herbert, pleaase have a look
Comment 2 hdu@apache.org 2003-08-08 15:47:03 UTC 
When a font collection (*.ttc file) contains different styles or  
different fonts have the same font name but differently marked 
font file names (*zhs.ttf, *zht.ttf, *jan.ttf, *ko.ttf) then in it is true 
that we are choosing the one from the current locale. 
 
This is still necessary because the upper layers are not telling 
us yet which of the font styles to choose. When different fonts 
are used everything should (and does work here, including 
PDF). 
 
Can you attach the *pdf?
Comment 3 hdu@apache.org 2003-08-14 09:11:21 UTC 
HDU->US: Can you help me to recreate this?
Comment 4 Unknown 2003-08-21 13:00:01 UTC 
2 things:

a) the font names are different (the "GB" and "big5" ist part of the
font name).

b) I'm unable to recreate the problem anymore.  I've tried the last
couple of days..  I've got the sneaking suspicion I might have started
a _Linux_ version by accident, which then showed the problem described.

So, for now, I'm setting the issue to "INVALID".  

As I'm using the same files and fonts further, I'll see if the problem
arises again, and, if so, will try to give a better description and/or
example files.
Comment 5 ulf.stroehler 2003-08-27 17:55:06 UTC 
us->roklein: Thanks for your support.
Closing issue as "RESOLVED INVALID".