Issue 10537 - Roman and CJK Scripting Does not Change correctly when switching font selection.
Summary: Roman and CJK Scripting Does not Change correctly when switching font selection.
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 643C
Hardware: PC Windows 2000
: P2 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-01-09 02:18 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
2 users (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-01-09 02:18:38 UTC 
To simulate

1. Use Win2K with Chinese Traditional Language option installed via Control 
Panel > Global Settings"
2. Setup default Roman fonts in "Tools > Config > Roman Fonts"
3. Setup default CJK fonts in "Tools > Config > CJK Fonts"
4. Type in Roman Characters "test", the current font in the tool bar shows the 
correct default Roman font and script changed to Roman.
5. Toggle the Input Method Editor to enter Chinese characters. After the first 
character is entered, the current font in the tool bar shows the correct 
default CJK font and script changed to CJK.

Problem appears in the follow:

Replace Step 1 to 4.

5. Now change the current font setting to say "Arial" via the tool bar
6. Toggle the Input Method Editor to enter Chinese characters. After the first 
character is entered, the current font in the tool bar failed to change to 
default CJK font but shows "Arial", script is still Roman. Since Arial does not 
include CJK characters, the default glyph, an hollow square, appear.
Comment 1 h.ilter 2003-01-13 10:56:26 UTC 
Reassigned to US
Comment 2 ulf.stroehler 2003-02-14 17:31:39 UTC 
US->FME: I remember you (or was it Karl) fixed that some time ago, right?
Comment 3 frank.meies 2003-02-17 07:08:16 UTC 
FME->US: Fixed something similar with internal #104270#. But I cannot
reproduce this one with OOo643c.
Comment 4 prgmgr 2003-06-14 14:22:51 UTC 
Wai Ting, does this problem still exist with OOo 1.0.3.1 or OOo 1.1
Beta 2?
Comment 5 Unknown 2003-06-14 17:09:01 UTC 
It does not happen in OO 1.1beta2
Comment 6 prgmgr 2003-06-28 13:07:18 UTC 
.