News for hackers. Stuff that matters.
Re:Windows 10 Console Host Enhancements by yuhong on Tuesday February 09, 2016 @02:40PM (#11068128)
Unlikely to happen, they went UTF-16 long ago.
Re:Windows 10 Console Host Enhancements by mark-r on Tuesday February 09, 2016 @05:05PM (#11069172)
I realize the interface to the Windows API is UTF-16, but the program interface to the console (stdout) is not - it's based on 8 bit characters, generally code page 437. Converting from UTF-8 to UTF-16 is trivial, as long as you get the full byte sequence that makes up a character.
Re:Windows 10 Console Host Enhancements by nikbackm on Wednesday February 10, 2016 @12:41AM (#11070962)
Does this this [1] work for the console?

[1] http://stackoverflow.com/questions/388490/unicode-characters...

Re:Windows 10 Console Host Enhancements by mark-r on Thursday February 11, 2016 @09:40AM (#11080353)
Have you read all the comments below the answer about how broken 65001 is?
Re:Windows 10 Console Host Enhancements by yuhong on Tuesday February 09, 2016 @06:38PM (#11069718)
There is ReadConsoleW/WriteConsoleW which have full UTF-16 support already.
Re:Windows 10 Console Host Enhancements by rspeer on Wednesday February 10, 2016 @12:04AM (#11070855)
Having to use a completely different abstraction instead of stdout is enough to just make people give up on outputting Unicode on Windows.