This meeting has started, but we're missing many of the normal crew.
Please note the DST change only impacted European participants. If you
planning to attend, we're looking forward to you joining ASAP!

Tom.

On 11/3/21 1:30 PM, Tom Honermann via SG16 wrote:
> Reminder that this meeting is taking place *today*. Sorry, I forgot to
> send a reminder yesterday!
>
> Tom.
>
> On 10/31/21 12:55 PM, Tom Honermann via SG16 wrote:
>>
>> SG16 will hold a telecon on Wednesday, November 3rd at 19:30 UTC
>> (timezone conversion
>> <https://www.timeanddate.com/worldclock/converter.html?iso=20211103T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cet>).
>>
>> *For participants in Europe, please note that daylight savings time
>> ends 2021-10-31, so this telecon will start one hour earlier than our
>> last telecon (North America time zones don't change until 2021-11-07).
>> *
>>
>> The agenda is:
>>
>> * D2071R1: Named universal character escapes
>> o Continue review pending a revision update.
>> * P1854R1: Conversion to literal encoding should not lead to loss
>> of meaning <https://wg21.link/p1854r1>
>> o New revision review.
>> * P2361R3: Unevaluated strings <https://wg21.link/p2361r3>
>> o New revision review; we last reviewed this proposal during
>> the 2021-09-22 telecon
>> <https://github.com/sg16-unicode/sg16-meetings#september-22nd-2021>.
>>
>> The most recent revision of D2071R1 is attached to the email thread
>> archived at https://lists.isocpp.org/sg16/2021/10/2767.php
>> <https://lists.isocpp.org/sg16/2021/10/2767.php>. Further review of
>> D2071R1 is pending minor updates to address feedback from the last
>> telecon as well as wording updates offered on the SG16 mailing list
>> <https://lists.isocpp.org/sg16/2021/10/2766.php>.
>>
>> We had continued discussion of P1885 <https://wg21.link/p1885> at the
>> last telecon and had concluded with the intent to conduct some polls
>> at this upcoming telecon. However, since we had already approved
>> forwarding of a draft revision of P1885R8 <https://wg21.link/p1885r8>
>> during our 2021-09-22 telecon
>> <https://github.com/sg16-unicode/sg16-meetings#september-22nd-2021>,
>> LEWG will be proceeding with electronic polling of it (actually, of
>> P1885R9 <https://wg21.link/p1885r9>; this revision includes a mandate
>> that CHAR_BIT is 8 for all of the encoding querying functions). As a
>> result, any further discussion of P1885 concerns is now tabled
>> pending submission of a new paper that proposes changes to the design
>> specified in P1885R9. SG16 should now view P1885R9 as the status quo
>> unless LEWG rejects it.
>>
>> We last reviewed P1854 in Belfast. Please review the minutes recorded
>> here <https://wiki.edg.com/bin/view/Wg21belfast/SG16P1854R0> as well
>> as recent email discussion archived here
>> <https://lists.isocpp.org/sg16/2021/10/2780.php>. Prior polls on this
>> proposal are located with the minutes for P1885 here
>> <https://wiki.edg.com/bin/view/Wg21belfast/SG16P1885R0>. We had
>> previously decided to block P1854 on P1855 (as noted in those polls).
>> Now that we have forwarded P1885, P1854 is cleared to proceed.
>>
>> We last reviewed P2361 during our 2021-09-22 telecon
>> <https://github.com/sg16-unicode/sg16-meetings#september-22nd-2021>.
>> Please review those notes as well as the new revision.
>>
>> Tom.
>>
>>
>
>