-
-
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
Kirat Rai #445
Kirat Rai #445
Conversation
Preliminary script code: Krai |
Checked consistency with Ken’s UnicodeData-16.0.0d6.txt and LineBreak-16.0.0d2.txt. |
CI does not pass because of collation. |
I tried that (looking at the proposal and the assignments for other characters, with a couple of forays into the standard to figure out what was going on), but I am of course still mostly clueless about this, so please review carefully. |
Re the
I will look at Ken's past notes and see if I can propose some data. |
I added an initial sort order definition in unidata.txt here: 42bcaa8 |
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.
Partial review
Looks like the allkeys.txt file generated fine 🎉 The "variable" punctuation characters are a little hard to make out because they are not in collation order, but the script block looks as expected (I think):
FYI @Ken-Whistler but definitely no urgency! I see that there is not an explicit contraction for the recursive decomposition 16D6A --> 16D69 16D67 --> 16D63 16D67 16D67. Maybe need to tweak the sifter code to provide the full canonical closure here? |
I see that we now have a different CI failure:
This depends on me working on the script metadata. I have most of that data available, but don't have time right now to work it in. We definitely need to change the CI so that a UCA-tool failure does not block UCD progress. |
Indeed. On it. |
Re our friends alpha dia ext: all the interesting signs are Alphabetic by their Gc so that is easy. It would probably make some sense to make the viramas Diacritic, but it is probably best to deal with that as part of https://github.com/unicode-org/properties/issues/195. |
I investigated the issue of InPC thoroughly, and I now agree with Ken and Robin that we need InPC for the right side depdenent vowels of Kirat Rai. Will include them in my copy of InPC.txt and will figure out how to merge them into main. |
[171-C13] Consensus: Accept 58 Kirat Rai characters in a new Kirat Rai block that extends from U+16D40..U+16D7F for a future version of the standard, with properties as amended in discussion. (Reference L2/22-043R)
[176-C25] Consensus: Generalize conjoining behavior to include Kirat Rai vowel signs, and set the Grapheme_Cluster_Break property of the Kirat Rai vowel signs {E, AI, AA, O, AU} to "V". For Unicode 16.0. See L2/23-160 item 4.2.
[176-A83] Action Item for Robin Leroy, PAG: Set the Grapheme_Cluster_Break property of the Kirat Rai vowel signs {E, AI, AA, O, AU} to "V". For Unicode 16.0. See L2/23-160 item 4.2.
RMG tracking: https://github.com/unicode-org/utc-release-management/issues/28