C++ Windows Unicode Console Output

unicode gone wrong

Update 2019-11-11

Not much has changed in the WINLAND console world. Still, the following code produces no output.

Unless you do spend time digging through this long post or other similar posts elsewhere. Generally doing things, Linux/Mac console developers users, have never heard of.

For example. I have never mentioned ‘u8’ (UTF-8) string literals. That is an iso C++ native way to use UTF-8 encoding of char string literals.

To actually make the above work, you need to do two more “things” as ever: make sure chcp 65001 is executed beforehand, on the same console (in WIN10 it *should* be the default), and of course if not already switch to the font that can show these glyphs.

Yes, to code in a truly portable fashion, I suggest using char8_t as bove.  Alternatively, one can always try a bit more relaxed style:

But be prepared to be surprised by your compiler, at least for a while until it exhibits a full C++20 conformance.

Windows Terminal 1.0

Yes, there is much more I can write about this whole issue, but I decided not to.  Yet. Let’s allow the WIN team leadership to release a stable and bug-free new console subsystem first. Apparently that is “spring 2020”.

Continue reading “C++ Windows Unicode Console Output”

Speculation on the future of .NET Framework

April 2014

Why would anybody produce any Speculation on the future of .NET Framework? Perhaps you have invested a lot of time and money in .NET? As a such you are keenly interested just where is .NET heading these days, mid 2014? Wherever it’s daddy is taking it one might say and proceed elsewhere. But, I have produced yet another set of speculations, if anybody is interested ? Continue reading “Speculation on the future of .NET Framework”