Mark Maynereid schreef:
Please note I am posting to the fw-general and NOT the I18N/Locale list in
respect of Thomas' advice here:
http://www.nabble.com/forum/ViewPost.jtp?post=8972463&framed=y&skin=16154 as
it's seems like I18N/L10n support is something all ZF components should
support and so be aware of Zend_Locale/Zend_Translate.
Specifically, Zend_Validate messages don't seem to support L10N yet as,
unless I'm mistaken, you can only translate fixed text so the Zend_Validate
classes themselves need to be L10n aware somehow. This in turn is making me
wonder if I can use Zend_Filter_Input.
I'm working on my first real world ZF app and I figured I would implement it
with British and American English translations for simplicity. Then I won't
have the pain of converting the whole app later when I want to add Spanish
and so on, but I'm not sure due to the above if ZF as whole is practicably
L10n ready yet.
Does anyone have any comments/workarounds for these problems in the
meantime? Or should I just skip localisation until it matures in ZF?
Thanks in advance,
Mark Maynereid
PS
Just posted a comment on this related proposal on exception codes
http://framework.zend.com/wiki/display/ZFPROP/Exception+codes+in+exceptions+-+Matthew+Ratand
found my way there via this issue
http://framework.zend.com/issues/browse/ZF-904
Hi Mark,
Making components locale aware, does not persé mean having translated
error messages / exceptions, etc etc by default.
If you want to have translations for your validator classes, have a look
at the Zend_Validate_Abstract::setMessage() method. This method allows
you to override default error messages, and thus you can also use this
to translate errors.
The implementation however, will depend on your project requirements /
system architecture.
Best,
--
Andries Seutens
http://andries.systray.be
Gecontroleerd op virussen door de JOJO Secure Gateway.
