cldr
cldr copied to clipboard
unicode-org
CLDR-16595 Add DisplayAndInputProcessor rule for normalizing Kashmiri, normalize Kashmiri
WIP: Still need to replace in ks.xml; will try using Eclipse
This normalizes YEH WITH TAIL (an incorrect Pashto letter) to KASHMIRI YEH. See L2/23-241.
CLDR-16595
- [x] This PR completes the ticket.
ALLOW_MANY_COMMITS=true
Hooray! The files in the branch are the same across the force-push. 😃
~ Your Friendly Jira-GitHub PR Checker Bot
![jira-pull-request-webhook[bot] avatar](https://avatars.githubusercontent.com/u/13873561?v=4 "Published by a pub.dev verified publisher"){kind=small}
Notice: the branch changed across the force-push!
- tools/cldr-code/src/main/java/org/unicode/cldr/test/DisplayAndInputProcessor.java is different
~ Your Friendly Jira-GitHub PR Checker Bot
Notice: the branch changed across the force-push!
- tools/cldr-code/src/main/java/org/unicode/cldr/test/DisplayAndInputProcessor.java is different
~ Your Friendly Jira-GitHub PR Checker Bot
nice. i'll make sure this gets discussed and probably assign the ticket to you
Do we want to do this in advance of a possible UTC decision? (There is a separate proposal about various YEHs)
Yes, the Pashto yeh is incorrect regardless of the UTC decision. This matches the current state of the unicode standard, and if Unicode decides to disunify it's a simple second transformation to apply.
What is the current status of this PR? Will CLDR-16595 need to be split to continue work in v46?
I don't think there's further work there.
There is further work in this space on SAH's side, which I am doing. It does not need to be tracked by CLDR.
I think this is ready to merge once reviewed.
The PR description still says WIP.
@macchiati @DraganBesevic @pedberg-icu - I've been going through all the open tickets that are still in review. Can we still merge this PR, or should Manish clone his open ticket and have this target v46 instead? Thanks!