The summary for the SG16 meeting held December 9th, 2020 is now
available. For those that attended, please review and suggest corrections:

  * https://github.com/sg16-unicode/sg16-meetings#december-9th-2020

No decisions were made at this meeting.

The next meeting is scheduled for Wednesday, January 13th, from
19:30-21:00 UTC (timezone conversion
<https://www.timeanddate.com/worldclock/converter.html?iso=20210113T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>).
The draft agenda is:

  * P2246R0: Character encoding of diagnostic text
    <https://wg21.link/p2246r0>
      o And companion paper: WG14 N2563: Character encoding of
        diagnostic text
        <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2563.pdf>
  * SG16, SG22, and WG14 coordination.
      o Priority and owners for SG16's open WG14 issues
        <https://github.com/sg16-unicode/sg16/issues?q=is%3Aissue+is%3Aopen+label%3Awg14>
  * WG14 N2620: Restartable and Non-Restartable Functions for Efficient
    Character Conversions | r4
    <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2620.htm>

We'll try to wrap up discussion and polling of P2246R0
<https://wg21.link/p2246r0> in the first 30 minutes. Please read both
P2246R0 <https://wg21.link/p2246r0> and WG14 N2563
<http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2563.pdf> prior to the
telecon.

Discussion of coordination with SG22 and WG14 is expected to be short;
perhaps 15 minutes. Please review the SG16 open issues tagged as WG14
<https://github.com/sg16-unicode/sg16/issues?q=is%3Aissue+is%3Aopen+label%3Awg14>
ahead of time and consider whether you can offer assistance moving them
along. In particular, I'd like to find owners for the WG14 equivalents
of P1949 (C++ Identifier Syntax using Unicode Standard Annex 31) and
P1041 (Make char16_t/char32_t string literals be UTF-16/32).

The remainder of the telecon will focus on socializing and reviewing
JeanHeyd's work on WG14 N2620
<http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2620.htm>. This is a
fairly long paper, so please set aside some time to read it. We won't
delve into the proposed wording, but for the standardeze lovers out
there, reading just the wording will give you a good sense of what the
paper is about (but please try and read sections 2-4 as well).

Polls to forward P2246R0 to EWG are expected. Direction polls for WG14
N2620 may be taken.

For any new attendees: The meetings are video conferences conducted via
Zoom. If you are planning to attend, please test your system by
visiting https://zoom.us/test before the scheduled meeting time.

Tom.