Hi Francois, (and everybody else ;)
are there any plans to create an ignore-list for these: http://fgouget.free.fr/wine-po/en_US.spell.html to be able to distinguish real typos from false positives?
Most reported errors are false positives (like "codec" or "checksum") but there are real errors, or at least instances of uncommon spelling (like "customising", which is British English afaik, or "Cancelled") which should be fixed (after 1.4), imho.
Best regards, Julian
On Wed, 29 Feb 2012, Julian Rüger wrote:
Hi Francois, (and everybody else ;)
are there any plans to create an ignore-list for these: http://fgouget.free.fr/wine-po/en_US.spell.html to be able to distinguish real typos from false positives?
[...]
I have not looked at the British vs. American English issues. Part of the reason is that I'm a bit fuzzy on how we use the PO files for these. Is the following correct?
* All of Wine resources are supposed to be 100% American English. * en_US is automatically filled using Wine's resources. * en is manually translated to British English, essentially like any other language.
Why en rather than en_GB? Should en.po only contain translations where British differs from American English? But then how do we know that the translation is complete?
There is also a bug that claims having en.po be incomplete causes trouble, though I could not observe that and am pretty skeptical:
http://bugs.winehq.org/show_bug.cgi?id=29924
Am Freitag, den 16.03.2012, 11:05 +0100 schrieb Francois Gouget:
I have not looked at the British vs. American English issues. Part of the reason is that I'm a bit fuzzy on how we use the PO files for these. Is the following correct?
- All of Wine resources are supposed to be 100% American English.
- en_US is automatically filled using Wine's resources.
- en is manually translated to British English, essentially like any other language.
This should be answered by someone more qualified, but it makes sense to me ;)
Why en rather than en_GB? Should en.po only contain translations where British differs from American English? But then how do we know that the translation is complete?
Maybe we should rename en.po?
There is also a bug that claims having en.po be incomplete causes trouble, though I could not observe that and am pretty skeptical:
Yep, I'm on the CC list for that, but could not reproduce until now. I had an idea that I just checked, and bingo:
LC_MESSAGES=en_GB.UTF-8 LC_CTYPE=fr_FR.UTF-8 ./wine control
seems to work fine (everything in English), but if I replace fr_FR with my system's locale eg:
LC_MESSAGES=en_GB.UTF-8 LC_CTYPE=de_DE.UTF-8 ./wine control
I get a mixed English/German GUI. Will add a comment to the bug.
Best regards, Julian
On Fri, 16 Mar 2012, Julian Rüger wrote:
Am Freitag, den 16.03.2012, 11:05 +0100 schrieb Francois Gouget:
[...]
- All of Wine resources are supposed to be 100% American English.
- en_US is automatically filled using Wine's resources.
- en is manually translated to British English, essentially like any other language.
[...]
Why en rather than en_GB?
Maybe we should rename en.po?
I checked with Alexandre and it turns out en.po is not just used for British but also for Canadian, Australian, etc. That's why it's not called en_GB.po. In theory that means it should contain 'neutral English' but there's not really any such thing so in practice that means it's British English.
And I got confirmation that the en_US.po spelling issues should be fixed in the corresponding RC file. Also, ideally one should provide a command to fixup the PO files to avoid fuzzying the translations every time.
[...]
Should en.po only contain translations where British differs from American English? But then how do we know that the translation is complete?
The thinking is that en.po should probably contain entries for everything even though that may be more work to maintain (really not that much compared to a real translation; imho, maybe even less as it would make keeping it up to date much easier). And that should fix bug 29924.
-
Francois Gouget -
Julian Rüger