Closed GoogleCodeExporter closed 8 years ago
Original comment by andy.koppe
on 9 Apr 2009 at 9:40
Hello.
I wrote the patch for this problem.
The change was written referring to the source of putty.
Operation is confirmed in a Japanese environment.
thanks.
Original comment by oustt...@gmail.com
on 14 Apr 2009 at 6:33
Attachments:
IME active but my language (korean) string is broken!
font codepage set UTF-8 exact display but "use font encoding" set broken!;
My codepage CP949 but not list codepage.
Original comment by noull...@gmail.com
on 14 Apr 2009 at 7:25
I wrote additional patch for comment 3 UTF-8 problem.
It refers to the source of windows/window.c@putty-0.60.
But I don't have Korean environment. Please check it.
Original comment by deenhe...@gmail.com
on 14 Apr 2009 at 1:58
Attachments:
Re-added IME support in r235 on trunk. Thanks for the patches; I ended up doing
much
the same thing.
Not sure why I ever removed the support in the first place. Perhaps I was under
the
impression that DefWindowProc would do the right thing for IME messages. Still
wondering whether there isn't a better approach than Putty's for supporting IMEs
though ...
Anyway, please give this a try. Also, pointers on how to to test IMEs properly
would
be much appreciated (Cygwin version, environment variables, font and codepage
settings).
Original comment by andy.koppe
on 14 Apr 2009 at 10:06
Took fix to 0.3 branch in r249.
Original comment by andy.koppe
on 24 Apr 2009 at 8:52
r237 on trunk was part of the fix too. Taken to 0.3 branch in r252.
Original comment by andy.koppe
on 24 Apr 2009 at 9:08
Original comment by andy.koppe
on 25 Apr 2009 at 1:55
Original issue reported on code.google.com by
noull...@gmail.com
on 9 Apr 2009 at 2:06