Open Bug 1506415 Opened 3 years ago Updated 6 months ago

Arabic digits are not enclosed in ARABIC END OF AYAH

Categories

(Core :: Graphics: Text, defect, P3)

63 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: Lateef_sagar, Unassigned)

Details

Attachments

(1 file)

102.98 KB, application/x-zip-compressed
Details
Attached file Tehreer.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce:

1. Please unzip Tehreer.zip file
2. Open pqm_test.html file. It uses SIL Scheherzade and PakType Tehreer font. The End of Aaya mark encloses numbers properly in Internet Explorer but not in FireFox.

I have attached the font also so that it can help you in debugging the issue may be.


Actual results:

The End of Aaya mark encloses numbers properly in Internet Explorer but not in FireFox


Expected results:

The page should be displayed same as it does in IE. End of Aya should enclose numbers properly
Component: Untriaged → Graphics: Text
Product: Firefox → Core
Flags: needinfo?(jfkthame)
Priority: -- → P3
End of Ayah has always been a tricky character. I think this is somehow related to directionality and how the text gets broken into runs and reordered, though I don't recall all the details offhand.

Interestingly, the Scheherazade example displays as expected if you add unicode-bidi:bidi-override to the style, in both Firefox and Chrome. The PakType Tehreer example doesn't, however, suggesting that the two fonts aren't handling this in the same way.

Also interesting to see that Tehreer displays quite differently in Firefox vs Chrome. Something about the glyph sizing is very odd.
Flags: needinfo?(jfkthame)
(In reply to Jonathan Kew (:jfkthame) from comment #1)
> End of Ayah has always been a tricky character. I think this is somehow
> related to directionality and how the text gets broken into runs and
> reordered, though I don't recall all the details offhand.
> 
> Interestingly, the Scheherazade example displays as expected if you add
> unicode-bidi:bidi-override to the style, in both Firefox and Chrome. The
> PakType Tehreer example doesn't, however, suggesting that the two fonts
> aren't handling this in the same way.
> 
> Also interesting to see that Tehreer displays quite differently in Firefox
> vs Chrome. Something about the glyph sizing is very odd.

Thank you, I am using unicode-bidi:bidi-override and after some kerning tweaks in my font I am good now. Please close the issue.
You need to log in before you can comment on or make changes to this bug.