How to manage translations as they are added by the release?

Question

I work on the RoR website, which is translated into several languages. It’s a real pain to manage what’s new translations for each version. We must collect all the new keys and send them to the table in the translation team. So my question is:

How do people structure their locale files and manage the addition of new keys so that it is easy and painless to associate changes with the translation team?

Answer 1

http://www.github.com/mynewsdesk/translate

This is really awesome, although it will not organize the translation of yml languages ​​into any specific categorized structure. He will insert the word “absent”, if necessary, and delete the orphaned entries.

You might also want to look at the textmate package.

Answer 2

I wrote a pearl to solve "what's new for translating the problem"

https://github.com/zoodles/vocab

After installing the gem, you run the following command:

vocab init

This will save the link to the current git main SHA to a file named .vocab

After adding lines to the site, you run:

vocab extract rails

This will create a yml file containing all the English keys and strings that were added after the commit provided by the SHA in .vocab. You can send this file to translators for translation.

When translations come back from translators, you can run the command:

vocab merge rails

This will translate the values ​​to all valid yml files in config / locales.

Answer 3

We recently switched to https://webtranslateit.com/ . A great tool for managing our locations. Just pick up the last yML file of the master locale file to their web service and it will mark the whole new line as untranslated and even track the changes in the old lines and mark them as "Check Required". A few days ago, my colleague wrote a blog post about our translation process .

Answer 4

I would suggest some simple ways. We follow the first -

• Always save entries in locale files sorted by key. This will help you find out extra / missing data by doing a simple diff using any diff tool

• Put a marker at the end of the file after the previous version and add new key values ​​at the end of the file

Answer 5

Easy really ... The best thing to do is send the translation command to your full English file. If they are professionals, they use a translation memory tool such as Trados or Deja Vu. THY will import your file, and the lines that they have already translated will be pre-populated and they will remain with deltas.