Re: List control Korean Unicode Chars - No problem with managed code

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sat, 7 Apr 2007 21:44:26 -0700

Message-ID:

<395A76D3-A903-4BDF-9BFF-AB272E6DB753@microsoft.com>

I have a difficult time believing that underneath it all it's not still
Win32 at some point and, although I don't know how .NET is implemented
exactly, I'd be surprised if they redrew every control that Windows
supports. Also, the use of a BOM is pretty non-standard on Windows. I use
it in my files and lots of times Notepad, for example, just displays little
strange looking characters instead of ignoring the BOM. My guess is
somewhere in the original code the strings are getting translated using an
invalid codepage or ACP when the wrong region is loaded.

I never have problems with Korean or Japanese in my list controls in MFC,
but I do have trouble if I try to run them under English Windows for example
rather than one with the Asian IME loaded.

Tom

"MrAsm" <mrasm@usa.com> wrote in message
news:cecf13pnnafmlptovffgfic7svomcn8eri@4ax.com...

I tried to recreate the same problem discussed in thread

"CListCtrl unicode doesn't display korean characters correctly"

under VC#2005 Express in WinForm dialog-box, and there is no problem
in that context.

I also gave a look with Spy++ to the list control of the .NET world,
and it seems a different thing from the Win32 controls (its class name
is "WindowsForms10.SysListView32.app.0.b7ab7b").

I wonder if the .NET developers:

1. rewrote the controls from scratch (not reusing Win32 controls)

2. put a BOM in front of each Unicode strings... :)

3. ?

Still no answer from the
microsoft.public.win32.programmer.international newsgroup. Still no
simple message from anyone from Microsoft like "we are investigating
the problem...".

MrAsm