Funny but real: WTF-8 and OMGWTF-8

[dodexahedron]

That's not a typo.

Check this out.

It's a real thing and is worth a laugh. While it is a real and full specification to address problems between UTF-8 and UTF-16, it's still more of a complaint and proof of concept than anything else and not intended for actual use, Just something both amusing and interesting I stumbled on and wanted to share. 😊

https://simonsapin.github.io/wtf-8

And that then led to someone else extending and refining the spec in OMGWTF8, which is also a legitimate attempt to complain about and address a problem, but not intended for real use.

And y'all probably thought I had too much time on my hands to write stuff. 😅

[dodexahedron]

OMG

The Wikipedia article on UTF-8 mentions WTF-8 😂

[dodexahedron]

Hm. This Microsoft Learn doc sure is interesting: https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page

So is this wiki article:

https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows

From the MS Learn doc, these are particularly interesting bits:

With a minimum target version of Windows Version 1903, the process code page will always be UTF-8, so legacy code page detection and conversion can be avoided.

Until recently, Windows has emphasized "Unicode" -W variants over -A APIs. However, recent releases have used the ANSI code page and -A APIs as a means to introduce UTF-8 support to apps. If the ANSI code page is configured for UTF-8, then -A APIs typically operate in UTF-8. This model has the benefit of supporting existing code built with -A APIs without any code changes.

🤔🤔🤔🤔🤔🤔