Translating

From UFO:AI
Revision as of 05:36, 3 February 2014 by Duke (talk | contribs) (General Information)
Please do not use a normal text editor, use PoEdit >= 1.5 instead!

General Information

We use gettext for our translations.

  • Grab the latest po file from our repository.
  • Open it in poedit.
  • Submit a patch with the zipped po file as attachment.

That is the easiest and at the same time the worst way to do it. It only works if you are sure that you are the only person working on that translation. Otherwise it can produce merge conflicts and/or duplicate work.

So if you have the chance,

  • use GIT to get the repository
  • create git patches and submit those
  • try to devide your work into logigal chunks and make separate patches

Language-specific Style

In probably every language there are certain recurring words and phrases that can be translated in more than one way, resulting in a slightly different tone. It is of some importance that the same way is chosen throughout UFO:AI. So translators can describe those language-related rules in the following sections. They are of course not in english.

German

Hints

When the UFO gameplay changes, many texts may need adjustments. Hopefully someone does that to the english version. If he does, all the affected texts in all the other languages will be marked as 'fuzzy'. It's very tedious to look through long fuzzy messages only to find that merely half a sentence was changed.

Here's what you can do:

  • get a one year old version of the ufoai-en.po
  • load both that and the current ufoai-en.po in your editor (eg. C::B)
  • use the editor's find cmd to find the fuzzy message in both files
  • copy both messages into WinMerge and compare them

WinMerge can well detect that one changed paragraph, sentence or sometimes even single character. Unfortunately WinMerge isn't available on Linux.

Links