On 20/02/2024 04.56, Tom Honermann via SG16 wrote:
> 1. Accept the changes to XID_continue, or
> 2. Reject the changes to XID_continue by adjusting the profile specified in [uaxid.def.general] <http://eel.is/c++draft/uaxid.def.general>, possibly by including the Default-Ignorable Exclusion Profile <https://www.unicode.org/reports/tr31/tr31-39.html#Default_Ignorable_Exclusion_Profile>, though that would exclude many code points <https://util.unicode.org/UnicodeJsps/list-unicodeset.jsp?a=%5B%3AXID_continue%3A%5D%26%5B%3ADefault_Ignorable_Code_Point%3A%5D&g=&i=> beyond ZWNJ and ZWJ.
>
> Once consensus for a direction is established, a volunteer will be needed to draft wording changes for [uaxid] <http://eel.is/c++draft/uaxid>.

I would like to point out that [uaxid] is informative
(not normative). While we should keep it in sync,
[lex.name] is where the normative statement about
XID_Continue is.

> LWG 4043 was recently filed by Jonathan Wakely. It reports a straightforward concern; that the set of encodings recognized by std::text_encoding does not include "ASCII" despite that name being unambiguous and recognized by common encoding libraries. The proposed resolution is to add "ASCII" to the set of aliases for that IANA specified "US-ASCII" encoding despite the fact that the IANA character set registry <https://www.iana.org/assignments/character-sets/character-sets.xhtml> does not do so.

We've already fixed a typo and removed a duplicate, I think,
so this sounds good to me.

Jens