Hi, I think i am having the same problem, only that i need the i18n in spanish.
I read that, so I was expecting to work out of the box : http://www.symfony-project.org/jobeet/1_4/Doctrine/en/19#chapter_19_sub_forms_forms_i18n Only the labels of the register form fields are not translated automatically. The <h1> content and submit button that are explicitely translated with __() are translated ok ... so i guess that means XLIFF are ok ... Any idea ? Thanks ! M. On Aug 16, 4:15 pm, Reo <[email protected]> wrote: > Hi, > > After long research i didn't find a way to use the i18n file include > in the plugin. > > I want to use them to translate the form register (or any others), may > i did something wrong : > apps/frontend/settings.yml > all: > .settings > enabled_modules: [default, sfGuardAuth, sfGuardRegister] > i18n: true > default_culture: fr_FR > standard_helpers: [Partial, Cache, I18N] /* Not sure > about the use of this parameter */ > > However, i found a solution by creating a new module and change the > _form.php template, but then i just wonder the use of thoose i18n > files in the plugin. > > Regards. -- 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 users" 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-users?hl=en
