I'm glad it worked! :) You can set a different catalogue to use for a form in the form formatter class.
As far as the module code generation goes... hmm, you'd have to create your own module generation theme. Cheers, Daniel On Dec 29, 2009, at 3:46 AM, diogobaeder wrote: > Hi, Daniel, > > Thanks for the help, it really worked for the __() function calls! :-) > > Despite, I noticed that fields generated by widgets don't include this > function call, so I would have to declare localized labels for them, > too... wouldn't it be a better idea if these plugins were already > prepared for internationalization? I mean, loading the i18n helper at > the templates and form libs, so that the user could easily create > translation files for the plugin? > > Diogo > > > > On 28 dez, 06:35, Daniel Lohse <[email protected]> wrote: >> For your example it's pretty clear that symfony can't find the translations. >> And sure enough, you forgot to add the catalogue to the __() method call. >> Plugin or not, it doesn't matter. >> >> In the signinSuccess.php change this: >> >> __('Forgot your password?') >> >> to this: >> >> __('Forgot your password?', array(), 'sf_admin') >> >> and it should work. >> >> Cheers, Daniel >> >> On Dec 28, 2009, at 1:43 AM, diogobaeder wrote: >> >>> Daniel, >> >>> For example, in the signinSuccess.php template, at >>> sfDoctrineGuardPlugin, we have a "__('Forgot your password?')" call, >>> that should be translated if a translation is put in the >>> sf_admin.pt_BR.xml file. I've put a translation element there, but >>> it's not working. But for a translation for a gettext function call in >>> the Symfony core, for example a "__('Choose an action')" call (the >>> first <option> for the <select> at the bottom of the admin list >>> actions), it works. >> >>> So, if I have: >> >>> <trans-unit> >>> <source>Choose an action</source> >>> <target>Selecione uma ação</target> >>> </trans-unit> >>> <trans-unit> >>> <source>Forgot your password?</source> >>> <target>Esqueceu sua senha?</target> >>> </trans-unit> >> >>> The first translation is working, but the second is not. I realized >>> that the second is used in a plugin, so that's why I thought it could >>> be something with how the translations relate to plugins. >> >>> Any ideas? >> >>> Diogo >> >>> On 27 dez, 12:12, Daniel Lohse <[email protected]> wrote: >>>> Could you elaborate on/rephrase your last message again, please? >>>> I did not understand what stays where and does not get translated... :) >> >>>> Daniel >> >>>> On Dec 27, 2009, at 2:57 PM, diogobaeder wrote: >> >>>>> Hi, Daniel, >> >>>>> I've already named the file like you said, and part of the admin is >>>>> translated. But the part that stays in the plugins (sfDoctrineGuard >>>>> and sfMediaBrowser) is not translated. It seems like the translation >>>>> file I created only works with translation for the core components. >> >>>>> Any other idea? >> >>>>> Thanks! >> >>>>> On 27 dez, 08:44, Daniel Lohse <[email protected]> wrote: >>>>>> You'll need to name the file sf_admin.pt_BR.xml >> >>>>>> Cheers, Daniel >> >>>>>> On Dec 27, 2009, at 3:30 AM, diogobaeder wrote: >> >>>>>>> No solution for that? Anybody? >> >>>>>>> On 22 dez, 18:04, Diogo Baeder <[email protected]> wrote: >>>>>>>> Hi there, >> >>>>>>>> I'm translating some strings that lacked in the original pt_BR XLIFF >>>>>>>> file for Symfony 1.4.2-DEV. Even though, my translation for >>>>>>>> sfDoctrineGuardPlugin is not working; None of them is being read. >> >>>>>>>> How can I translating the plugin, so that the authentication screen and >>>>>>>> messages stay in my language? (Brazillian Portuguese.) >> >>>>>>>> Thanks! >> >>>>>>>> -- >>>>>>>> Diogo Baeder - desenvolvedor webhttp://diogobaeder.com.br >> >>>>>>> -- >> >>>>>>> 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 >>>>>>> athttp://groups.google.com/group/symfony-users?hl=en. >> >>>>> -- >> >>>>> 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 >>>>> athttp://groups.google.com/group/symfony-users?hl=en. >> >>> -- >> >>> 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 >>> athttp://groups.google.com/group/symfony-users?hl=en. > > -- > > 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. > > -- 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.
