4 ms·

Unlikely to happen, they went UTF-16 long ago.

• mark-r 11y ago
  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.
  • yuhong 11y ago
    There is ReadConsoleW/WriteConsoleW which have full UTF-16 support already.
    • rspeer 11y ago
      Having to use a completely different abstraction instead of stdout is enough to just make people give up on outputting Unicode on Windows.
  • nikbackm 11y ago
    Does this this [1] work for the console? [1] http://stackoverflow.com/questions/388490/unicode-characters-in-windows-command-line-how/388500#388500 http://stackoverflow.com/questions/388490/unicode-characters...
    • mark-r 11y ago
      Have you read all the comments below the answer about how broken 65001 is?