Yes, thanks! I will hereafter pronounce S-U-E-F as if it were a word, "suef".

Zach

On Mon, Aug 28, 2023 at 2:18 PM Tom Honermann via SG16
<sg16_at_[hidden]> wrote:
>
> That's great! Thank you for following up, Robin!
>
> Tom.
>
> On 8/28/23 9:36 AM, Robin Leroy via SG16 wrote:
>
> Dear SG 16,
>
> Last month at UTC #176, the Properties & Algorithms Group recommended, and Unicode Technical Committee decided, the following:
>
> [176-A59] Action Item for Asmus Freytag, EDC: Change definition D79 to look like a definition, and add bullet points noting the use of the term to refer to the three UTF and suggesting the term “standard Unicode encoding forms” for clarity. Update mentions of “the [three] Unicode encoding forms” throughout the core specification as appropriate, for Unicode Version 16.0. See L2/23-160 item 1.1.
>
> [176-C14] Consensus: UTC authorizes a proposed update of UTR #17 based on Section 1.1 of L2/23-160.
>
> [176-A60] Action Item for Ken Whistler, EDC: Prepare a proposed update of UTR #17, changing mentions of “the [three] Unicode encoding forms” to use the phrase “standard Unicode encoding forms” as appropriate. See L2/23-160 item 1.1.
>
> [176-A61] Action Item for Rick McGowan, UTC: Post a PRI for PU UTR #17 with a closing date of 2023-10-11.
>
> [176-A62] Action Item for Asmus Freytag, EDC: In the FAQ and Glossary, change mentions of “the [three] Unicode encoding forms” to use the phrase “standard Unicode encoding forms” as appropriate. See L2/23-160 item 1.1.
>
> You should thus be able to use the phrase “standard Unicode encoding forms” in C++26 (Unicode 16.0 will be published in September 2024).
>
> Best regards,
>
> Robin Leroy
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16