"Lei Zhang" <[EMAIL PROTECTED]> 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 potenti
On 7/16/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
"Lei Zhang" <[EMAIL PROTECTED]> 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
Hello!
> Did you test this translation? You are using KOI8-R which won't work
> properly in russian resources.
I'm sorry for a carelessness. My current locale was koi8, it became the reason
of my mistake. I resend the patch.
--
Best regards,
Konstantin Kondratyuk.
Alexander Nicolaysen Sørnes:
>> By the way, do you know what's the sublanguage of the Norwegian Windows
>> here.
>> Is it only available in Bokmål or in both variants?
>
> Originally it was only in Bokmål, but I have seen that a few of the recent
> add-on components such as Windows Installer 3.0
Hi, Dmitry!
I have fixed failures in Win2k3 and have posed patch in Wine-Devel.
May be it will be passes in WinXP.
--
Best regards
Anatoly Lyutin.
"Lei Zhang" <[EMAIL PROTECTED]> 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 Julliar
On 7/16/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
I don't think we want to do it that way, we should use a Unix version
of OpenWatcom, and detect it in configure.
The OpenWatcom guys haven't gotten around
to making Linux packages available from their main
download site. It should happe
"Dan Kegel" <[EMAIL PROTECTED]> writes:
> So if I want these in the tree, they should be built and run
> by default. Got it. Next question: is it acceptable to
> require OpenWatcom? (That's the only free compiler I
> know of that targets win16. Turbo C++ is also a free
> download, but it's not
On 7/16/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
I don't think there's any point in putting into the tree test cases
what won't be built or executed. They will just bitrot. We already
have a hard time keeping the normal test suite in a usable state.
So if I want these in the tree, they
"Dan Kegel" <[EMAIL PROTECTED]> writes:
> Given that not many developers will bother installing
> openwatcom just to be able to compile the win16
> tests, I suspect that might be enough of a test
> harness for now. Objections?
I don't think there's any point in putting into the tree test cases
w
10 matches
Mail list logo
