The NB comments for the CD ballot have been officially released. Now
that we have official identifiers for the comments, I am going to use
those in the published summary for this meeting. I'm also going to
revise the summary for the 2022-10-19 telecon
<https://github.com/sg16-unicode/sg16-meetings#october-19th-2022> to use
them. If this is a cause for concern for anyone, please let me know.

I also realized that I neglected to explicitly declare the result of the
final poll we took for the 2022-11-02 telecon. The published summary
will indicate a lack of consensus for that poll. The poll was:

  * Poll: [FR-10][FR-21]: SG16 recommends resolving these comments by
    restricting all references to the Unicode Standard to the version
    that corresponds to the referenced version of ISO/IEC 10646.
      o Attendees: 9 (1 abstention)
      o
        SF
         F
         N
         A
         SA
        2
         3
         0
         3
         0

      o No consensus

Tom.

On 11/1/22 2:50 PM, Tom Honermann via SG16 wrote:
>
> This is your friendly reminder that this meeting is taking place tomorrow.
>
> If you have not yet reviewed the emails sent for each of the NB
> comments listed below, please try to do so before the meeting.
>
> I'd like to focus on the issues that I expect to have good consensus
> first with the goal of quickly dispensing with as many NB comments as
> we can before Kona. Based on the responses received so far, prior
> discussions, and my own expectations, I include these in that list:
>
> * [FR-05]: FR 22.14.6.4 [format.string.escaped] aggressive escaping
> <https://github.com/cplusplus/nbballot/issues/408>
> * [GB-03]: GB 5.2 [lex.phases] Clarification of wording on new-line
> and whitespace <https://github.com/cplusplus/nbballot/issues/432>
>
> The following are ones that I expect to require more discussion and
> where finding consensus may be more challenging. I'd like to tackle
> them in this order:
>
> * [FR-09]: FR Annex E [uaxid] Shorten contents and integrate with
> [lex.name] <https://github.com/cplusplus/nbballot/issues/411>
> * Unicode vs ISO/IEC 10646 (to be discussed together):
> o [FR-10]: FR [Bibliography] Unify references to Unicode
> <https://github.com/cplusplus/nbballot/issues/412>
> o [FR-21]: FR 5.3p5.2 [lex.charset] Codepoint names in
> identifiers <https://github.com/cplusplus/nbballot/issues/423>
> * [FR-06]: FR 22.14.2.2 [format.string.std] codepoints with width 2
> <https://github.com/cplusplus/nbballot/issues/409>
> * [FR-20]: FR 5.3 [lex.charset] Replace "translation character set"
> by "Unicode" <https://github.com/cplusplus/nbballot/issues/422>
>
> We'll get through as many as we can tomorrow and then discuss whether
> we want to attempt to meet again before Kona or whether to plan to
> prepare responses for the remainder for Issaquah in February.
>
> Tom.
>
> On 10/26/22 11:54 AM, Tom Honermann via SG16 wrote:
>>
>> SG16 will hold a telecon on Wednesday, November 2nd, at 19:30 UTC
>> (timezone conversion
>> <https://www.timeanddate.com/worldclock/converter.html?iso=20221102T193000&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 2022-10-30, so this telecon will start one hour earlier than our
>> last telecon (North America time zones don't change until 2022-11-06).*
>>
>> The agenda is:
>>
>> * NB comment processing.
>>
>> Draft NB comments have been made available from the CA, DE, FR, and
>> GB NBs. The following are those that I determined would benefit from
>> SG16 review. If you are aware of others not on this list, please let
>> me know. Please note that official NB comment identifiers are not yet
>> available; the [NB-XX] monikers below correspond to the individual
>> draft documents, but won't necessarily match the final identifiers.
>> The descriptions used here match the titles used for the
>> corresponding issues in the GitHub nbballot repository
>> <https://github.com/cplusplus/nbballot/issues>.
>>
>> * [FR-05]: FR 22.14.6.4 [format.string.escaped] aggressive escaping
>> <https://github.com/cplusplus/nbballot/issues/408>
>> * [FR-06]: FR 22.14.2.2 [format.string.std] codepoints with width 2
>> <https://github.com/cplusplus/nbballot/issues/409>
>> * [FR-09]: FR Annex E [uaxid] Shorten contents and integrate with
>> [lex.name] <https://github.com/cplusplus/nbballot/issues/411>
>> * [FR-10]: FR [Bibliography] Unify references to Unicode
>> <https://github.com/cplusplus/nbballot/issues/412>
>> * [FR-20]: FR 5.3 [lex.charset] Replace "translation character set"
>> by "Unicode" <https://github.com/cplusplus/nbballot/issues/422>
>> * [FR-21]: FR 5.3p5.2 [lex.charset] Codepoint names in identifiers
>> <https://github.com/cplusplus/nbballot/issues/423>
>> * [GB-03]: GB 5.2 [lex.phases] Clarification of wording on new-line
>> and whitespace <https://github.com/cplusplus/nbballot/issues/432>
>>
>> [FR-05] is related to our discussion of [US-38] during last week's
>> telecon
>> <https://github.com/sg16-unicode/sg16-meetings#october-19th-2022>.
>>
>> [FR-10] and [FR-21] are strongly related, so we'll discuss those
>> together.
>>
>> I will start separate email threads for each of these to facilitate
>> mailing list discussion in advance of the telecon next week with the
>> goal of establishing consensus with minimal discussion during the
>> telecon.
>>
>> Tom.
>>
>>
>