16.Feb.2010 at 15:05 by Dennis Benkert
Also I liked the the plugins you showed!
Internationalization
Thomas Rabaix (16.Feb.2010)
Talk at Symfony Live Conference 2010 (English - US)
Internationalization is an important feature in a worldwide project.
All-important projects required at some point to be used by people
with different cultures and languages. This constraint must be
understood from the application architecture to the implementation.
Symfony is bundled with many tools to create a full stack
internationalized and localized application. However it can be
hard to know how to handle all these tools: from the database
layer (doctrine / propel) to the view, without missing the sfForm
sub-framework.
The translation process can be very long as it involves the
technical team to update and deploy the new translation files.
Moreover it also requires some technical knowledge from the client
to work with translation files. All these issues can be nicely
resolved by using one plugin: mgI18nPlugin.
mgI18nPlugin is a n interactive GUI build on top of the symfony
framework to translate messages used in the current pages. The
plugin can also parse lib and action class to find translatable
messages.
The session will demonstrate:
All i18n features provided by the symfony framework
Good practices
Presentation of the mg18nPlugin which allows to edit project translations from within the website.
Quicklink: https://joind.in/1402
Slides: Internationalization
Who are you?
By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.
If the claim is approved you will be able to edit the information for this talk.
Are you sure?
Comments
16.Feb.2010 at 21:02 by Christian Morgan
Thanks Thomas - was a great start to the conference!
Anyone have any links to info about how to use MySQL (Doctrine) to store the translation catalogues (and then using backend (admin generator) to edit the translations)? We did this using Propel way back in the mists of time with sf1.0 but couldn't find any info about doing it with Doctrine + sf1.4 when I looked recently.
18.Feb.2010 at 21:21 by Evert Harmeling
I kinda expect it will create overhead for you app, instead of easing the I18n for you... Too bad the plugin is not yet ready for sf1.4 and Doctrine... But will definitely have a look at this! Since it seems like one of the few examples (plugins) in storing your translations in the database! And it's support for translations in your lib and actions seems great. What about messages (email)?
So thanks for sharing and pointing it out!
@caponica that's my question too :)
Speaker comment:
18.Feb.2010 at 21:35 by Thomas Rabaix
@evertjes @caponica You can get a working copy for sf1.3 and sf1.4 here : http://svn.symfony-project.org/plugins/mgI18nPlugin/branches/sf1.3/ (the plugin works on both version).
As the plugin uses Doctrine is kinda "Doctrine ready ...", If you want to edit the translation in a backend application you can generate an admin gen with models : mgI18nTransUnit and mgI18nCatalogue.
Please, feel free to contribute to the plugin with you find anything to improve.
23.Feb.2010 at 11:51 by Nathan Lisgo
Good topic. Covered a lot and highlighted lots of available resources.
16.Feb.2010 at 13:02 by Mike van Riel
Great session, very clear description of the I18N system in symfony.