New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: full cldr #33682
fix: full cldr #33682
Conversation
Nice fast work @doom777 - I was just looking at that configuration too :-) |
Note that you must remove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for doing this fix!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
something fishy is going on here. we should dig into this more before merging the PR
@@ -19,17 +19,21 @@ export default [ | |||
'agq', [['a.g', 'a.k'], u, u], u, | |||
[ | |||
['n', 'k', 'g', 't', 'u', 'g', 'd'], ['nts', 'kpa', 'ghɔ', 'tɔm', 'ume', 'ghɨ', 'dzk'], | |||
['tsuʔntsɨ', 'tsuʔukpà', 'tsuʔughɔe', 'tsuʔutɔ̀mlò', 'tsuʔumè', 'tsuʔughɨ̂m', 'tsuʔndzɨkɔʔɔ'], | |||
[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's odd that the formatting is now different but the content is the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, I have found that clang will refuse to format some files on my machine. I don't know why.
@@ -57,7 +57,8 @@ export default [ | |||
'RUR': [], | |||
'SEK': [], | |||
'THB': ['฿'], | |||
'TWD': ['NT$'] | |||
'TWD': ['NT$'], | |||
'XXX': [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in this case there seems to be a data change. is that expected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #33682 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, data change is expected, because it is part of update from cldr33 to cldr36, where some of the files were not yet upgraded.
] | ||
], | ||
[['е.ә.', 'ј.е.'], u, ['ерамыздан әввәл', 'јени ера']], 1, [6, 0], | ||
['dd.MM.yy', 'd MMM y', 'd MMMM y', 'd MMMM y, EEEE'], | ||
['HH:mm', 'HH:mm:ss', 'HH:mm:ss z', 'HH:mm:ss zzzz'], ['{1} {0}', u, u, u], | ||
[',', '.', ';', '%', '+', '-', 'E', '×', '‰', '∞', 'NaN', ':'], | ||
['#,##0.###', '#,##0%', '¤ #,##0.00', '#E0'], '₼', 'AZN', | ||
['#,##0.###', '#,##0%', '#,##0.00 ¤', '#E0'], '₼', 'AZN', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another suspicious data change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this could well have been a fix from when we upgraded to 36 but that didn't show up previously if this is one of the files that was missing from that previous PR.
|
||
const u = undefined; | ||
|
||
export default []; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these supposed to be empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many of the extra
files are empty, which is why we just concatenated them together in the "global" versions.
switching to cldr-data package resulted in loss of some locales, since by default only core locales are loaded. This PR adds a flag to tell cldr-data to use full locale coverage fixes: #33681
Rebasing done, @IgorMinar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after the rebase
Thanks! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Blocked on #33699
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Fixes #33681
What is the new behavior?
Enables all the previous locales, plus new ones as per cldr-36
Does this PR introduce a breaking change?
No, but the PR whose behavior it fixes, does
Some locales were removed, some were renamed.