at crossed purposes now. Remember
that my original question had nothing to do with paths. I simply used paths as
a convenient example. My question is about command-line parameters and (more
specifically) about UTF-8 string conversion. Here's an example Consider a
Windows user whose name
--- On Tue, 12/6/12, John Emmas john...@tiscali.co.uk wrote:
snipped
Thanks Hin-Tak and Dan but I think we're at crossed purposes
now. Remember that my original question had nothing to
do with paths. I simply used paths as a convenient
example. My question is about command-line parameters
On 12/06/2012 8:59 PM, John Emmas wrote:
Thanks Hin-Tak and Dan but I think we're at crossed purposes now.
Remember that my original question had nothing to do with paths. I
simply used paths as a convenient example. My question is about
command-line parameters and (more specifically) about
--- On Thu, 7/6/12, John Emmas john...@tiscali.co.uk wrote:
snipped
Is Wine clever enough to realise that the UTF8 string needs to be converted
to a locale-specific string, so that the Windows app can understand it? Or
does Wine simply pass whatever characters it received, without
--- On Thu, 7/6/12, John Emmas john...@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
--- On Thu, 7/6/12, Dan Kegel d...@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
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
On 7 Jun 2012, at 10:27, Hin-Tak Leung wrote:
The short answer is that wine *does* translate from unix-like to windows-like
file paths so that the application receives the right stuff. You have nothing
to worry about.
I must admit, that was what I hoped to hear! I don't suppose it
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
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
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
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
12 matches
Mail list logo
