Re: [PATCH 1/2] winepath: add option to output paths in the current Windows ANSI code page
"Lei Zhang" <thestig(a)google.com> writes:
It's occasionally useful to be able to get the Windows path in the Windows ANSI code page, so I added the --ansi command option to winepath.
The ansi code page is not supposed to leak out of a process. What do you need this for? -- Alexandre Julliard julliard(a)winehq.org
On 7/16/07, Alexandre Julliard <julliard(a)winehq.org> wrote:
"Lei Zhang" <thestig(a)google.com> writes:
It's occasionally useful to be able to get the Windows path in the Windows ANSI code page, so I added the --ansi command option to winepath.
The ansi code page is not supposed to leak out of a process. What do you need this for?
-- Alexandre Julliard julliard(a)winehq.org
I have a shell script that calls winepath -w to get the windows path from a unix path. Then I want to stick the value into the registry by a search and replace in ${WINEPREFIX}/*.reg.
"Lei Zhang" <thestig(a)google.com> writes:
I have a shell script that calls winepath -w to get the windows path from a unix path. Then I want to stick the value into the registry by a search and replace in ${WINEPREFIX}/*.reg.
That's a bad idea. You should use regedit, which will avoid potential conflicts with a running session, and will take care of the encoding (the Ansi codepage is *not* the right encoding for reg files). -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
Lei Zhang