-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct Spacing for LAM before Non-Arabic and BEH Before Number #189
Comments
Not only before non-arabic or numbers. I remember an old issue that some inline markup, |
A test here. |
@ntounsi, while this is a valid case with the hyperlink breaking, but the question here is more about which method should be used to correct the gap caused by either of LAM+non-Arabic, BEH+number, or link. Do you happen to have any information on that? |
@shervinafshar, I don't have any suitable information about "correct spacing for LAM before latin" . I often use to write LAM followed by W3C (to mean "for W3C"), and I do LAM+W3C, without any character between. Meanwhile I tried and I didn't find a rule around this case. |
Why are the ZWJ on the "far" side of the space character in the examples at the top? |
@asmusf, was a mistake. Corrected that. |
We have two characters that are separated by SPACE. One of them is from
a script subject to joining behavior.
On which side of the space do we expect the ZWJ?
|
ZWJ appears immediately after character from the script subject to joining behavior to force initial/medial form from an standalone character. |
Unicode (9.2, p.369 in version 11.0):
Common practice observed on some online reputable publications is LAM + TATWEEL + SPACE + ..., but this might be (a) to keep readability, (b) technical limitation in entering ZWJ.
Need to survey the experts for the correct and/or common method.
Testing with Google web-fonts:
![screencapture-fonts-google-2018-07-10-22_29_50](https://user-images.githubusercontent.com/875962/42552450-2dddc1d8-8491-11e8-8efd-f21d9104fb0d.png)
Plain text for testing in other environments:
The text was updated successfully, but these errors were encountered: