From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98) BuildID: 00000000 - Bidi build dated 20010404 Arabic Unicode text is displayed disconnected (not properly shaped) in file Ken.htm Reproducible: Always Steps to Reproduce: 1.Open file Ken.htm Actual Results: Arabic text is displayed disconnected all in Middle character shapes Expected Results: View same file on IE5 for correct character shapes
focus on landing IBMBIDI without breaking Latin and CJK on moz0.9. move bidi functional bug to moz0.9.1
Target Milestone: --- → mozilla0.9.1
erik resign. reassign all his bug to ftang for now.
Assignee: erik → ftang
mark it as assign
Status: NEW → ASSIGNED
decommit other bidi issue until we land IBMBIDI default on.
reassign to email@example.com
Assignee: ftang → simon
Status: ASSIGNED → NEW
Changing QA contact to firstname.lastname@example.org.
QA Contact: andreasb → mahar
Ftang - Is this a beta stopper, or will Arabic support not be complete for nsbeta1?
Marking as nsbeta1-. Arabic support will not be in until M0.9.2 window
Keywords: nsbeta1 → nsbeta1-
Assigning M0.9.2 | P2. I think we need this for RTM.
Priority: -- → P2
Target Milestone: --- → mozilla0.9.2
Setting dependency on Shaping (82383) to have correct shaping and Bidi UI (85420) to set text type visual/logical for correct order.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Ftang - Does it look like Arabic will be supported in the final release?
I'm not sure why this has a milestone but is dependent on bugs that don't. Resetting component while I'm here.
Component: Internationalization → BiDi Hebrew & Arabic
Target Milestone: mozilla0.9.3 → ---
Mass-move all BiDi Hebrew and Arabic qa to me, email@example.com. Thank you Gilad for your service to this component, and best of luck to you in the future. Sholom.
QA Contact: mahar → zach
arabic contact to maha.
QA Contact: zach → mahar
Can someone confirm whether the testcase in attachment 48281 [details] is in fact valid? It seems to me that the characters are wrong in the source file. For example the word for "Arabic" in the "Native Language" column is always spelt with character FE90; ARABIC LETTER BEH FINAL FORM, but I believe it should be FE91; ARABIC LETTER BEH INITIAL FORM. Apart from that and some other cases, the display seems correct to me (tested on Bidi enabled and US Windows NT), and I think this can be marked FIXED.
True there are some characters having the wrong shapes, but this was not the problem reported. the output was displayed in a totally different manner than IE5 which was the reference in this case. IE5 handles UTF-8 as a visual charset. we need to define it as such. Adjusting dependency on 81664 to have correct display on Bidi & non-Bidi systems. Attaching a fix to define UTF-8 as visual charset.
Maha: This bug is separate from the problem with the ordering of UTF-8, which is bug 75004. That was closed as invalid after I commented: >The Arabic Hebrew and Farsi text in this example are in visual order (which is >incorrect for UTF-8) so Mozilla's behaviour here is correct. > >On selecting Bidi Options | Text Type | Visual, the text is displayed as >expected. > >The Arabic and Farsi are displayed correctly in IE5 because two errors are >cancelling one another out: the visual order and the fact that IE5 doesn't >classify Bidi characters in the FExx range as right-to-left. Note that the >Hebrew text is displayed reversed in IE5 and AFAIK there is no way in the UI to >correct this. Notice that UTF-8 pages with Arabic in the 06xx range are displayed as logical in both IE and Mozilla, for example http://www.unicode.org/iuc/iuc10/x-utf8.html
Simon, you are right, the example got me confused. As far as this bug is concerned we only need patch in bug# 81664 in order to have similar display on Bidi & non-Bidi systems. Please disregard the latest patch I attached. We also need the Bidi options present so we have correct display by forcing the TextType visual, adding dependency on #85420
Depends on: 85420
Kindly be informed that Ahmad A. Abu-Taha (firstname.lastname@example.org) from IBM Egypt is replacing Maha Abou El-Rous (email@example.com) in monitoring and receiving notifications of Mozilla bugs regarding Arabic.
No longer depends on: 85420
Resolving as INVALID given the comments above (and the fact that we no longer support Win98, and that if there ever was a real problem reported here, it's long gone).
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
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.