The summary for the SG16 meeting held October 19th, 2022 is now
available. For those that attended, please review and suggest corrections.

  * https://github.com/sg16-unicode/sg16-meetings/#october-19th-2022

The following polls were taken:

  * Poll 1: SG16 suggests to consider US-02 as "not a defect", but to
    improve the presentation by editorially moving the definition of
    "multibyte character" to [multibyte.strings]
    <http://eel.is/c++draft/multibyte.strings>.
      o No objection to unanimous consent.
  * Poll 2.1: [US-38] SG16 agrees that the formatted code units in the
    escaped string are intended to be usable as a string literal that
    reproduces the input.
      o No objection to unanimous consent.
  * Poll 2.2: [US-38] SG16 agrees that the escaped string is intended to
    be readable for its textual content in any Unicode script.
      o No objection to unanimous consent.
  * Poll 2.3: [US-38] SG16 agrees that separators and non-printable
    characters ([format.string.escaped]p(2.2.1.2)
    <https://eel.is/c++draft/format.string.escaped>) shall be escaped in
    the escaped string.
      o No objection to unanimous consent.
  * Poll 2.4: [US-38] SG16 agrees that combining code points shall not
    be escaped unless there is no leading code point or the previous
    character was escaped.
      o No objection to unanimous consent.
  * Poll 3: [US-64] SG16 agrees with resolving the issue in the
    direction presented in the comment
      o No objection to unanimous consent.

These poll results will be recorded in the nbballot github repository
<https://github.com/cplusplus/nbballot> once it is populated with issues
for the C++23 NB comments.

Tom.