-
-
Notifications
You must be signed in to change notification settings - Fork 58
8 affricate ligatures #709
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
Conversation
roozbehp
left a comment
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.
Please add the DoNotEmit data too.
markusicu
left a comment
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.
no test data?
Hi @roozbehp Robin did add that data. I assume that we can dismiss your past negative review. |
No, this is from before I started writing these tests. Maybe I should go back and write tests for those older proposals, though when I asked whether I should (not sure if it was in RMG or in PAG) I didn’t get much of a response. |
See L2/24-051 Unicode request for affricate ligatures.
https://github.com/unicode-org/sah/issues/418
https://github.com/unicode-org/utc-release-management/issues/102
UTC-179-C55 Consensus: Provisionally assign 8 code points U+1DF1F..U+1DF24 and U+1DF2B..U+1DF2C for Latin affricate ligatures in the Latin Extended-G block as described in document L2/24-051. [Ref. Section A.VI of document L2/24-068]
[185-C40] Consensus: UTC accepts for encoding in Unicode 18.0 the following 321 Arabic, Armenian, Bengali, Cuneiform, Devanagari, Hebrew, Kana, Khitan, Latin, Mongolian, Phonetic and other symbol characters for which code points have previously been assigned: