-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Four Arabic Pegon Characters #435
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ArabicShaping.txt has issues with Joining_Type of the dal-like character and the schematic names of all three.
I think it should be:
|
Yes, but with "TWO" replaced by "2" and "VERTICAL" preceding the digit. "DAL WITH VERTICAL 2 DOTS BELOW" etc. |
See also issue #454 for catching issues in the schematic name. |
…ning class for U+0897 ARABIC PEPET to ccc=230, from ccc=0 as approved by UTC-172-C3.
Checked consistency with Ken’s UnicodeData-16.0.0d6.txt and LineBreak-16.0.0d2.txt. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[172-C3] Consensus: Accept the following four characters for a future version of the standard, with property values as given in L2/22-116:
(Reference: L2/22-116 and section 4b of L2/22-128)
[176-C15] Consensus: The UTC approves the ArabicShaping.txt entries in L2/23-160 item 2.1 (a), replacing those recommended by L2/22-116 and previously approved in UTC-172-C3.
[176-C17] Consensus: The UTC approves the change of canonical combining class for U+0897 ARABIC PEPET to ccc=230, from ccc=0 as approved by UTC-172-C3.