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
support CLDR v27 #33
Comments
CLDR v26 was released on September 18: Relevant spec changes:
Notable data changes:
|
plus add script for upgrading to new versions
by keeping currency symbol for AUD (Australian Dollar) in en-AU (Australian English) as `$` instead of `A$` details: http://unicode.org/cldr/trac/ticket/7964
CLDR v27 was released on March 19: The JSON data is now distributed via GitHub: |
- Remove CLDR data with draft status of 'provisional' or 'unconfirmed' and only include 'contributed' or 'approved', which is the same threshhold as the ICU Project as well as the CLDR JSON data as of v27 - Remove 'provisional' draft numbering systems until they become at least 'contributed': brah (Brahmi), cakm (Chakma), osma (Osmanya), shrd (Sharada), sora (Sora Sompeng), takr (Takri)
but we should still test and support it
* origin/cldr27-dev: update locale inheritance test data [#33] update tests for CLDR v27.0.1 [#33] currency decimal is no longer in any locale [#33] new target is CLDR v27.0.1 [issue #33] generate: fix locale variants add proper locale inheritance to the update script scripting the update of base number data (ongoing)
Upgraded CLDR data from v24 (2013-09-18) to v27.0.1 (2015-03-30) and released to CPAN in CLDR::Number v0.11. See the Changes file for details: What I did on my summer vacation :D |
CLDR v25 was released today:
http://unicode-inc.blogspot.com/2014/03/cldr-version-25-released.html
The changes are primarily structural in nature and very few of these changes affect numbers, while none of these structural changes affect the implemented portions of CLDR::Number.
Here are the locale data changes that affect us:
fy
(West Frisian),fy-NL
,ug
(Uyghur),ug-Arab
,ug-Arab-CN
,prg
(Prussian)Additionally there is "Better locale matching, with better fallbacks; likely subtags for regions; added scripts for various languages" but our locale matching and fallbacks were already rather minimal. We should obviously use the new version when implementing matching/fallback improvements.
The text was updated successfully, but these errors were encountered: