I agree with you, it's quite a headache to deal with the translation files as XML. I have a couple of ideas on how this could be improved but I did not have the time to implement it as a plugin.
For existing solutions to this problem take a look at: http://www.symfony-project.org/plugins/mgI18nPlugin A really nice plugin that stores translations in DB and provides a jQuery UI to translate the strings directly on the portal. gabriel On Nov 22, 11:40 am, Simone Fumagalli <simone.fumaga...@gmail.com> wrote: > Hello everybody. > > When I develop I18n project I always spend a lot of time (too much) to > translate it. It's hard for me to keep translation files updated and > share them with the translators. My translators don't know how to use > programs like Virtaal/Pootle and the send me MS Words/Excel files ! (I > let you imagine problems with UTF 8 and etc) > > I've 2 questions: > > 1) Does anybody have hints or want to share best practices for manage > the translation process ? > 2) Is there a site/service where I can hire a translator and get my > dictionary file in Xliff format ? > > Thanks > > -- > Simone -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
