On Mon, 9 Nov 2020 at 16:20, Tom Honermann via SG16 <sg16_at_[hidden]>
wrote:

> 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
> <https://www.timeanddate.com/worldclock/converter.html?iso=20201111T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>).
> The draft agenda is:
>
> - P1885R3: Naming Text Encodings to Demystify Them
> <https://wg21.link/p1885r3>
> - Review updates since the review of D1885R2 in Prague
> <https://wiki.edg.com/bin/view/Wg21prague/SG16D1885R2>.
>
>
FYI no design changes were made, I mostly added a few clarifications as to
why IANA and not something else, as advised at the time.
There will be further wording tweaks following some good feedback Tom sent
me, but at this point I'd really like LEWG to look at this paper.
Which they haven't really done yet, the ongoing LEWGI thread on the
reflector isn't exactly gathering crowds!


>
> - P2093R2: Formatted output <https://wg21.link/p2093r2>
>
> 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.
>
> No decisions are anticipated at this meeting, but direction polls 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.
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>