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] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
