WineHQ Bugzilla – Bug 29924 – control and inetcpl show some texts in wrong language

Bugzilla

Last modified: 2015-02-20 08:26:17 UTC

control and inetcpl show some texts in wrong language

Bug 29924 - control and inetcpl show some texts in wrong language


Summary:	control and inetcpl show some texts in wrong language

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.4-rc4
Hardware:	Other other

Importance:	P2 minor
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2012-02-18 04:03 UTC by Lauri Kenttä
Modified:	2015-02-20 08:26 UTC (History)
CC List:	2 users (show)

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Lauri Kenttä 2012-02-18 04:03:07 UTC

LC_MESSAGES=en_GB.UTF-8 LC_CTYPE=fr_FR.UTF-8 ./wine control

The command above makes Wine use mostly English, but a few texts are in French instead: the Control panel title, the inetcpl menu item and description, inetcpl title and the text that should say "Security settings for zone:" on the Security tab.

Using en_US instead of en_GB works fine. Apparently Wine does something strange when it can't find a translation that matches exactly the given LC_MESSAGES locale.

How to reproduce:
* Make sure you have the required locales on your system
* Set LC_MESSAGES=en_GB.UTF-8
* Set LC_CTYPE=fr_FR.UTF-8
* Run wine control

Comment 1 Lauri Kenttä 2012-02-18 14:27:57 UTC

"Trash" in explorer.exe also does this.

Comment 2 Lauri Kenttä 2012-03-03 08:49:47 UTC

The reason for this behaviour is that the English neutral sublanguage (en.po) is missing a lot of texts. This seems a bit weird considering that English is the primary language for the project. Is it really important to go though all the texts and check that they're "neutral", or would it be ok to just copy the msgids to msgstrs for the missing texts?

Comment 3 François Gouget 2012-03-16 05:02:02 UTC

I ran the command you specified on my computer:
LC_MESSAGES=en_GB.UTF-8 LC_CTYPE=fr_FR.UTF-8 ./wine control

But all I get is English, not a trace of French anywhere. Could you recheck?
My understanding is that wrc is supposed to generate a fully translated set of resources, using the msgid whenever a translation is missing. So having missing translations in en.po should simply result in Wine's default strings (more or less American English) being used.

Comment 4 Julian Rüger 2012-03-16 08:43:26 UTC

Confirming.

I could not reproduce this until I replaced fr_FR with my system's current locale.

In other words:

LC_MESSAGES=en_GB.UTF-8 LC_CTYPE=fr_FR.UTF-8 ./wine control

seems to work fine on a non-french system, all strings in English, but e.g.

LC_MESSAGES=en_GB.UTF-8 LC_CTYPE=de_DE.UTF-8 ./wine control

for a German system shows a mixed German/English GUI.

Comment 5 Lauri Kenttä 2012-03-16 09:42:35 UTC

> But all I get is English, not a trace of French anywhere. Could you recheck?

I've checked it many times. Do you have the locales installed?
locale -a | grep -e en_GB -e fr_FR

> My understanding is that wrc is supposed to generate a fully translated set
> of resources, using the msgid whenever a translation is missing.

Yes, if the resource exists at all. For example, if I add a translation for msgid "Configure Wine Internet Browser and related settings", the previous msgid "Internet Settings" magically works, too. However, if the resource (STRINGTABLE or whatever) is empty, it's not generated.

Comment 6 François Gouget 2012-03-26 11:16:43 UTC

I thought I had en_GB.UTF-8 but I did not (apparently I only had en_US.UTF-8). I have added it and now I can reproduce the problem. Sorry about that.

Comment 7 Lauri Kenttä 2013-02-24 14:31:08 UTC

With en.po at 98%, should we mark this fixed? The behaviour hasn't changed, so the bug will come back if en.po isn't kept up to date.

Comment 8 François Gouget 2015-02-11 05:17:20 UTC

I think we can consider this fixed. The en_GB translation is currently at 100% and it's just a matter of keeping it up to date like every other translation.

Comment 9 Alexandre Julliard 2015-02-20 08:26:17 UTC

Closing bugs fixed in 1.7.37.