Path: csiph.com!aioe.org!Puiiztk9lHEEQC0y3uUjRA.user.46.165.242.75.POSTED!not-for-mail
From: Manfred <noname@add.invalid>
Newsgroups: comp.lang.c++
Subject: Re: Character encoding conversion in wide string literals
Date: Tue, 7 Dec 2021 19:07:18 +0100
Organization: Aioe.org NNTP Server
Message-ID: <soo7sn$b5e$1@gioia.aioe.org>
References: <sonh15$g9j$1@gioia.aioe.org> <soo2mk$ljk$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Info: gioia.aioe.org; logging-data="11438"; posting-host="Puiiztk9lHEEQC0y3uUjRA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
X-Notice: Filtered by postfilter v. 0.9.2
Content-Language: en-US
Xref: csiph.com comp.lang.c++:82572

On 12/7/2021 5:38 PM, James Kuyper wrote:
> * I remember hearing rumors that modern versions of Windows do provide
> some support for UTF-8, but that support is neither complete, nor the
> default. You have know what you need to do to enable such support - I don't.

One relevant addition that is relatively recent is support to/from UTF-8 
in the APIs WideCharToMultiByte and MultiByteToWideChar.
These allow to handle UTF-8 programmatically in code.
Windows itself still uses UTF-16 internally.
I don't know how filenames are stored on disk.