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

Re: [PATCH 4/4] mshtml: Added IWindowForBindingUI 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=18890 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

June 8, 2012

Re: Command line parameters

by John Emmas

On 7 Jun 2012, at 21:04, Dan Kegel wrote: > John wrote: >> FWIW the Windows app launches perfectly if I use execl() in the Linux app - and in fact, this has all worked perfectly for years. > > That's great. Do you actually pass filenames? > Yes, our host app is cross-platform (Windows, Linux and OS-X). On all 3 platforms it passes a file path to the Windows/Wine client app. On Windows, this file will be in the user's "My Documents" folder (e.g. C:\Documents and Settings\[user name]) so there's a very good chance that in non-English locales, the user name might have non-Latin characters. For that reason we specifically have to make a translation from UTF-8 ourselves. However, it only occurred to me a few days ago that (even though we don't translate the file path on the non-Windows platforms) nobody has ever complained. This suggests either that the paths (on those platforms) never have names with non-Latin characters - or that Wine is silently making the conversion for us. To be honest, I've no easy way of knowing which explanation is the true one. In fact, they could both be true! John

June 8, 2012

Re: [4/4] windowscodecs: Add WICIfdMetadataReader registration. Resend.

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=18888 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

June 8, 2012

Re: Re: Patch 2/2 - [scrrun] - Add initial tests for Dictionary - resend

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=18875 Your paranoid android. === WINEBUILD (build) === Make failed

June 7, 2012

Re: Command line parameters

by Ben Peddell

On 8/06/2012 4:57 AM, John Emmas wrote: > FWIW the Windows app launches perfectly if I use execl() in the Linux app - and in fact, this has all worked perfectly for years. It was only yesterday that I began to wonder if there might be a problem in non-English locales. Up to now, nobody's ever reported a problem (though, as we all know in programming, that doesn't mean there isn't one!) Wine (and Windows NT OSes) use unicode for the command-line. Wine would convert the UTF-8 unix command-line to a UTF-16 Windows command-line. It is then up to the Windows locale conversion to convert that UTF-16 string to the locale's character set. -- Ben Peddell IT Support Bowen, Collinsville and Proserpine Catholic schools http://klightspeed.killerwolves.net/

June 7, 2012

Re: [PATCH 1/1] shell32: Fix FindExecutable search path when a default directory is supplied.

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=18869 Your paranoid android. === WNT4WSSP6 (32 bit shlexec) === shlexec.c:1336: Test failed: FindExecutable(notepad.exe) returned command=[C:\WINNT\System32\notepad.exe] shlexec.c:1342: Test failed: FindExecutable(notepad.exe) returned command=[C:\WINNT\System32\notepad.exe] === W2KPROSP4 (32 bit shlexec) === shlexec.c:1336: Test failed: FindExecutable(notepad.exe) returned command=[C:\WINNT\system32\notepad.exe] shlexec.c:1342: Test failed: FindExecutable(notepad.exe) returned command=[C:\WINNT\system32\notepad.exe]

June 7, 2012

Re: Command line parameters

by Hin-Tak Leung

--- On Thu, 7/6/12, Dan Kegel <dank(a)kegel.com> wrote: > John wrote: > > from what Hin-Tak said earlier, it sounds like Wine > itself will translate any paths that I pass as a command > line parameter (or did I misunderstand that?) > > Example: > wine notepad /home/dank/foo.txt > This fails because notepad treats / as the beginning of an > option (see http://source.winehq.org/source/programs/notepad/main.c#L616 > ). > > So, no, Wine doesn't translate arguments for you. It would probably work in any of these though: z:/home/dank/foo.txt h:/foo.txt \\home\\dank\\foo.txt h:\\foo.txt (the double backslash for its been interpreted by bash, or whatever shell you use) or cd /home/dank && wine notepad foo.txt > > FWIW the Windows app launches perfectly if I use > execl() in the Linux app - and in fact, this has all worked > perfectly for years. > > That's great. Do you actually pass filenames? > - Dan That probably means it does not use "/" for options . ("-" or no options at all?).

June 7, 2012

Re: Command line parameters

by Dan Kegel

John wrote: > from what Hin-Tak said earlier, it sounds like Wine itself will translate any paths that I pass as a command line parameter (or did I misunderstand that?) Example: wine notepad /home/dank/foo.txt This fails because notepad treats / as the beginning of an option (see http://source.winehq.org/source/programs/notepad/main.c#L616 ). So, no, Wine doesn't translate arguments for you. > FWIW the Windows app launches perfectly if I use execl() in the Linux app - and in fact, this has all worked perfectly for years. That's great. Do you actually pass filenames? - Dan

June 7, 2012

Re: Command line parameters

by Hin-Tak Leung

--- On Thu, 7/6/12, John Emmas <johne53(a)tiscali.co.uk> wrote: <snipped> > FWIW the Windows app launches perfectly if I use execl() in > the Linux app - and in fact, this has all worked perfectly > for years. It was only yesterday that I began to > wonder if there might be a problem in non-English > locales. Up to now, nobody's ever reported a problem > (though, as we all know in programming, that doesn't mean > there isn't one!) That depends on whether your application uses the *W file operation WIN32 api or the much older *A routines. For example, I have a quick look at bcc32.exe (part of borland's compiler, time stamp july 2000, 12 years old) with 'winedump -j import bcc32.exe' . It loads only 3 *W routines but 25 of the *A ones. Whereas cl.exe from visual c++ express 9 (2008, 4 years old) loads 31 *W routines and only 2*A routines. So MS VC 9 is far happier in non-English locale than the much older borland 5.5 compiler.

June 7, 2012

Re: Command line parameters

by John Emmas

On 7 Jun 2012, at 19:30, Dan Kegel wrote: > John asked >> [ How do I launch Windows apps from Unix apps and pass filenames to them?] >> execl (the_path_to_wine, "wine", path_to_the_windows_program, command_line_parameter_for_windows_app, NULL); > > Relative unix paths will often work with Windows apps, but > in general, you will have to translate > command_line_parameter_for_windows_app, and any > paths that appear in data files, from Unix to Windows before launching the app. > Thanks Dan, Paths in data files I can understand but from what Hin-Tak said earlier, it sounds like Wine itself will translate any paths that I pass as a command line parameter (or did I misunderstand that?) FWIW the Windows app launches perfectly if I use execl() in the Linux app - and in fact, this has all worked perfectly for years. It was only yesterday that I began to wonder if there might be a problem in non-English locales. Up to now, nobody's ever reported a problem (though, as we all know in programming, that doesn't mean there isn't one!) John

June 7, 2012