Core Team Proposal Reviews
Hy jayson,
With
0.1.4 out of the way, and 0.1.5 a quick bug-fixing, doc cleanup, testing
strengthening release, the core team is now getting underway with proposal
reviews from those that have been collecting in the Wiki and well get through
the current set, then move the next set into the under review section and
move through them all systematically.
Good to hear...
I was already thinking that I missed something in
my calendar. (30th June, as written in the proposal, has passed already)
:)
Until now, I've done some basic works on
Zend_Locale_Data to get the basic LDML Handling working as specified in the
standard. Didn't want to do much on that, until the proposals are
accepted.
My plan to get locale support classes working are
as following:
1.) Zend_Locale_Data (internal class handling the
LDML, is now in progress)
2.) Zend_Locale - Basic interface and abstraction
layer
3.) Zend_Locale_xxx - Implementations for source
languages (Gettext, TMX, SQL,...)
4.) Zend_Date
5.) Zend_Unit
6.) Zend_Currency
Work for several months :)
Btw:
To say it befor the first labratory
release :
- The locale ressource files are 320 xml files as
every language and country is described.
- In sum they need 3,6MB place. XML Description could be stripped, but they will have 3MB at
least.
But:
- In LDML there are translations in all
languages for all date-strings (Months, Days, era), all countries, all
terretories, all timezones, all scripts and all currencies included, additionaly
to the locale-formating informations.
So the core
framework could produze a list of all countries in every language with only 1
statement.
f.e. $countrylist = Zend_Locale::getCountryList();
$zones = Zend_Locale::getTimeZones('nl_NL');
or something like this.
The only thing I'm not clear until now is if the
classes should be static or not.
Greetings
Thomas
Locked
