-- Jurian Sluiman <[email protected]> wrote (on Wednesday, 26 September 2012, 09:14 PM +0200): > 2012/9/26 Ralf Eggert <[email protected]> > > within ZF1 we had a lot of this stuff within XML files: > > > > > > http://framework.zend.com/svn/framework/standard/branches/release-1.12/library/Zend/Locale/Data/ > > > > Maybe that could be reactivated and reincluded to the /resources folder? > > > That data is called CLDR (Common Locale Data Repository) and is maintained > at http://cldr.unicode.org/. They have a downloads section where you can > get all the xml files. Inside the CLDR data there is a section "display > names" where a list of all territories: > http://unicode.org/reports/tr35/#Display_Name_Elements > > I am not sure what the reason was to remove the CLDR data from zff2, but if > I remember correctly it was a large codebase and hard to keep up to date > with the latest release from http://cldr.unicode.org/. But perhaps this > will be resubmitted to the zf2 repository, but I am not sure...
There were two primary factors: * ext/intl fulfills a majority of L10n needs, and, due to being in C, is much, much faster than anything we could write in userland. * As you note, keeping the CLDR up-to-date was a major hassle, and hugely inflated the repository size -- and the majority of user needs fell within what ext/intl offers, making the offering questionable. Additionally, due to the size, there were performance issues that led to a need for robust caching. While we could transcode the XML to native PHP data structures, those structures would be large enough to impact resources. Caching only what is used works, but it requires some pretty difficult strategies to accomplish well. If enough people are interested in having CLDR-backed L10n, we can likely add it in a future release, or, better yet, via a module. -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
