C++ Logo

SG16

Advanced search

Subject: Reminder: SG16 telecon tomorrow, Wednesday, 2020-11-11
From: Tom Honermann (tom_at_[hidden])
Date: 2020-11-10 10:30:26


This is your friendly reminder that an SG16 telecon will be held
tomorrow, Wednesday November 11th, at 19:30 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>).

*Please note that daylight savings time ended for the **Pacific,
Mountain, Central, and Eastern timezones since our last telecon; this
telecon will start one hour earlier than our last meeting for people in
those timezones.*

This meeting will be conducted via Zoom.  To attend, visit
https://iso.zoom.us/j/8414530059 at the start of the meeting.  Please
contact me privately if necessary for the meeting password.

The agenda is:

  * P1885R3: Naming Text Encodings to Demystify Them
    <https://wg21.link/p1885r3>
      o Review updates since the review of D1885R2 in Prague
        <https://wiki.edg.com/bin/view/Wg21prague/SG16D1885R2>.
  * 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.

LEWG(I) mailing list review for P1885R3 is currently taking place on the
lib-ext mailing list; please contribute non-SG16 concerns to that
discussion.

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.

Tom.



SG16 list run by sg16-owner@lists.isocpp.org