corrections to combining characters table #302
Conversation
This file contains hidden or 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
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.
The tables in appendix B3 show some entries with 3-digit hex such as U+02E and U+0B8 and (consequently) no comment with the unicode name as the id lookup failed. In one case the line is duplicated with both a broken entry for U+02E followed by the correct entry for U+002E full stop
This has been corrected in the source unicode.xml at commit
w3c/xml-entities@ed8b732
and the matching entries fixed here (by hand as I see no record of the script to generate
combining-operators.htmleither here or in the xml-entities repo).so there are no normative changes here just deleting one duplicated entry and replacing uncommented three-character hex by four character hex with a comment of the Unicode name.