Issue 1203 - Garbage display when inserting a special character before a normal word
Summary: Garbage display when inserting a special character before a normal word
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 638
Hardware: PC Windows ME
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: issues@www
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2001-07-11 11:40 UTC by issues@www
Modified: 2003-12-06 14:52 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2001-07-11 11:40:38 UTC
To simulate:

1. Run 627 in a CJK Windows. I use Chinese Windows Me.
2. Open Writer. Default font is set to "Times Roman New". Type in "Testing"
3. Position the cursor at the front of the word "Testing"
4. Insert symbol "beta", unicode code 0x00DF by select "Insert > Special 
Characters ..."
5. The beta symbol and letter "T" was intepreted as one CJK char and looks like 
garbage.

Winddows NT does not have this problem.
If you select the second character, "T" which is half char size of the garbage 
CJK character and change font to "Times New Roman" (actually it is already in  
Times New Roman and this action is somehow redundant), everything returns to 
normal.
Comment 1 stefan.baltzer 2001-07-24 09:41:21 UTC
Reassigned to Ulf.
Comment 2 ulf.stroehler 2001-09-28 19:00:37 UTC
Please verify again in 638 and comment. Thank you.
Comment 3 Unknown 2001-09-29 04:43:16 UTC
Verified.

The problem is still in 638. 
Comment 4 Unknown 2001-11-08 23:11:40 UTC
changing QA contact from bugs@ to issues@
Comment 5 ulf.stroehler 2001-11-09 14:23:20 UTC
I guess that this is a problem with weak characters. Weak characters
are those characters, which can not determined as CJK or western
characters (mostly symbols). To make a guess, which font has to be
used (CJK or a western one) OO examines the character before the weak
character (none in your case)and the installed Office language. In the
past we took also the character behind the weak character into
account. Please verify again in a forthcomming OO641 and comment, as
we changed a lot in this area. Thank you.
Comment 6 ulf.stroehler 2002-02-06 10:55:28 UTC
We reworked the concept for 'Weaks' completely. Please verify this
issue again (638 is somewhat outdated). Works for me.
Comment 7 Unknown 2002-02-16 10:42:47 UTC
Problem still exists in 641c
Comment 8 Unknown 2002-03-16 04:45:08 UTC
Reassign issue to owner of selected subcomponent
Comment 9 stefan.baltzer 2002-04-02 15:26:31 UTC
Ulf: I guess you should sort out what "L10N" and "I18N" data is involved. I guess that maybe the 
special treatment of certain characters is subject to this data. And as far as I know, these 
files have "dummy" contents in OpenOffice (until someone decides to fill it), therefore the 
behavior may differ from the current StarOffice. I may be on the wrong track, though... 
Reassigned.
Comment 10 prgmgr 2002-09-21 17:51:39 UTC
WaiTing, thanks for posting this issue.

Does this problem still exist in OOo 1.0.1?

Thank you for using and supporting OOo.
Comment 11 Unknown 2002-09-24 14:22:32 UTC
Repeat steps 1 to 5 as described in initial problem report. The 
characters "beta" and "Testing" are shown properly.

However, if we hightlight all characters and change the font to 
Arial, the first 2 chars will be misintepreted as a single Chinese. 
This problem remains even after we change the font back to Times 
Roman.

Comment 12 ulf.stroehler 2002-11-28 11:10:07 UTC
Pls. verify in OOo643. All prior versions lack a real l10n framework.
Comment 13 ulf.stroehler 2002-11-28 11:11:36 UTC
.
Comment 14 Unknown 2003-01-05 06:14:29 UTC
OO643C on Me is not stable. It crashed when I tried to repeat the 
test.
Comment 15 michael.bemmer 2003-03-24 11:57:26 UTC
Despite some reminders there is still no target milestone asigned. From the fact
that reporter and owner are identical we conclude information is missing that
doesn't allow working on this issue. That's why we've decided to close such
issues. This is done without invidually taking care of each issue. If you feel
this decision has been wrong regarding this specific issue, please re-open it.
Comment 16 michael.bemmer 2003-03-24 12:03:57 UTC
Despite some reminders there is still no target milestone asigned. From the fact
that reporter and owner are identical we conclude information is missing that
doesn't allow working on this issue. That's why we've decided to close such
issues. This is done without invidually taking care of each issue. If you feel
this decision has been wrong regarding this specific issue, please re-open it.
Comment 17 michael.bemmer 2003-03-24 12:11:35 UTC
Despite some reminders there is still no target milestone asigned. From the fact
that reporter and owner are identical we conclude information is missing that
doesn't allow working on this issue. That's why we've decided to close such
issues. This is done without invidually taking care of each issue. If you feel
this decision has been wrong regarding this specific issue, please re-open it.