+1
I'm all for keys. However, if for whatever reason it's just not going
to happen then I'd like keys to be a separate Bundle for those who
really need that maintainability. Then to output translations
something like this:
{{ trans_key authentication.success }}
A way to override default location/format of the library would also be
nice. Then we can easily create an interface, and allow translators to
do their part.
On Mar 5, 5:45 am, Ariel Ferrandini <[email protected]> wrote:
> In my case, we extend the sfI18N class to use some MySQL tables with
> languages, translations and a relation of them so when we add a __()
> function everywhere the code if the translation is new we add it to the
> database.
>
> This way is perfect for us because we export the information to excel and
> the translators work with it and the we import it again with the new
> translations.
>
> I thinks we will do something like this in Symfony2 :D
--
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
