Issue 59633 - Thai characters swapped when using change tracking
Summary: Thai characters swapped when using change tracking
Status: CLOSED DUPLICATE of issue 59630
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: regression
Depends on: 59659
Blocks: 41707
  Show dependency tree
 
Reported: 2005-12-21 08:50 UTC by samphan
Modified: 2006-01-02 12:21 UTC (History)
6 users (show)

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

Attachments
The writer file with a change record that will be displayed and accepted incorrectly (6.29 KB, application/vnd.sun.xml.writer)
2005-12-21 08:56 UTC, samphan 		no flags Details
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 samphan 2005-12-21 08:50:09 UTC 
I have problems using change tracking with Thai documents. I've made a smallest
sample that will show the problem.

- in a blank Writer document, type 'à¸à¸²à¸£à¸—ำงาน'
- Edit->Changes->Record
- between à¸à¸²à¸£ and ทำงาน, insert 'ได้'
- save the document (attached). In its contents.xml you'll see correctly :-
<text:p text:style-name="Standard">à¸à¸²à¸£<text:change-start
text:change-id="ct168685168"/>ได้<text:change-end text:change-id="ct168685168"/>
ทำงาน</text:p>

- open the document, make sure that Edit->Changes->Show is checked
- you'll see 'à¸à¸²à¸£à¹‰à¸”ไทำงาน'
- if you Edit->Changes->Accept or Reject, then accept the change, you'll get
that exactly incorrect text

This make the feature unusable for Thai.

I suspect this bug may be related to issue 59270 and issue 59630 but not sure.
Comment 1 samphan 2005-12-21 08:56:24 UTC 
Created attachment 32621 [details]
The writer file with a change record that will be displayed and accepted incorrectly
Comment 2 michael.ruess 2005-12-22 10:21:42 UTC 
Reassigned to SBA.
Comment 3 jack.warchold 2005-12-23 17:21:34 UTC 
it is duplicate to this issue

*** This issue has been marked as a duplicate of 59630 ***
Comment 4 jack.warchold 2005-12-23 17:22:21 UTC 
duplicate -> close
Comment 5 stefan.baltzer 2006-01-02 12:21:13 UTC 
SBA: Small correction: Duplicate of issue 59659
(of wich issue 59630 is a duplicate, too)