Closed Bug 75047 Opened 24 years ago Closed 17 years ago

Bidi: LamAlef ligature from 864 to 06 range

Categories

(Core :: Layout: Text and Fonts, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mrous, Assigned: smontagu)

References

Details

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98) BuildID: 00000000 - Bidi build dated 20010404 Bidi: LamAlef converts to one character only from 864 to 06 range. It should be two characters Reproducible: Always Steps to Reproduce: 1.Open an Arabic visual file with LamAlef in the text 2.Force the text type to be Logical Actual Results: the lamAlef ligature becomes only Lam character Expected Results: It should convert to two characters Lam and Alef.
please include test cases and two screen shot bidi functional bugs, move to moz0.9.1
Target Milestone: --- → mozilla0.9.1
after talk to maha, we decide to fix this by change 864i to unicode converter. We need to map the following characters to two unicode F8 to 0x644 0x622 F9 to 0x644 0x622 99 to 0x644 0x623 9a to 0x644 0x623 9d to 0x644 0x627 9e to 0x644 0x627
I need the origional mapping table. I need to rewrite this converter and cannot use the .ut mechanism.
Assignee: erik → ftang
Attached file cp864.cpg.txt which is the conversion table from 864 to Unicode 06 range.
mark it as assign
Status: NEW → ASSIGNED
decommit other bidi issue until we land IBMBIDI default on.
Target Milestone: mozilla0.9.1 → ---
reassign to simon@softel.co.il
Assignee: ftang → simon
Status: ASSIGNED → NEW
Changing QA contact to mahar@eg.ibm.com.
QA Contact: andreasb → mahar
We could use the ICU shaping engine to shrink/grow for the Lam-Alef in the de- shaping process.
Depends on: 82383
move to "Bidi-Arabic/Hebrew"
Component: Internationalization → BiDi Hebrew & Arabic
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
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
In an Arabic e-mail message, i am seeing the lamAlif ligature correctly, but after each occurrence of such there's a little box with the (Latin) letters "ZWSP". Is this the same problem? I will happily upload a screenshot if someone will please tell me how to take one on Linux. (I will also open a new bug, if this is thought to be a separate issue.) I'm using Linux trunk build 2001-11-07-06.
That sounds like a variation on the theme of bug 36163.
Blocks: 115714
I noticed that the ZWSP char that came after complex letters (such as : LAM_ALEF, Lam_hamzaonalef, Lam_madaonalef, Lam_hamzaunderalef, and so on ), this ZWAP was not in the mozilla 0.9.7, but t returned to the 0.9.8!
Status: NEW → ASSIGNED
This bug is also on Linux, so please change platform and OS to all. Could we please do something to enhance the priority of this bug? Because the ligatures all come out with this humungous ZWAP, even the simplest Arabic pages come out unacceptable. To make an analogy, it kind of like seeing a smiley face after every letter "y" which appears in any text on the page. Could we please promote this to major and add keyword mozilla1.0.1 or at most mozilla1.1?
The issue with the ZWSP after LamAlef is filed as bug 117041. It has a patch attached which will cause other regressions unless the patch in bug 138097, currently awaiting review, is checked in first. The original issue of this bug is specific to documents in the IBM-864 encoding.
Kindly be informed that Ahmad A. Abu-Taha (ahtaha@eg.ibm.com) from IBM Egypt is replacing Maha Abou El-Rous (mahar@eg.ibm.com) in monitoring and receiving notifications of Mozilla bugs regarding Arabic.
I'm unable to reproduce this bug.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
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.

Attachment

General

Created:
Updated:
Size: