[Bug 11281] New: CJK input many issues

http://bugs.winehq.org/show_bug.cgi?id=11281

Summary: CJK input many issues
           Product: Wine
           Version: 0.9.53.
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=10369)
 --> (http://bugs.winehq.org/attachment.cgi?id=10369)
An approximation of Japanese legacy application

There are so many issues I don't know where to start.

The good thing is the input sort of works so there must be something present in
Wine that handles it one way or another. However, it is unusable in its current
state.

First, a CJK font is needed which is not normally present in Wine. Also Wine
cannot pull characters that do not exist in current font from other fonts so
all relevant system fonts have to be mapped to something that actually contains
the characters.

For Japanese the font Kochi Gothic is quite useful but it does not contain much
in the latin range.

Now in the Wine notepad the Japanese characters are displayed only if you go to
the font selection, select a font with Japanese characters, and select the
Japanese script. I don't know why is that, some Latin accented characters are
displayed even if Japanese script is selected but not the other way around.

Now typing Kana (and even Kanji) works with scim in notepad except the cursor
is always positioned in front of the part just inserted (is not moved after
inserting characters). Doing some cursor movement appears t orestore the cursor
to the right position.

However, typical win32 application is codepage based, and would only work with
SJIS encoding. After generating a SJIS Japanese locale and executing the
included test application with
LANG=ja_JP ./testwin.exe
I get the text displayed correctly. Unfortunately, now the input does not work
because scim runs in UTF-8, and wine in SJIS. This is the same as any other X
applications run in that locale. However, starting a whole X session in an
obscure Japanese locale is not a solution (although it seems the application
would work).