Agreed. Someone made an interesting point here:
http://groups.google.com/group/symfony-users/browse_thread/thread/d69957ca379dc47d/9b14198d4d13a70b?lnk=gst&q=translation#9b14198d4d13a70b
"For example, if we translate the word 'room', we don't know exactly if it
means a room or space in the text it is used.
So I want to find a tool which can show dynamically the context, for
example, display the whole text which contains the keyword. "
It is indeed a problem when translating our apps from english into french.
I would much prefer to do something like:
"admin.contact.create.success.created" instead of __("Contact has been
created") etc.
On 3 January 2011 14:48, Bernhard Schussek <[email protected]> wrote:
> I agree that parameters should have a unified naming and cannot really
> add much to your post.
>
> What I'd like to throw in though is the proposal to lookup
> translations by using message keys. AFAIK this is the recommended way
> in Rails and Struts, for example.
>
> The current way of refering to translations by using the root language
> has several drawbacks:
>
> - when you fix a typo in the root language, all translations are broken
> - the same english text (or in any other root language) might be
> translated differently within different contexts
>
> We switched to using message keys in symfony 1 projects two years ago
> and could fix these problems. I think this should be a best practice
> and encouraged by the core framework in Symfony2.
>
> Cheers,
> Bernhard
> --
> Software Architect & Engineer
> Blog: http://webmozarts.com
> Twitter: http://twitter.com/webmozart
>
> --
> 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]<symfony-devs%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
>
--
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