Gurung Khema #564
Merged
Gurung Khema #564
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roozbehp
reviewed
Nov 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[172-M1] Motion: UTC accepts 58 Gurung Khema characters at U+16100..U+16139, with names and glyphs as given in L2/22-157, and with property values given in L2/22-157 as amended in section 5 of L2/22-128, in a new Gurung Khema block that extends from U+16100..U+1613F for a future version of the standard. (Reference: section 5 of L2/22-128)
(The motion passed.)
LineBreak according to L2/22-080, contra Ken’s draft 3. UnicodeData.txt and LineBreak.txt otherwise consistent with Ken’s.