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”

Dear Chairman: Please keep your eyes on the road

nokia-2012-sep
Somehow the Roadmap was not followed. Best navigation App did not help.

As a business leader, do keep on engaging with Enterprise Architects regularly.

You are the captain, Architect is the navigator. You say where to go, Architect says how to get there.

At least twice per year check with your Enterprise Architects, are you actually where the markets wanted you to be.

Vision and Road-map are long term navigation maps, best owned by good and forward-thinking Enterprise Architects. Don’t let something “amazing” surprise you, as it happened to NOKIA

c++ strong types holy grail

Exact types of Fasteners
Exact types of Fasteners type. It is impossible to confuse them with each other.

This is the second installment of an aptly named “c++ strong duck” post. (a title is an act of deliberate sarcasm vs ‘duck typing’ ). If you haven’t before please make a slight detour to that post, for a brief introduction on strong types, as an antidote to “type punning“. Continue reading “c++ strong types holy grail”