Re: [alreq] U+FDF2 'ARABIC LIGATURE ALLAH ISOLATED FORM' not always rendered correctly from Denis Moyogo Jacquerye via GitHub on 2018-06-22 (public-i18n-archive@w3.org from April to June 2018)

From: Denis Moyogo Jacquerye via GitHub <sysbot+gh@w3.org>
Date: Fri, 22 Jun 2018 09:21:28 +0000
To: public-i18n-archive@w3.org
Message-ID: <issue_comment.created-399380160-1529659287-sysbot+gh@w3.org>

As @r12a notes in https://r12a.github.io/scripts/arabic/block#charFDF2 the compatibility decomposition for FDF2 is <alif, lam, lam, heh> (“≈ [isolated] 0627 0644 0644 0647”).

While the (non normative) reference glyph is a ligature <alif, lam, lam, shadda, superscript alif, heh>, this hasn’t always been the case. In the [Appendix H. New Characters](https://www.unicode.org/versions/Unicode1.1.0/appH.pdf) of the Unicode Standard 1.1, the reference glyph used is a ligature <alif, lam, lam, heh> without shadda nor superscript alif.
This may explain where the compatibility decomposition of FDF2 comes from.
![capture d ecran 2018-06-22 a 10 18 25](https://user-images.githubusercontent.com/1923747/41768961-a70af0e8-7605-11e8-930d-2918b3ef86b1.png)

-- 
GitHub Notification of comment by moyogo
Please view or discuss this issue at https://github.com/w3c/alreq/issues/125#issuecomment-399380160 using your GitHub account

Received on Friday, 22 June 2018 09:21:31 UTC