Closed patch closed 8 years ago
CLDR v26 was released on September 18: http://unicode-inc.blogspot.com/2014/09/cldr-version-26-released.html
Relevant spec changes:
<numbers>
, add <minimumGroupingDigits>
. This can be used to indicate whether the locale suppresses grouping separators (such as thousands separators) below a certain value, so that for example the grouping separator is only used for values of 10000 and up.”Notable data changes:
fr_CH
thousands separator to space.”฿
to THB
.”pt_PT
, pt_CV
, kea
: Change currency formats for Escudo so the currency symbol is the decimal separator, e.g. 1,234$56
.”CLDR v27 was released on March 19: http://cldr.unicode.org/index/downloads/cldr-27
The JSON data is now distributed via GitHub: https://github.com/unicode-cldr
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: https://metacpan.org/release/PATCH/CLDR-Number-0.11
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.