Bidi: Kashida, Arabic colon causes 2000 to reverse the string

RESOLVED FIXED

Status

()

Core
Layout: Text
RESOLVED FIXED
17 years ago
10 years ago

People

(Reporter: Maha Abou El-Rous, Assigned: smontagu)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
BuildID:    00000000 - Bidi build dated 20010404

Bidi: When a Arabic visual (FE range characters) htm is displayed on Windows 
2000 and windows NT having a 06 character such as kashida or Arabic semicolon, 
Shaddah in it, the system does some bidi processing to the string which then 
changes it correct order.

Reproducible: Always
Steps to Reproduce:
1.Open file cp864.htm
2.check out on of the words with Shaddah in.

Actual Results:  the order of the word with Shaddah character is mixed up

Expected Results:  the word should read correctly. You can view that by setting 
Mozilla clipboard mode to logical and copy that word, then paste it in Notepad.

Need to insert Right-to-Left markers before those characters in the buffer, to 
force their correctc display on Win2000 and NT
(Reporter)

Comment 1

17 years ago
Created attachment 29982 [details]
Visual LTR Arabic HTM
(Reporter)

Comment 2

17 years ago
Created attachment 29983 [details]
Visual LTR Arabic HTM

Comment 3

17 years ago
maha: could you make two screen shot, one with correct, one with the actual 
result?
bidi functional bug, move to moz0.9.1
Target Milestone: --- → mozilla0.9.1

Comment 4

17 years ago
after talk to maha, we decide to change the 864 to unicode converter to solve 
this issue
We need to add 200E before the following code point

E0
AC
B0-B9
BB

Comment 5

17 years ago
I need to rewrite the converter, I cannot use the current .ut mechanism to do 
that. 
Assignee: erik → ftang
(Reporter)

Comment 6

17 years ago
Created attachment 31762 [details]
conversion table from 864 to Unicode presentation range (FE)
(Reporter)

Comment 7

17 years ago
Attached file cp864.cpg, which contains the conversion table from 864 to Unicode
FE range
(Reporter)

Comment 8

17 years ago
Frank, please add the following code points to your list that also need the 200E
character inserted before them. (the code points are in 864)
0x25
0xbf

Comment 9

17 years ago
mark it as assign
Status: NEW → ASSIGNED

Comment 10

17 years ago
decommit other bidi issue until we land IBMBIDI default on.

Updated

17 years ago
Target Milestone: mozilla0.9.1 → ---

Comment 11

17 years ago
reassign to simon@softel.co.il
Assignee: ftang → simon
Status: ASSIGNED → NEW

Comment 12

17 years ago
Changing QA contact to mahar@eg.ibm.com.
QA Contact: andreasb → mahar

Comment 13

17 years ago
Move to "Bi-Di: Arabic/Hewbrew"
Component: Internationalization → BiDi Hebrew & Arabic

Comment 14

17 years ago
Mass-move all BiDi Hebrew and Arabic qa to me, zach@zachlipton.com. 
Thank you Gilad for your service to this component, and best of luck to you 
in the future.

Sholom. 
QA Contact: mahar → zach

Comment 15

17 years ago
Assigning Arabic bug back to mahar:

mahar@eg.ibm.com

Zach, in future, please re-aasign Arabic specific bug to her. You should
keep Hebrew or Bidi bugs.
QA Contact: zach → mahar

Comment 16

17 years ago
the patch in bug 81664 solves this problem as it handles FE & 06 characters 
seperately and thus at one point of time there is only one type of string sent 
for display (either FE or 06).
Depends on: 81664
(Assignee)

Comment 17

17 years ago
Maha, please resolve this bug if it is fixed in current trunk builds.

Updated

17 years ago
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 18

17 years ago
Bug fixed

Updated

10 years ago
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: mahar → layout.fonts-and-text
You need to log in before you can comment on or make changes to this bug.