Windows vs UTF-8 (issue 15845)

[ag0aep6g via Digitalmars-d]

On 04.04.2016 00:31, Martin Krejcirik wrote:
> Sorry, I missed that in your post. Anyway, after years of trying, I've
> resorted to always converting to/from OEMCP.
>
> You can use fromMBSz, toMBSz, GetConsoleCP, GetConsoleOutputCP functions
> for that.

I'm not really asking for myself, but more for fixing issue 15845. If 
reading UTF-8 is broken in Windows and there's no workaround, then issue 
15845 can't be fixed, and we should stop telling people to use `chcp 
65001` (and don't forget to change the font).