Monday, March 24, 2014

Managing translations on a team project

We have finished translating our application into a second language, but are having trouble finding a good solution for keeping this up to date going forward. Currently we have just been sending the .po file to the translator, but as we hope to have the dual language support not be a "beta" thing, we need to find a more serious way to handle this.

We have about 12 developers spread around the world working full time on the project, which means that strings change rapidly and it's hard to keep up on what is needed for translations before the list gets rather long. Can anyone recommend blogs or tools that can help manage this problem? We would basically love some way to get a list of strings that are currently untranslated generated automatically so our translators can know what needs done.

We looked into using the django-rosetta project, but seems like it wouldn't work well with our deployment process.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/951233fc-df3d-415c-a9a2-5d8308e3fc36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment