CLDR-18319 kbd: bnf: update bnf for transform ranges #4377
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
- Single escaped points in a range such as <transform from="[\u{127}]"> were not supported, but they are present in the spec.
mcdurdin
approved these changes
Feb 17, 2025
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.
Single escaped points in a range such as
<transform from="[\u{127}]"/>were not supported, but they are present in the spec.For example,
[a-z]or[a-\u{127}]or[\u{61}-z]are all supported, just not[\u{61}](and by extension,[a-z\u{127}]is not supported by the current BNF).this PR fixes the EBNF / ABNF to allow a single escaped codepoint to be a member of the character classes.
CLDR-18319
ALLOW_MANY_COMMITS=true