First, some information on how translation is done under the hoods. Probably most of you already know, but for those who don’t, the most used way of translating an application in Linux is with GNU gettext. Without going into much detail, gettext provides a simple way to translate an application, both from the developer and the translator point of views.
For the translator, all he has to do is fill a text file with a key-value structure. Normally, the key is the expression in english, and the value is the translated expression. Here’s an example:
msgid "Turn Off Radio"
msgstr "Desligar Radio"
If you open the "share/radiotray/i18n/radiotray.pot" you’ll see a template ready to fill. From that folder, all subfolders represent a specific language and have a "po" file that is nothing more than a "pot" file, with the values filled in. If you want to help, you could just fill those blanks and send me the file.
However, for organising the whole translation process better, there’s Transifex. Transifex is synchronized with the sourceforge project and gives a simple interface to create and edit the "po" files. If you want to use Transifex, you just have to register and go to the Radio Tray project page.
From there, select the "trunk" component and a list of languages will be listed. If the language you want is already in the list, you can ask to edit that language. If not, you can submit a new "po" file for the language you want. You can also join a translating team or ask to create a new one. But instead of me textually explaining how all of this works, it’s better to just watch the howto video, obtained from Transifex help page.
Radio Tray has very few expressions to translate, so it won’t take you much time. The translated languages will be available in the following release of Radio Tray. If you can’t wait, you can just grab them from the SVN repository in the sourceforge project 🙂
Thank you all for contributing and happy listening!