-
Notifications
You must be signed in to change notification settings - Fork 26.9k
Update i18n locale data extraction script #21626
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
Conversation
47d6bf1 to
dfe26ed
Compare
|
You can preview dfe26ed at https://pr21626-dfe26ed.ngbuilds.io/. |
dfe26ed to
97312d8
Compare
|
You can preview 97312d8 at https://pr21626-97312d8.ngbuilds.io/. |
|
While the TS 2.6 commit (second one) is not strictly required for the patch branch, it's better to keep generated files in sync between master and patch. |
|
running g3sync presubmit http://test/OCL:182567375:BASE:182567631:1516391751302:a8e6c969 |
…TS 2.6 (angular#21626) Fixes angular#21608 PR Close angular#21626
|
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. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
We have multiple issues with the extraction script for CLDR data:
inspectfunction fromutilto print missing values from arrays (util: change sparse arrays inspection format nodejs/node#11576) resulting in corrupted data filesinspectmethodIssue Number: #21608
What is the new behavior?
I've replaced the
inspectfunction by a modifiedJSON5.stringifymethod which fixed all of the issues, and I've extracted the plural function as requested. You can find the new LTR/RTL characters in languages such as arabic (ar.ts) or hebrew (he.ts)I pushed two different commits since I did two different updates.
Does this PR introduce a breaking change?