I come back here.
I found another solution to translate fields :
In your form class :
class CustomAuthForm extends sfGuardFormSignin
{
public function configure()
{
$this->widgetSchema->getFormFormatter()-
>setTranslationCatalogue('form');
//etc...
}
}
Then create a form.xml in i18n/xx/form.xml
and populate it with field that you want to translate.
You can also put field in i18n/xx/messages.xml
but auto-delete task will remove them has it's considerate as old
string.
Regards.
On 1 sep, 20:23, Manu SW <[email protected]> wrote:
> Hi,
>
> Lutz thanks a lot for your reply. I tried what jjoaco suggested but no
> luck so far. I will try to get back to this problem a post a bit more
> info in here, see if i can get help to figure this out.
>
> Regards,
> M.
>
> Lutz wrote, On 8/25/10 2:09 AM:
>
> > Hi,
> > I had the same problem with HTML tags in general.
> > I found this thread:
> >http://oldforum.symfony-project.org/index.php/mv/msg/10655/77804/#msg...
> > that helped me.
> > I modified 'lib/symfony/i18n/sfMessageSource_XLIFF.class.php'
> > according to what 'jjoaco' wrote
> > and the text got translated including the HTML tags.
>
> > @Reo
> > The thing with the new module is maybe related. I guess the plugin
> > already uses the _('') helper, just that included html tags aren't
> > recognized correctly and so the
> > text got not translated. Maybe the solution spares you to create your
> > own module, also.
>
> > I hope it helps.
>
> > BR,
> > Lutz
>
> > On 25 Aug., 00:53, mrossw <[email protected]> wrote:
>
> >> 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_s...
>
> >> 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.- Zitierten Text ausblenden -
>
> >> - Zitierten Text anzeigen -
--
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
