5
AllocConsole();
consoleHandle = GetStdHandle(STD_OUTPUT_HANDLE);
WriteConsoleW(consoleHandle, L"qweąęėšų\n", 9, NULL, NULL);
_wfreopen(L"CONOUT$", L"w", stdout);
wprintf(L"qweąęėšų\n");

Output is:

qweąęėšų
qwe

Why does wprintf stop after printing qwe? \0 byte encountered in ą should terminate wide-char string, AFAIK

user206334
  • 850
  • 1
  • 8
  • 18

2 Answers2

2

At first I accepted Hans Passant answer, but the root cause for wprintf not printing to UTF-8 streams is that wprintf behaves as though it uses the function wcrtomb, which encodes a wide character (wchar_t) into a multibyte sequence, depending on the current locale - link. Windows does not have an UTF-8 capable locale (a locale which would support an UTF-8 codepage (65001)).

Quote from MSDN:

The set of available locale names, languages, country/region codes, and code pages includes all those supported by the Windows NLS API except code pages that require more than two bytes per character, such as UTF-7 and UTF-8.

Community
  • 1
  • 1
user206334
  • 850
  • 1
  • 8
  • 18
  • 3
    note: you could use `_setmode(_fileno(stdout), _O_U16TEXT);` (or `_O_U8TEXT`), to print Unicode using `wprintf()` -- though it breaks `printf`. – jfs Nov 29 '15 at 06:33
1

The stdout stream can be redirected and therefore always operates in 8-bit mode. The Unicode string you pass to wprintf() gets converted from utf-16 to the 8-bit code page that's selected for the console. By default that's the olden 437 OEM code page. That's where the buck stops, that code page doesn't support the character.

You'll need to switch to another 8-bit code page, one that does support that character. A good choice is 65001, the code page for utf-8. Fix:

 SetConsoleOutputCP(CP_UTF8);

Or use SetConsoleCP() if you want stdin to use utf-8 as well.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
  • 2
    So it seems Microsoft C runtime is not compliant in this case, cause stdout should use mode-orientation which was used first. – user206334 Apr 05 '13 at 08:53