The Zend_Locale documentation already has extensive information on setting a default locale through the Zend_Registry, which will then be used by all 'localizing' functions (Zend_Date, Zend_Measure etc). Thomas Weidner's blog also mentions it. However, neither the (unstable) 1.6.0 RC3 release nor the latest stable 1.5.3 release seem to support it. I tried implementing it the way it was described in the documentation, but it didn't seem like anything was done with the 'Zend_Locale'-value in the Zend_Registry. Afterwards, I took a quick look through the sourcefiles of the aforementioned classes, and there was not a sign of any Zend_Registry use in any of them. Might it be that it just isn't there yet, and that we'll have to wait until the next full release? Weidner says:
You can use this feature within the actual trunk or you have to wait until 1.6GA is released.
Sorry for possibly asking a stupid question, but what does he mean when addressing the 'actual trunk'?

In another post he states that some of the i18n features have been delayed until release 1.7... so I guess even the september 1.6 release will not entail the stuff I'm looking for? If really so, I'd really like to know what he meant by the actual trunk...

Thanks in advance!

The dev-team has decided not to integrate the rewrite of the I18N core.
There are a couple of other features and issues which have been fixed, but the core rewrite leads to a minor BC brake with the old 'auto' locale feature.

So all you have to do, to get this feature working, is to use the actual trunk from SVN instead of the finished release 1.6.

__________________
Greetings
Thomas Weidner
I18N Team Leader, Zend Framework
http://www.thomasweidner.com

Thanks for your reply. Does it also mean that this new feature will never be integrated, or that it is just not ready for the next release yet?

I wanted to use it in a standard framework website solution, which is supposed to have flexible, easy-to-use and full internationalization features. Therefore, I think it would not be a good idea for me to use an SVN - integrating a non-standardized feature in a supposedly standardized framework website does not seem very clean to me. Still, thank you, and I hope the feature will, at some point, be available in a stable release.

As mentioned in the past this features will be released with 1.7.
They are already in core... all features implemented in trunk are the base for the next release.

Btw: Trunk does not mean non-standardized, nor untested. The trunk holds new components or features which will be released with the next release. Not more, not less. All features within there are tested and documented.

__________________
Greetings
Thomas Weidner
I18N Team Leader, Zend Framework
http://www.thomasweidner.com