No Skirmish button (Beta2)

[Devil12]

Well this looks funny.
Where normally an "one Player Skirmish"-button should be, is nothing, but when I klick on the place, the menu comes.
I'm using Win XP SP2 and the German Translation of Warzone (as you can see).

[doom3r]

Try clicking on it anyway, I think it will work. Thats because of a translation problem (translation needs to be upgraded to new version).

[Devil12]

I already wrote that it works.
Is there already a newer version?
If yes, where can I find it?

[doom3r]

No, they were 95% on the old translation phase, which happened before the beta. In the beta some menu changed, so someone should translate the new strings...

[DevUrandom]

Untranslated strings show up as english.
This is http://gna.org/bugs/?11277

[Devil12]

How cam I fix it myself?

[Kamaze]

Just click there, where the text should be.

[Devil12]

I mean the problem that no text is displayed, I already played skirmish.

[Kamaze]

Wait for beta3

[Buginator]

How cam I fix it myself?

Quickest fix is to play in English.

Next quickest way is to compile (the latest version) it yourself, and see if it is fixed.

[Hatsjoe]

it's not really a big issue now is it ?
Check the translation file in the trunk to see whats wrong with your language. I understand that when no translation has been given for a certain piece of original text, the game uses the english text instead. So maybe the one who has done the translation typed in blanks or something.

[Buginator]

it's not really a big issue now is it ?
Check the translation file in the trunk to see whats wrong with your language. I understand that when no translation has been given for a certain piece of original text, the game uses the english text instead. So maybe the one who has done the translation typed in blanks or something.

No, that isn't the issue.  The issue is (was?) it isn't drawing the text if you have Umlaute(s) in the text string.

Hopefully, that is solved now.

[DevUrandom]

It is solved now. I released a patch for non-Windows users (namely Linux distributors) and for the Windows users a new installer.
The issue was that the translation could have a different character encoding than what we told the fontrenderer he would get. And if he gets feed with something he does not expect, he just stops drawing it.

You might have fixed it (on Linux at least, have no tested whether it works on Windows, too) by setting the environment variable "LANG" to "xx_XX.UTF-8".
I.e. for a german run "LANG=de_DE.UTF-8 warzone2100" from a console (Bourne Again Shell / bash).
If it works on Windows (untested, see above) it would be

Code: Select all

set LANG=de_DE.UTF-8
cd C:\Path\To\Warzone
warzone2100.exe

[Buginator]

You might have fixed it (on Linux at least, have no tested whether it works on Windows, too) by setting the environment variable "LANG" to "xx_XX.UTF-8".
I.e. for a german run "LANG=de_DE.UTF-8 warzone2100" from a console (Bourne Again Shell / bash).
If it works on Windows (untested, see above) it would be

Code: Select all

set LANG=de_DE.UTF-8
cd C:\Path\To\Warzone
warzone2100.exe

Just a FYI, but with the 'official' beta 2 release, in windows, you can change languages just fine.

However, if you compile the MSVC version, you can't, since the libs/dlls are pretty old, and like to crash on some things.
One of these days, we will all be using the same libs, and this issue will be moot.  :-X