Enforcing charset/codepage (was: Commit 37591409b28c2000e70bd0d3c654a3a7559a4a26 breaks accentuation)

[Pedro Araujo Chaves Jr.]

Follow-up...

I recall that forcing the charset to be ANSI_CHARSET instead of
DEFAULT_CHARSET [1] "fixed" bug 7571 [2] here, and from that rose an
idea: would it be possible to add an option to winecfg to enforce a
particular charset/codepage, much like it is already done in web
browsers? That way, we here wouldn't have to face 7571 while the fix
isn't ready.

Is such a thing acceptable?

TIA,
- Pedro.

[1] http://www.winehq.org/pipermail/wine-patches/2007-March/036538.html
[2] http://bugs.winehq.org/show_bug.cgi?id=7571

P.S.: TMTC, I'm still working on 7571; 7703's been taking a lot of my time...

Enforcing charset/codepage (was: Commit37591409b28c2000e70bd0d3c654a3a7559a4a26 breaks accentuation)

[Dmitry Timoshkov]

"Pedro Araujo Chaves Jr."  wrote:
> I recall that forcing the charset to be ANSI_CHARSET instead of
> DEFAULT_CHARSET [1] "fixed" bug 7571 [2] here, and from that rose an
> idea: would it be possible to add an option to winecfg to enforce a
> particular charset/codepage, much like it is already done in web
> browsers? That way, we here wouldn't have to face 7571 while the fix
> isn't ready.
>
> Is such a thing acceptable?

As the test case shows that's not how Windows does things. All we have
to do is to make the test fully pass under Wine, and it will fix your
problem as well.