views:

30

answers:

3

I work on a RoR website that is translated into a number of languages. It's a real pain to manage the "what's new to translate" for each release. We have to collect all the new keys and send them out in a spreadsheet to the translation team. So, my question is:

How do people structure their locales files and manage the addition of new keys so that it's easy and painless to communicate changes to the translation team?

+2  A: 

http://github.com/newsdesk/translate

This is really awesome though won't organise your languages translation yml's into any particular categorised structure. It will insert the word "missing" however, where necessary and remove orphaned entries.

You might also wish to look at the textmate bundle.

mark
Great link, my homebrewed web-interface is a bit lacking.
Terry Lorber
A: 

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

  1. Always maintain the entries in the locale files sorted on the key. This will help you to find out the extras/missing by doing a simple diff using any diff tool

  2. Put a marker at the end of file after previous release and add new key-values at the end of the file

Gopi
A: 

Easy actually... The best thing to do is to send the translation team your complete English language file. If they are professionals, they are using a translation memory tool such as Trados or Deja Vu. THey will import your file and the strings that they already translated will pre-populate, and they will be left with only the delta.

NinjaCat
Caveat, "if they are professionals". I'll look into it...
Terry Lorber
not to be cheeky... why would you not have a professional translate something as your UI? There's nothing worse than a bad translation...
NinjaCat