Translators Guide (Windows)

Note: This guide assumes you are able to check out the sources and can either commit changes or submit patches to the developers.

Just want to translate? Try the Web-based Translation Tool instead.

Translation editing

The .po files are in the "po" subdirectory. Although the .po files are text files, we highly recommend you use a catalog editing app to edit the files to make sure that the metadata is updated.

Windows .po editors:

•  Poedit

Installing the Gettext tools

Note: This is only for developers and testers.

The latest Gettext tools for Windows can be downloaded here (no installer):
 http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/gettext-tools-0.17.zip

Be sure to add the tools to your PATH.

Updating the translations

Note: This is only for developers.

This will extract the translatable strings from the C++ sources and merge the entries into the .po files.

First, install the Gettext tools (see above).

Then, run (from the directory where you checked out the sources):

build\update-po

Compiling the translations

Note: This is only for developers and testers.

This will compile the .po files into .mo files.

First, install the Gettext tools (see above).

Then, run (from the directory where you checked out the sources):

build\gen-mo

The compiled .mo files can be found in the share/locale folder.

Testing the translations

Option 1: Set the "LANG" environment variable when running hoverrace.exe:

set LANG=en_US@piglatin
Debug\HoverRace

Option 2: Pass the "-L" command-line argument to hoverrace.exe:

Debug\HoverRace -L en_US@piglatin

Option 2 is useful if you want to run the game from the Visual Studio debugger:

1. Right-click on the "client" project and select "Properties".
2. Select the "Debugging" section.
3. Add the command-line arguments to "Commmand Arguments" (e.g. "-L en_US@piglatin").