U+19DA is DISALLOWED because XV8 #609
Merged
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
markusicu
requested review from
macchiati,
asmusf,
josh-hadley and
Ken-Whistler
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.
Fixes a derived-data bug caused by a tooling error which had set the idna2008derived status of U+19DA to be PVALID.
In IdnaMappingTable.txt U+19DA has an IDNA2008 Status of XV8: https://www.unicode.org/reports/tr46/#Table_Data_File_Fields
“XV8 is present when the character is excluded by IDNA2008 for the current version of Unicode.”
Therefore, in the idna2008derived files it needs to be DISALLOWED.
All files copied verbatim today from https://www.unicode.org/Public/idna/idna2008derived/
except for restoring the template placeholders in the ReadMe.