Latest Posts

Changes in TranslatingWidelands

Editor Comment

New section "How to deal with changes in the source language"

Revision Differences of Revision 12

## Translating Widelands ¶

Like all development, translations are also done on []( All translation work is done in your web browser and everybody can contribute translations in any language in seconds. ¶

**note**: there are [TranslationDictionaries]( for most common words - please use these words (like building names, ...) for a consistent translations ¶

The process is quite simple: ¶

1. Sign up on [Click here]( ¶
2. Tell Launchpad which languages you want to work with: [Click here]( ¶
3. Start translating widelands: [Click here]( ¶
1. You can see all statistics of all languages Widelands is translated into. ¶
2. Click on your language, choose the text domain (widelands, maps, scenarios...) you want to work on. ¶
3. Start translating. ¶
4. If you don't know how to translate Wideland's words (names of wares, workers, buildings etc.), please look in the TranslationDictionary, if one exists for your language. If not, please use the translations already implemented in the game - and feel free to start a new Translation dictionary for your language. ¶
5. Further discussion is made in the [Forum Translation & Internalization]( ¶

All translations will eventually land in a bzr branch via autoimport from launchpad. We will then merge them before a release, so your translation will make it to widelands. All new translations you make are under a BSD license - this basically means that other projects on Launchpad can use them too. ¶

Further reading: [Launchpad Translation Documentation]( ¶

## How the translations are organized ¶
In some cases, you wish to find a specific string of text, either because it has not been translated yet, or you want to improve the current translation/fix a typo. The translation templates are split up rather logically, so as long as you know where to look, you'll most likely find it. The following descriptions of the various templates are partially based on a [question asked on Launchpad]( ¶

Template | Description ¶
------- | -------- ¶
widelands | contains everything not covered elsewhere, including all menus, options, error messages, buttons, dialogs and other things in the game. If it is something which does not seem to fit in any of the other templates, it is most likely located here. ¶
maps | contains names and descriptions of maps which are shown when selecting which map to play. ¶
tribe-* | contains names and descriptions of wares, workers and buildings (including help texts) for the tribe. ¶
scenario-tutorial1 | the tutorial available from the main menu ¶
scenario-* | the history/dialog in the campaigns. They are numbered like the order they appear in, and identified by atl (atlantean), emp (empire) or t (barbarian) prefix before the number. I guess t=barbarian as those maps were added first, when there was only one campaign. ¶
world | the trees, stones, creatures etc. on the map. ¶
win-conditions | description of the various types of games and messages with "you have won/lost" ¶
texts | includes the README, credits, the hints shown when loading the game, and similar things. ¶
map-plateau.wmf | the story for "The green plateau", a scenario. ¶
mp-scenario-* | Text used in the multiplayer scenarios, identifiable by name. ¶
scenario-dummy.wmf | the placeholder map informing the player that no further maps/campaigns exists. ¶

###An example: ¶
Say for instance if you are playing the second mission in the barbarian campaign and notice some typo in the story text. Then it would would make sense to search in scenario-t02.wmf, since that contains all translations for the second map in the barbarian campaign. ¶

## How to deal with changes in the source language ¶

Because we're still in Alpha, it can happen that we need to break some of your translations. Sometimes, it is just a matter of a fixed typo, but Launchpad will kill your translations anyway. Sometimes, we can have pretty big changes, although we do our best to avoid them. There are two ways to deal with this: ¶

### Using an offline translation tool ¶

We highly recommend that you use an offline translation tool if you plan to translate a sizeable chunk or to work on this project continuously. The two most common tools that we can recommend are [Virtaal]( and [Poedit]( They both work fine - pick the one you prefer. Launchpad offers you to download / upload a file when you're in the translation view, so you will get the files to translate from there. ¶

These offline tools come with a translation memory, which means that they will remember all the translations that you have saved, ever. So, if a file with a slightly changed source text comes along, the tool will show you a suggestion and also mark the differences. This is also convenient for translating strings that are similar - we have a number of those in the project, especially with the tribes. The tool will help you keep consistency with your translations and also reduce the amount typing that you need to do. ¶

### Accessing older versions of your translation on Launchpad ¶

If you haven't been using an offline tool, you can still access previous versions of your translation. For this, you will need to ¶

* [browse the revision history]( of the code. ¶

* Use the "<< Newer" / "Older >>" links on the bottom to navigate to a date, then click on the name of the revision you wish to access. ¶

* Click on "browse files at revision <number>" ¶

* In the "Filename" column, click on "po" ¶

* Select the translation template and then the file with your language code, e.g. "maps" and "de.po" for the German translation of the "maps" template. ¶

* If you don't fancy reading the source code version of the file, click "download file" on the top right. You will then need to get an offline translation tool like [Virtaal]( and [Poedit]( if you haven't already installed one.