New CLDR implemented
Today I updated the locale database to the latest release (CLDR 1.7) which is available since 2 weeks by unicode. It provides several corrections for existing locale informations.
Corrected currency signs, additional locales, additional timezone data and much more. This update changes about 5MB of data and is only provided within trunk. It will be available to ZF with the next minor release 1.9.
Additional new informations are provided by CLDR like
* postalcodes
* phonecodes
* locale upgrading
and several more.
This new informations will be integrated within ZF soon.
See http://framework.zend.com/issues/browse/ZF-6681 for informations about new features to be integrated.
Please note, that like in past Zend (and me) is not allowed to provide changed CLDR files. When you find a error you have to possibilities.
* Anyone who finds an error can keep it private
* Or feel free to write a issue to unicode (unicode.org/cldr) about incorrect informations
I hope you find it usefull
Greetings
Thomas Weidner
I18N Team Leader, Zend Framework
Zend Framework Advisory Board Member
Zend Certified Engineer for Zend Framework
Add comment
Fill out the form below to add your own comments
Wednesday, May 20, 2009 - 12:21:07
Really nice :) I like the postal code regexes - these look very useful! country to country codes for phonenumbers is also a nice feature. Thanks for the information.
Wednesday, May 20, 2009 - 13:29:12
Out of curiosity, why aren’t you allowed to provide changed CLDR files?
Even so, surely you can provide the originals + patches/overrides and just merge them at runtime, so it’s transparent to the user, if you want to?
Wednesday, May 20, 2009 - 21:50:30
I am no lawyer, so I can’t say which paragraphs between CLDR and ZF don’t correspond. This is the reason I do only things which we are allowed and which I was told in past.
Another thing is that I can’t check if things which users write as issue are correct or not. I am no native speaker for 135 countries and even if you are native speaker the official information can still differ from what people think.
And adding patches to the database raises another problem as this patches are depended on the version of CLDR. This would lead to backwards incompatibilities also when one user works with a patched database and another one with an unpatched.
To prevent legal and usage problems we decided not to change the provided data. You can still change this data manually yourself and write your own patches.