Widelands on Windows XP encoding problems

[Country_Man_G]

version WL 6289 ... see also the screenshot

their wrong chars for "umlaute" in the information dialogs

Note:
"ä" is ok
"ß" is ok
"ö" is wrong
"ü" is wrong
......

[Venatrix (elisabeth)]

Can’t reproduce it with rev6297 on Ubuntu Oneiric. The translation seems to be right, too.

[Launchpad Janitor (janitor)]

[Expired for widelands because there has been no activity for 60 days.]

[SirVer (sirver)]

can't reproduce either and no further feedback provided. closing as invalid.

[Venatrix (elisabeth)]

Setting as confirmed, as there was a new bug report (#998894).

Maybe it’s only affected by Windows?

[Shevonar (shevonar)]

I cannot reproduce this bug on Windows 7 with build17.

Another confusing fact is that this bug only mentions ö and ü as broken, while bug 998894 shows that ö, ü and ä, ß are broken.

[Hans Joachim Desserud (hjd)]

The reporter of the duplicate bug was running Windows XP, is this also the case here?

I am not sure exactly where or even if the translation files are included on Windows installations, but could either of you check whether widelands/po/scenario_emp01.wmf/de.po use the correct characters (for instance in the "150 Soldaten" sentence)?

[Nasenbaer (nasenbaer)]

@#7: the *.po files are of course not included. They are only the source from which the *.mo files are derived. And under normal circumstances the *.po files should be the ones from the bzr checkout, as the compilation does not change these files.

I already thought this could be another cross library problem. E.g. an older version of the gettext libraries (that does not support utf-8 (properly) ) installed somewhere in the Windows system directories and used by Widelands instead of the packaged one.

Just my 1¢ of idea ;)

[fuchur (fuchur77)]

It's similar here, with Windows SP 3 and Widelands bzr 6485.
I didn't check all the texts, but "ä" and "ü" seem to be displayed correctly, "ö" is definitely wrong.

[Tino (tino79)]

This bug still exists, more detailled screenshots here: https://wl.widelands.org/forum/topic/1290/

Verified on WinXP with both build 17 and recent build 18 trunk builds.
Does not occure on Windows Vista and Windows 7.

Affects all non-ascii characters, but only in some UI elements (messages, campaign texts) and others not (menus, buttons, window headers).

[SirVer (sirver)]

Mmh, it sems like we do not have a good idea what could be causing this. We might consider just wontfixing this as XP is EOL anyways and I do not feel compelled to support an OS that is no longer supported by its makers. Thoughts?

[Launchpad Janitor (janitor)]

[Expired for widelands because there has been no activity for 60 days.]

[GunChleoc (gunchleoc)]

Duplicate bug: https://bugs.launchpad.net/widelands/+bug/1290049

I noticed that the Russian capital R (which looks like latin P) is not shown correctly in-game. Instead, it's depicted as an E with grave. The word in the screenshot should say 'Рыба'. I can't really narrow it down any more, as some of the words with that letter are shown correctly.

Here's the unicode letter that I'm taking about (just in case)
UTF-8 Code point | Letter | Hex | descr
U+0420 | Р | d0 a0 | CYRILLIC CAPITAL LETTER ER

I am using Windows. However the building names like 'Рудник' are just fine. I'm only seeing this in help texts and scenario stories. Weird.

[Lex (teh-f4ll3n)]

Using Win 7 64-bit, not XP.