Moreover, ACP is mostly irrelevant in modern code and it's sufficient to
compile with /utf-8 on MSVC (and on most other systems UTF-8 is the default
for char).

HTH,
Victor

On Thu, Jul 2, 2026 at 6:12 PM Tony V E via SG16 <sg16_at_[hidden]>
wrote:

> Isn't there a setting (ie on the compiler or in the exe manifest, etc) now
> under Windows to mark your exe as UTF8 such that your exe sees UTF8 as the
> active code page, regardless of what the OS has as the active code page?
>
>
> Be seeing you,
> Tony
>
> On Thu., Jul. 2, 2026, 7:47 p.m. Herb Sutter via SG16, <
> sg16_at_[hidden]> wrote:
>
>> Hi C++ Unicode folks, literally asking for a friend (Christopher, on the
>> To: line so please Reply-All)…
>>
>>
>>
>> His project team wants to use UTF-8 in their code base and they hoped to
>> switch to u8string[_view] and char8_t throughout, but they encountered two
>> sets of limitations:
>>
>>
>>
>> - In the standard, those types don’t seem to work with std::format
>> and streams.
>>
>>
>>
>> - On Windows, platform APIs interpret narrow characters using the
>> active code page (e.g., std::cout emits mojibake,
>> filesystem::path{std::string} UTF-8 paths are mangled or throw).
>>
>>
>>
>> What’s the current best guidance for adopting UTF-8 in C++ code?
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Herb
>>
>>
>> --
>> SG16 mailing list
>> SG16_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>> Searchable archives: http://lists.isocpp.org/sg16/2026/07/index.php
>>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
> Link to this post: http://lists.isocpp.org/sg16/2026/07/4777.php
>