Windows 11 activates Beta support for UTF-8 system-wide by default

Interesting. Was it actually UTF-8? Or was it UCS2? The thread in question is discussing UTF-8, as opposed to local codepages, but it's possible they're getting confused by the fact that it requires conversion to UTF-8 to pass the strings around. I'm guessing Windows is taking those UTF-8 strings and transparently converting them to UCS2 though, since Windows internals have stuck to UCS2 for so long.

A search I did says:

> The encoding used with wchar_t does not necessarily have to be UTF-16--it could also be UTF-32 for example.

Is this a non-issue for applications that have explicitly opted in to UTF-8 [1]?

[1] https://learn.microsoft.com/en-us/windows/apps/design/global...

(2021)