vim-jp/issues — Issue #179: There is the environment where there is two kinds of terminal encoding
Author: Shougo
Created: 2012-03-07 06:59:04+00:00
State: open

This is from this issue: https://github.com/Shougo/vimproc/issues/14

>Yes, I understand the problem. But it looks like Windows encoding mess is so broken that it cannot be fixed with a simple use of encoding and termencoding.

>For instance, for Russian locale on Windows, common encodings are CP1251 for GUI and CP866 for console applications.
>Consequently, vimproc#readdir works fine only if termencoding is cp1251 (encoding can be of any compatible value).
Speaking of console applications, there are two cases:
>1) a console application using CP866. Vimproc works correctly only if enc=tenc=cp866 or enc=cp866, tenc=cp1251. It does not work for enc=utf-8 or other cases.
>2) a console application using CP1251. The output is shown correctly only if enc=tenc=cp1251. Other combinations of utf-8, cp1251, cp866 show garbage.

What should you do for us?