https://issues.dlang.org/show_bug.cgi?id=1448

--- Comment #18 from kinke <kinke@gmx.net> ---
This isn't solved, but would now be solvable with recent Windows versions.

There are 2 things about this:
* DMD outputs a mix of UTF-8 and strings in the current codepage, AFAIK without
setting any console codepage, so DMD output on Windows can be garbage. LDC
v1.17 fixes this for LDC.
* User programs writing UTF-8 strings to the console suffer from the same
issue. This *could* be worked around by setting the console codepage in
druntime's _d_run_main and resetting it to the original one before termination.

--

https://issues.dlang.org/show_bug.cgi?id=1448

--- Comment #19 from RazvanN <razvan.nitu1305@gmail.com> ---
(In reply to kinke from comment #18)
> This isn't solved, but would now be solvable with recent Windows versions.
> 
> There are 2 things about this:
> * DMD outputs a mix of UTF-8 and strings in the current codepage, AFAIK
> without setting any console codepage, so DMD output on Windows can be
> garbage. LDC v1.17 fixes this for LDC.

How does LDC solve the problem?

> * User programs writing UTF-8 strings to the console suffer from the same issue. This *could* be worked around by setting the console codepage in druntime's _d_run_main and resetting it to the original one before termination.

--

https://issues.dlang.org/show_bug.cgi?id=1448

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3

--

https://issues.dlang.org/show_bug.cgi?id=1448

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://issues.dlang.org/sh
                   |                            |ow_bug.cgi?id=24001

--