I'm not familiar with Zend_Translator, but I would suggest you take a look at the Xliff reader that Bernhard Schussek implemented for the Form/Validator components (if you haven't already). He is already making use of the intl package throughout those components and many date/number form fields already support localization. The default language is "en", which results in messages.en.xml being loaded.
Not sure if there is any support for customizing the locale via config - I believe he infers the locale from php.ini (the intl module's configuration). On Sep 13, 5:19 am, Matthias Nothhaft <[email protected]> wrote: > Hi, > > for the I18N, I think Zend_Translator is only a very small part.. Not > even sure if it's really usable.. From what I read it's only some sort > of "message reader" for several formats like xliff and so on. And the > translate() method can not handle arguments and no support for > catalogues. Nothing for numbers.. or are there other Zend components > that do "the rest" ? > > I suggest to create an I18nBundle from scratch and use the new intl > extension [1]. I also think that it's important to support arguments > and catalogues as it "was" the case with sf 1.x. Maybe there should be > a i18n:extract command that works for all bundles? (I know it's hard > to properly do it). I hope we can keep most of the goodness of the sf > 1 i18n stuff but improve the implementation by using the latest > available ways to do it. > > What do others think? > > regards, > Matthias > > [1]http://de2.php.net/intl -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
