This repository was archived by the owner on Apr 12, 2024. It is now read-only.
i18n: Taking numberformatsymbolsext into account #4858
Closed
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.
There are some errors in certain locale files, I noticed most latin american currencies were wrong. The problem is that closure library keeps a separate file numberformatsymbolsext.js for some languages.
This change uses this file too to generate the correct currency chars.
The locale generation process now downloads number format symbols from
this url too
http://closure-library.googlecode.com/svn/trunk/closure/goog/i18n/numberformatsymbolsext.js
Most locales should now be correct