This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Unicode CLDR Version 26 #76
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
|
Thanks for doing this, the help is very much appreciated. The tests are failing mostly due to a bug in V8, which I don't think I can work around without removing the tests (but that's another issue entirely). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I'm currently working for #69 because #69 is a critical issue for Japanese.
This PR is updating Unicode CLDR to version 26 simply. #69 will not resolve by this change, but I'd like to get done this first to make upstream data as up-to-date as possible. The release note of CLDR version 26 as follows.
The testing by
npm testmight be fails, but I think that be not due to this change.It includes many locale data updates. Please checkout my branch manually if you're with slow browser.