Issue 16247 - incurrect handling of netutal characters next to LTR characters, when reading MS word RTL document
Summary: incurrect handling of netutal characters next to LTR characters, when reading...
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: BiDi (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-30 14:43 UTC by sforbes
Modified: 2013-08-07 15:00 UTC (History)
2 users (show)

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

Attachments
Original word 2000 document (44.50 KB, application/octet-stream)
2003-06-30 14:43 UTC, sforbes 		no flags Details
Screen shots of the currect charachter display in word 2000 (11.70 KB, application/octet-stream)
2003-06-30 14:45 UTC, sforbes 		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 sforbes 2003-06-30 14:43:17 UTC 
when reading MS word RTL document, there is incurrect handling of netutal
characters next to LTR characters.

* Parentasis next to LTR characters incorrectly flip position
* 2 LTR string seprated by an underscore (_) switch positions.

Please see attached documents
Comment 1 sforbes 2003-06-30 14:43:49 UTC 
Created attachment 7262 [details]
Original word 2000 document
Comment 2 sforbes 2003-06-30 14:45:02 UTC 
Created attachment 7263 [details]
Screen shots of the currect charachter display in word 2000
Comment 3 Dieter.Loeschky 2003-08-14 13:17:55 UTC 
DL->FME: Could you please takeover?
Comment 4 sforbes 2003-08-15 02:00:12 UTC 
mehlng added to the cc list
Comment 5 frank.meies 2003-08-15 07:19:06 UTC 
FME->Shoshannah: I cannot reproduce the '_' issue with a current m15.
But I'm quite sure that the paranthesis issue is duplicate to #i18024#
(could you please check this?).  In this case we should close this
issue and only use #i18024#, because there already is some valuable
input from mehlng in #i18024#.
Comment 6 mehlng 2003-08-15 10:36:53 UTC 
I couldn't recreate the ENGLISH_ENGLISH issue as well.
Set as a dupe of my General comment.

*** This issue has been marked as a duplicate of 18024 ***
Comment 7 frank.meies 2003-08-15 11:10:36 UTC 
FME->US: Please verify if we should close this.
Comment 8 sforbes 2003-08-26 09:38:24 UTC 
english_english is indeed fixed in rc3.
closing bug
Comment 9 sforbes 2003-08-26 09:38:42 UTC 
.