On Wednesday, January 1, 2014 6:15:18 AM UTC+8, LiTuX wrote: > Since msys-bash has the same issue, while msysgit's bash fixed it, I think > there must be some way to fix this issue. So will anyone post a patch?
Actually the mechanism is like that: IME(unicode) --> Console(CP936) --> vim(any codepage or utf-8) IME generates unicode characters, which tossed away by Windows Console because it can only accept codepages. Therefore you will see "different" or "corrupted" characters appear in vim. This is a "live long" problem of Windows console in all versions of Windows, which Microsoft never care to fix in the past, now, or in the future. So when using vim under Windows environment, please use gvim, which bypass the trouble: IME(unicode) --> gvim(unicode or utf-8) Cheers -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
