Wouldn't you bet, Fret (aka You've got 50 ways to fix your characters)

re: Wouldn't you bet, Fret (aka You've got 50 ways to fix your characters)

Aaron Ballman — Thu, 27 Sep 2007 21:07:23 GMT

"Just be patient, everybody will be Unicode sooner or later (right after U.S. finally adopts the metric system :-)"

Don't forget about converting everyone in Liberia and Myanmar too. ;-)

re: Wouldn't you bet, Fret (aka You've got 50 ways to fix your characters)

Michael S. Kaplan — Thu, 27 Sep 2007 20:54:26 GMT

The only way to do that would be to change the code page to add new best fit mappings, which we cannot do for stability reasons....

re: Wouldn't you bet, Fret (aka You've got 50 ways to fix your characters)

Mihai — Thu, 27 Sep 2007 20:48:25 GMT

Although Windows might try and convert the WM_CHAR Unicode to ANSI using best fit. Then U+0219 would be converted to 0xBA cp1250 (U+015F).

But well ...

Sometime I wish that some change of change that requires Unicode would badly break English functionality :-)

Everybody will be unhappy for a while, move to Unicode, but in the end we will be in a better state.

Just be patient, everybody will be Unicode sooner or later (right after U.S. finally adopts the metric system :-)

re: Wouldn't you bet, Fret (aka You've got 50 ways to fix your characters)

Aaron Ballman — Thu, 27 Sep 2007 18:26:22 GMT

I ran into this issue myself (back when our application had to have a single binary to support Windows 98 and up), and the issue turned out to be the fact we were using Unicode in most places (such as defining the window and within the WndProc), with an accidental ANSI call to GetMessage/DispatchMethod in our mesage pump.

I am so happy we changed our requirements to Win2k and up so this sort of weirdness doesn't happen anymore! ;-)