From time to time it\’s time to talk together.

I thought that you might want to hear what happend within the last 4 months.
So I will give you the actual state of my work.

Since several months I focus completly on ZF2 development.
This means on the other hand that all new features and changes are instantly available for the next major release and must not be reworked.
When you want to follow me simply watch my github repository:

Actually I worked on fixing several small issues. Those are for example:

I added handling for floats within the Null filter. This has been missing in past.
Zend_Filter_Alnum/Alpha and EmailAdress had public variables. This has changed in favor of accessor methods to provide consistency to the other filters.

Now Zend_Translator can be used in phar libraries.
And auto-routing has been added. The users browser settings are used as routing information.

GreaterThan and LowerThan can now handle equal numbers.
IP can now handle hex, octal and binary noted IP adresses.

Behind the scene I am working on V2. It’s a complete rewrite of all locale classes.

Those are just a few examples.
In sum there are more than 80 issues which have been worked on and fixed since april.

Still much work to do.
Feel free to contact me directly when you think that an issue is missing or should be done first or also when you want to me to write about something in detail in my blog.
For coding help please contact the mailing list.

Thomas Weidner
I18N Team Leader, Zend Framework

Zend Framework Advisory Board Member
Zend Certified Engineer for Zend Framework

Back to top

Zend_Locale 2.0

Hy fellows,

first I want to wish you all a good start into this new decade.
Then I wanted to inform you about some news for Zend Framework.

Within the last days I began a complete rework of the I18n core for ZF.
The first class which will be reworked is Zend_Locale as it’s the base class for I18n within ZF.

The following changes will be done for Zend Locale 2.0:

CLDR update to 1.9
This integrates the most actual locale database within ZF

Usage of a fallback locale
This locale can be set and used as fallback when the wished locale is not supported

Usage of a fixed locale
This locale can be set and will be used regardless of any other locale which the accessing user wants
This removes the workaround from Zend_Application

Add locale providers as base
This allows to use other locale providers than CLDR
This will remove Zend_Locale_Format and integrate it into the used provider

Rework CLDR to be a provider

Add INTL as new provider
This allows to use INTL when available alone or in combination with CLDR because the INTL extension does not provide all informations like CLDR

Add a way to upgrade a locale
This would allow to provide informations for language locales when no region was given (f.e. when a user gives ‘en’ and wants to have informations from a region (f.e. currency))

Add script support
This allows to use locales which provide several scripts within the same language like Azerbaijani, English or Hausa.

That’s the actual plan for Zend_Locale 2.0 and will be the base for all other reworks.
Please note that all spoken will be done within Zend Framework 2.0 and not be migrated to 1.x.

Thomas Weidner
I18N Team Leader, Zend Framework

Zend Framework Advisory Board Member
Zend Certified Engineer for Zend Framework

Back to top

Translating validation messages

Hy interested ones,

many of you are using validators within Zend Framework.

As you know the returned error messages can be changed. This is very important for sites which are not delivered in english.
But they must translate all messages into their own language. This is a very tendious task.

Therefor I added today a new feature to Zend Framework. In fact it’s not really a new issue but more a long outstanding work :-)

Zend Framework comes now with translation resources.
These are pre-translated validation messages which are shipped as with release 1.10.

To use them you can simply do the following in your bootstrap:

$translator = new Zend_Translate(
    array('scan' => Zend_Translate::LOCALE_DIRECTORY)

When $language would be “de” all validation message are returned in german.
This should save you a lot of work for your project.

Note that the resources are outside the ‘/library’ path.
And you can also change the existing resources to do your own translations.
This is much simpler and faster than creating a new translation file manually.

For more informations take a look into Zend Frameworks manual.

I hope you find this feature useful and
have fun with Zend Framework,

Thomas Weidner
I18N Team Leader, Zend Framework

Zend Framework Advisory Board Member
Zend Certified Engineer for Zend Framework

Back to top