Steven Schveighoffer Wrote:
> The responsible party for displaying UTF properly is the console, not the > shell. > One important feature of legacy technology is it must not change for compatibility with legacy code, stdout is just an oblique pipe and one has no means to specify text encoding and legacy applications write OCP-encoded text to stdout, that's why console expects OCP output and breaking this convention will break legacy applications, piping etc, etc. BTW, cmd.exe can in fact produce utf-16 output.
