On Wed, Jan 14, 2026 at 12:58 PM Hubert Tong <
hubert.reinterpretcast_at_[hidden]> wrote:

> I believe that the claim in the first paper that "GCC assumes '\\' == '¥'
> to be true" should be corrected to reflect that it depends on the iconv
> implementation that GCC is linked against.
>

Also:
There is a typo in 3.8.2: "is_ascii_* rather than is_ascii_*".
The definition of ASCII-compatible is not extremely clear as to whether
values for which ascii_is_any is true can contextually be taken as anything
other than the ASCII character with that value.

-- HT


>
> On Tue, Jan 13, 2026 at 12:11 PM Tom Honermann via SG16 <
> sg16_at_[hidden]> wrote:
>
>> SG16 will hold a meeting *tomorrow*, Wednesday, January 14th, at 19:30
>> UTC (timezone conversion
>> <https://www.timeanddate.com/worldclock/converter.html?iso=20260114T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>
>> ).
>>
>> The agenda is:
>>
>> - P3688R5: ASCII character utilities <https://wg21.link/p3688r5>.
>> - P3876R0: Extending <charconv> support to more character types
>> <https://wg21.link/p3876r0>.
>>
>> Happy new year!
>>
>> If you concentrate hard, you might recall, way back before the
>> (non-)release of the Epstein files, the friendly visits from a jolly man in
>> a red suit, the celebrations of another successful circumnavigation of the
>> sun, the US capture of the leader of Venezuela, the reignited talk of the
>> US invading Greenland, the on-going ICE related tragedies in the US, and
>> the attempts to politicize the Federal Reserve, a full month ago, we had
>> been discussing the P3688 proposal to add a suite of ASCII related
>> utilities to the standard. Jan published *P3688R5* shortly after our last
>> meeting
>> <https://wiki.edg.com/bin/view/Wg21telecons2025/SG16Teleconference2025-12-10>
>> and, I think, has addressed all feedback that was provided. We'll review
>> the new revision, ensure previously raised concerns have been addressed,
>> and hopefully poll forwarding it to LEWG.
>>
>> *P3876R0*, for which Jan is also the primary author, seeks to
>> standardize additional overloads of std::to_chars() and std::from_chars() (and
>> their result types) for additional character types (char8_t, char16_t,
>> char32_t, and wchar_t). As usual, we'll consider encoding related issues
>> (e.g., handling for malformed code unit sequences) and impact on existing
>> implementations. Fortunately, since these utilities are locale independent,
>> we'll (hopefully) not have to wrangle with locale related concerns. This
>> proposal is conceptually simple, but the paper is relatively long (in a
>> good way), so I don't expect that we'll conclude discussion in this meeting.
>>
>> Tom.
>>
>>
>> --
>> SG16 mailing list
>> SG16_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>> Link to this post: http://lists.isocpp.org/sg16/2026/01/4659.php
>>
>