Hi Corentin,

Thank you for these drafts. I’m reading through “Down with character” and I think it’s looking really sound.

There appears to be a typographical problem in the first paragraph of [lex.token] – please could you check it?

Thanks,

              Peter

From: SG16 <sg16-bounces_at_[hidden]> On Behalf Of Corentin Jabot via SG16
Sent: 24 January 2023 20:40
To: sg16_at_[hidden]
Cc: Corentin Jabot <corentinjabot_at_[hidden]>; Tom Honermann <tom_at_[hidden]>
Subject: Re: [SG16] Agenda for the 2023-01-25 SG16 telecon​

EXTERNAL MAIL
Down with character: applied Alisdair feedback, added wording for [cpp] and [basic] https://isocpp.org/files/papers/D2749R0.pdf<https://urldefense.com/v3/__https:/isocpp.org/files/papers/D2749R0.pdf__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-K9bWl_8o$>

Referencing the unicode standard: applied SG-16 suggestion and the wording suggestion made by Jens on mattermost. I would prefer a solution that does not preserve the term ucs2, i think, but it's in a deprecated annex so... good enough! https://isocpp.org/files/papers/D2736R1.pdf<https://urldefense.com/v3/__https:/isocpp.org/files/papers/D2736R1.pdf__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-K_HXlkSA$>


I'll keep tweaking tomorrow but it should allow us to make progress during tomorrow's meeting.


On Tue, Jan 24, 2023 at 8:55 PM Tom Honermann via SG16 <sg16_at_[hidden]<mailto:sg16_at_[hidden]>> wrote:

This is your friendly reminder that this meeting is taking place tomorrow.
Tom.
On 1/23/23 12:45 PM, Tom Honermann via SG16 wrote:

SG16 will hold a telecon on Wednesday, January 25th, at 19:30 UTC (timezone conversion<https://urldefense.com/v3/__https:/www.timeanddate.com/worldclock/converter.html?iso=20230125T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KGv1Lq-s$>).

The agenda follows.

  * Planning for NOT Issaquah.
  * P2736R0<https://urldefense.com/v3/__https:/wg21.link/p2736r0__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KRs9FzKQ$>: Referencing the Unicode Standard.
  * D2749R0<https://urldefense.com/v3/__https:/isocpp.org/files/papers/D2749R0.pdf__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-K9bWl_8o$>: Down with ”character”

We agreed to hold a SG16 meeting in Issaquah during the 2023-01-11 SG16 telecon<https://urldefense.com/v3/__https:/github.com/sg16-unicode/sg16-meetings*january-11th-2023__;Iw!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-K3yfPMkI$>. Unfortunately, that isn't going to happen due to a lack of conference rooms available during regular business hours and previous discussions regarding meeting before or after regular business hours did not have consensus. That leaves us with just this upcoming telecon currently scheduled to dispense with our remaining NB comments. I'm hopeful that we'll be able to poll forwarding P2736 at this meeting, but I'm skeptical that we'll get to a point where we are comfortable polling P2749. However, I would be happy to schedule an additional telecon for 2023-02-01 if we agree there is a reasonable chance that we'll be able to establish a position on that paper by then.

We continued discussion of P2736R0 (Referencing the Unicode Standard) during the 2023-01-11 SG16 telecon<https://urldefense.com/v3/__https:/github.com/sg16-unicode/sg16-meetings*january-11th-2023__;Iw!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-K3yfPMkI$> and identified a few issues to be addressed. Corentin has requested some assistance, both on the SG16 mailing list<https://urldefense.com/v3/__https:/lists.isocpp.org/sg16/2023/01/3664.php__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KrU63gIQ$> and in the SG16 Mattermost channel<https://urldefense.com/v3/__https:/chat.isocpp.org/general/channels/sg16-unicode__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KOYUTTEg$>. If you can help out, please do so! (Sorry, Corentin, I've been playing too much catchup lately). Note that Fraser also expressed a view regarding the __STDC_ISO_10646__ macro<https://urldefense.com/v3/__https:/lists.isocpp.org/sg16/2023/01/3663.php__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KPQthupA$>; it would be helpful to have other comments either in agreement or in opposition to that view.

D2749R0 (Down with ”character”) was on the agenda for our last telecon, but we ran out of time. We last discussed the related NB comment during the 2022-12-14 SG16 telecon<https://urldefense.com/v3/__https:/github.com/sg16-unicode/sg16-meetings*december-14th-2022__;Iw!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KDeFMe-I$>. This paper is relatively long due to its wording impact. Please take the time to read the motivation and at least scan through the wording changes. I encourage everyone to reacquaint themselves with the terminology used in UTR #17<https://urldefense.com/v3/__https:/unicode.org/reports/tr17/__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-KaANWDk8$> beforehand as well.
Tom.
--
SG16 mailing list
SG16_at_[hidden]<mailto:SG16_at_lists.isocpp.org>
https://lists.isocpp.org/mailman/listinfo.cgi/sg16<https://urldefense.com/v3/__https:/lists.isocpp.org/mailman/listinfo.cgi/sg16__;!!EHscmS1ygiU1lA!EPHwwFdX7NN_CLOIyzJaoY1dz9evPv7PQgJFx8aVf9OOlPFDvtIg5nqRtLtfV67B68ijjf-Kaq_rlew$>