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

• https://github.com/sg16-unicode/sg16-meetings#october-28th-2020

No decisions were made at this meeting, but consensus was reached for the direction of transitioning the standard to a source translation model specified in terms of Unicode scalar values instead of UCNs.

The next meeting is scheduled for Wednesday, November 11th, from 19:30-21:00 UTC (timezone conversion).  The draft agenda is:

• P1885R3: Naming Text Encodings to Demystify Them
• Review updates since the review of D1885R2 in Prague.
• P2093R2: Formatted output
  

For P1885R3, please recall that we previously forwarded this paper in Prague knowing that we would review a future update.  This is that review.  Corentin invested the considerable time necessary to identify a number of encodings that are not accounted for in the IANA DB by cross referencing encodings supported by Windows, GNU iconv, and the WHATWG encoding standard.  We'll review that list and give the proposed interface a quick once over to refresh ourselves on it and look for any last tweaks to be suggested.  The intent is *not* to re-litigate the design.

For P2093R3, please chuckle at the quote, and then take time to contemplate how the proposed feature is expected to interoperate with the encoding of string literals and the (locale sensitive) run-time execution encoding.  In particular, note that the proposal uses the string literal encoding as a proxy to assume a run-time execution encoding.