February 2012 - Wine-Devel - list.winehq.org

Re: Translators wanted!

by Cheer Xiao

2012/2/17 Qian Hong <fracting(a)gmail.com>: > Hello, > > On Fri, Feb 17, 2012 at 2:13 AM, Francois Gouget <fgouget(a)free.fr> wrote: >> >> I feel that we should put out a call for translators to the wider >> community. In preparation for that I updated the Wiki's Translating page >> and added a winepo script to help translators who don't want to check >> out the whole Wine source: >> >> http://wiki.winehq.org/Translating >> >> > > I would like to help to update the Simplified Chinese translation, but > most likely I have no enouth time to complete it before wine-1.4 final > release. > Could anyone give a deadline? > > If anyone would like to translate Simplified Chinese please post a > reply here to prevent duplication work. I had maintained zh_CN translation for quite some time, but haven't touched it for about a year (since Wine switched to po files). I might get down to cleaning up zh_CN.po in the near future, but I'll contact you before that. > > Also I'll forward this mail to Traditional Chinese community, since as > a native Simplified Chinese speaker I can't use Traditional Chinese > correctly every time. > > Thanks Francois and the Wine community :) > > -- Regards, Cheer Xiao aka. xiaq

Feb. 27, 2012

Re: po: fixed remaining Slovenian true positives in the winepo error report

by Francois Gouget

On Sun, 26 Feb 2012, Jaka Kranjc wrote: [...] > This is the reason we have some extra newlines in usage strings. I saw you > removed them as part of one of the patches today, but that's potentially a bad > idea. They use a placeholder for the file name and you know how long they can > get, especially if the dir name isn't stripped first. The extra newline saved a > few characters to make it less likely to wrap. Not in the Slovenian translation then? However in the places where I did the translation line length matched the English line to with a few characters so I'd say it's not a significant factor. But if you have specific concerns let me know. > Probably it is best to reword the original string to not use the filename in > the middle of a sentence and then put it into a separate line. The best is to not hardcode wrapping. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ I haven't lost my mind, it's backed up on tape around here somewhere...

Feb. 27, 2012

Re: [PATCH] po: Update Swedish translation.

by Frédéric Delanoy

On Sun, Feb 26, 2012 at 20:47, Francois Gouget <fgouget(a)free.fr> wrote: > On Sun, 26 Feb 2012, Lauri Kenttä wrote: > [...] >> >> +msgstr "Verifiera blev %1\n" >> >> By the way, what do you think about translating "Verify" in the first >> place? It's some kind of flag, and it's left untranslated in many other >> languages. (See VERIFY command in cmd.exe.) > > Verify is the name of a command. But here it does not refer to what the > user has to type to invoke the command so I think translation is ok. It's the name of a command, but arguably kind of the name of a flag, so should probably stay untranslated. However, to get a meaningful message, we probably should have something like "Verification mode is disabled" instead of "Verify is off" for instance, but that will have to wait till after 1.4 release. Frédéric

Feb. 27, 2012

Re: po: zh_TW translation updates

by Francois Gouget

On Sun, 26 Feb 2012, Hin-Tak Leung wrote: [...] > BTW, where was the patch posted? I don't seem to have the very > original patch submission (if it were posted to wine-devel). Patches are posted to wine-patches(a)winehq.org: http://www.winehq.org/pipermail/wine-patches/2012-February/111804.html -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ If you think the whole world revolves around you, quit staring at the GPS display while driving.

Feb. 27, 2012

Re: Wrong charcter encoding in winmm-tests

by Francois Gouget

On Sun, 26 Feb 2012, Julian Rüger wrote: [...] > Then shouldn't most or all of those CP_ACPs (and CP_UTF8s) be replaced > with CP_UNIXCP? No. As I said, all the functions that end with an 'A' are supposed to return ANSI strings and thus must use CP_ACP. Remember that Wine is a Win32 API reimplementation so there are a lot of these Ansi functions. Now the places where we actually have to deal with CP_UNIXCP are pretty rare. You'll have to dig deeper to find exactly why the wrong encoding is used in the winmm test. Maybe it is as simple as passing Ansi strings straight to the native printf implementation? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ "Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds

Feb. 27, 2012

Re: [PATCH] po: Update Swedish translation.

by Lauri Kenttä

On 2012-02-26 21:47, Francois Gouget wrote: > Verify is the name of a command. But here it does not refer to what > the > user has to type to invoke the command so I think translation is ok. The program prints ON or OFF anyway, and I'd personally rather see a message like "VERIFY är OFF" (or even "VERIFY = OFF") than "Verifiera är OFF". Maybe there should be two different messages so that ON and OFF could be translated as well. -- Lauri Kenttä

Feb. 26, 2012

Re: Wrong charcter encoding in winmm-tests

by Julian Rüger

> So I think it's the test that should be performing the apprpriate > conversion (assuming we really care) but I can't remember the details I suppose everyone running the tests should be able to figure it out and set $LANG to en_US or something for the test. But I think this is more widespread: $ grep -d recurse "WideCharToMultiByte(CP_ACP" wine-git|wc -l 662 $ grep -d recurse "WideCharToMultiByte(CP_UTF8" wine-git|wc -l 45 > right now. In particular I'm not sure if using CP_UNIXCP would be > appropriate here. It might depend on the API used to write to stdout. > > And starting from a Unicode string would be much much better too... > (in particular for languages like Japanese, etc.) > I guess UNIXCP is the current codepage the host os uses? Like nl_langinfo(CODESET) from langinfo.h? $ grep -d recurse "WideCharToMultiByte(CP_UNIXCP" wine-git|wc -l 72 Then shouldn't most or all of those CP_ACPs (and CP_UTF8s) be replaced with CP_UNIXCP? Best regards, Julian

Feb. 26, 2012

Re: [PATCH 2/2] ddraw/tests: Add pitch alignment tests

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=17108 Your paranoid android. === WNT4WSSP6 (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw2: unhandled exception c0000005 at 00420FAD === W2KPROSP4 (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw2: unhandled exception c0000005 at 00420FAD === WXPPROSP3 (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw2: unhandled exception c0000005 at 00420FAD === W2K3R2SESP2 (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw2: unhandled exception c0000005 at 00420FAD === WVISTAADM (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw2: unhandled exception c0000005 at 00420FAD === W2K8SE (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw2: unhandled exception c0000005 at 00420FAD === W7PRO (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw2: unhandled exception c0000005 at 00420FAD === W7PROX64 (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw2: unhandled exception c0000005 at 00420FAD === TEST64_W7SP1 (32 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw2: unhandled exception c0000005 at 00420FAD === W7PROX64 (64 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === TEST64_W7SP1 (64 bit ddraw2) === ddraw2.c:1438: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === WNT4WSSP6 (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw1: unhandled exception c0000005 at 0041A3A5 === W2KPROSP4 (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw1: unhandled exception c0000005 at 0041A3A5 === WXPPROSP3 (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw1: unhandled exception c0000005 at 0041A3A5 === W2K3R2SESP2 (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw1: unhandled exception c0000005 at 0041A3A5 === WVISTAADM (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw1: unhandled exception c0000005 at 0041A3A5 === W2K8SE (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw1: unhandled exception c0000005 at 0041A3A5 === W7PRO (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw1: unhandled exception c0000005 at 0041A3A5 === W7PROX64 (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw1: unhandled exception c0000005 at 0041A3A5 === TEST64_W7SP1 (32 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw1: unhandled exception c0000005 at 0041A3A5 === W7PROX64 (64 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === TEST64_W7SP1 (64 bit ddraw1) === ddraw1.c:1175: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === W2KPROSP4 (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw7: unhandled exception c0000005 at 0042E3E1 === WXPPROSP3 (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw7: unhandled exception c0000005 at 0042E3E1 === W2K3R2SESP2 (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw7: unhandled exception c0000005 at 0042E3E1 === WVISTAADM (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw7: unhandled exception c0000005 at 0042E3E1 === W2K8SE (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw7: unhandled exception c0000005 at 0042E3E1 === W7PRO (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw7: unhandled exception c0000005 at 0042E3E1 === W7PROX64 (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw7: unhandled exception c0000005 at 0042E3E1 === TEST64_W7SP1 (32 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw7: unhandled exception c0000005 at 0042E3E1 === W7PROX64 (64 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === TEST64_W7SP1 (64 bit ddraw7) === ddraw7.c:1336: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === W2KPROSP4 (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw4: unhandled exception c0000005 at 00427CC1 === WXPPROSP3 (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw4: unhandled exception c0000005 at 00427CC1 === W2K3R2SESP2 (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw4: unhandled exception c0000005 at 00427CC1 === WVISTAADM (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw4: unhandled exception c0000005 at 00427CC1 === W2K8SE (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x887601fe. ddraw4: unhandled exception c0000005 at 00427CC1 === W7PRO (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw4: unhandled exception c0000005 at 00427CC1 === W7PROX64 (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw4: unhandled exception c0000005 at 00427CC1 === TEST64_W7SP1 (32 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. ddraw4: unhandled exception c0000005 at 00427CC1 === W7PROX64 (64 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout === TEST64_W7SP1 (64 bit ddraw4) === ddraw4.c:1549: Test failed: D3DPOOL_DEFAULT: Failed to create surface, hr 0x88760233. Timeout

Feb. 26, 2012

Re: Wrong charcter encoding in winmm-tests

by Francois Gouget

On Sun, 26 Feb 2012, Julian Rüger wrote: > OK, I think I finally found out what's going on here: > > in waveform.c waveOutGetErrorTextA() calls > WideCharToMultiByte(CP_ACP,.... with the ANSI codepage. > When I change that to CP_UTF8, it works as expected. > > Is this fix OK, or does that break anything? Should I send a patch? waveOutGetErrorTextA() is correct. As its name indicates it's supposed to return an ANSI string. So I think it's the test that should be performing the apprpriate conversion (assuming we really care) but I can't remember the details right now. In particular I'm not sure if using CP_UNIXCP would be appropriate here. It might depend on the API used to write to stdout. And starting from a Unicode string would be much much better too... (in particular for languages like Japanese, etc.) -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Broadcast message : fin du monde dans cinq minutes, repentez vous !

Feb. 26, 2012

Re: [PATCH] po: Update Swedish translation.

by Francois Gouget

On Sun, 26 Feb 2012, Lauri Kenttä wrote: [...] > >> +msgstr "Verifiera blev %1\n" > > By the way, what do you think about translating "Verify" in the first > place? It's some kind of flag, and it's left untranslated in many other > languages. (See VERIFY command in cmd.exe.) Verify is the name of a command. But here it does not refer to what the user has to type to invoke the command so I think translation is ok. Also note that whichever policy is selected here should also apply to the 'echo' command and maybe others: #, fuzzy msgid "Echo is %1\n" msgstr "Ekot är %s\n" -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ War doesn't determine who's right. War determines who's left.

Feb. 26, 2012