How to test latest translations?

Asked by Hans Joachim Desserud on 2010-05-25

As the title says, how can I test the game with the latest translations?
At present, I stay up to date by downloading new revisions and compiling the trunk. This part works without problems. In addition to testing the latest version, I would now like to be able to check which parts of the translations are missing, or even worse, wrong. I have downloaded the branch containing the latest translations, but I haven't been able to find any instructions how to combine these with the latest build. I tried to simply copy over the po-folder, though that didn't seem to do much.
Though that might be caused by the fact that I haven't really been able to play the game using any translations at all. Since I am on Ubuntu (10.04) I have tried the first workaround here (http://wl.widelands.org/wiki/WidelandsFaq/#translations_wont_work_in_ubuntu_linux) but it didn't seem to work. I have not tried the second workaround, as I would like to check a bit more what it really does, before trying it. Also, the FAQ said either of them should work.

Question information

Language:
English Edit question
Status:
Solved
For:
widelands Edit question
Assignee:
No assignee Edit question
Solved by:
Timowi
Solved:
2010-09-08
Last query:
2010-09-08
Last reply:
2010-05-26
Best Timowi (timo-wingender) said : #1

Translation are exported to the branch ~sirver/widelands/translations. You can merge this with

bzr merge lp:~sirver/widelands/translations

into an existing widelands trunk. You can also download the translation files from launchpad and copy the the the widelands directory.

The translation are only build automatically for release build. Either run cmake with "-DCMAKE_BUILD_TYPE=Release" or run "make lang" yourself. Note: it necessary to run "make install" or copy/symlinking the directory locale for the build directory to the base source directory. The build_and_run.sh creates this symlink but does not run "make lang". If the translations still do not work try to set the variable language in the widelands config file to an existing locale of your system.

Hans Joachim Desserud (hjd) said : #2

Thanks Timowi, that solved my question.

Hans Joachim Desserud (hjd) said : #3

Thanks, that seemed to work.

If anyone else has the same question:
Translations are merged into trunk from time to time.
I've discovered that due to recent changes, compile.sh will now ask whether or not translations should be built when compiling widelands.

PS. I thought I had answered this a long time ago.