Re: Re: On Windows(R) Emacs «shell» mode doesn't prints an output.

[Eli Zaretskii]

> Date: Thu, 25 Sep 2014 15:25:48 +0700
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> 
> On Thu, Sep 25, 2014 at 2:43 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >> I thought that the problem is in encoding, and set «shell»'s buffer
> >> with «C-x <RET> f» to UTF-16, which, as I know, uses MS, but it didn't
> >> fixed the problem.
> >
> > Console applications on Windows use the current OEM codepage, not
> > UTF-16.
> 
> This is correct in general, although *some* Windows console
> applications can be persuaded to output in UTF-16. (The only example I
> know of is cmd.exe /U.)

cmd.exe is not a "normal" console application.  And AFAIK, the /U
switch only affects output to files and pipes, not to the console.

> Also, there is an unofficial unsupported ugly hack to use “chcp 65001”
> which makes applications think that the current OEM codepage is UTF-8.
> (It is unsupported because that there is some code that assumes at
> most two bytes for each character, while UTF-8 may produce up to
> four.)

First, UTF-8 is still not UTF-16.

And second, there's nothing unsupported about codepage 65001, the only
problem with switching the console to that codepage is that the fonts
available for it in the console cover only a very small portion of the
BMP, so you don't really get a Unicode-capable console.