[symfony-users] Re: i18n with technical names instead of text

2010-04-30 Thread rafaelgou
You can simply user: _('mainPage.linkToLogin' ) in your code. But if you want to be more explicit about non translated strings (warn users about non translated strings), why can't use prefix/suffix as we can see in docs:

Re: [symfony-users] Re: i18n with technical names instead of text

2010-04-30 Thread Tom Haskins-Vaughan
I've been thinking about using 'keys' instead of full sentences: echo __('layout.greeting'); But is this an acceptable/symfony way to do it? On Fri, Apr 30, 2010 at 10:45 AM, rafaelgou rafael...@gmail.com wrote: You can simply user: _('mainPage.linkToLogin' ) in your code. But if you

[symfony-users] Re: i18n with technical names instead of text

2010-04-30 Thread rooster (Russ)
On Apr 30, 7:37 pm, Tom Haskins-Vaughan t...@templestreetmedia.com wrote: I've been thinking about using 'keys' instead of full sentences:   echo __('layout.greeting'); But is this an acceptable/symfony way to do it? Symfony won't tell you off if you do, it's up to you. There are pros

Re: [symfony-users] Re: i18n with technical names instead of text

2010-04-30 Thread Tom Haskins-Vaughan
Thanks for your input, Russ. I haven't used i18n much but I've taken over a CI project that uses keys rather than full sentences. I guess the benefit I was looking at is maintenance of the dictionaries, but I'll bear your advice in mind. Tom On Fri, Apr 30, 2010 at 1:48 PM, rooster (Russ)