Date: Wed, 1 Sep 2021 17:28:18 +0200
Hi all,
SG16 will hold a meeting on Wednesday, September 8th at 19:30 UTC.
- D2348R1: Whitespaces Wording Revamp (Corentin Jabot)
https://isocpp.org/files/papers/D2348R1.pdf
In our last meeting [1], we asked the author to rebase the wording on
P2314 "Character sets and encodings", and to fix an unintentional
design change to vertical tab and form feed handling
This new draft incorporates this feedback. If possible, we will poll
to forward the revised proposal to EWG as the recommended resolution
of CWG 1655 and CWG 2002, and with a recommendation to be immediately
forwarded to CWG as having no evolutionary impact [2].
- P2093R8: Formatted output (Victor Zverovich)
https://wg21.link/p2093r8
This paper has been revised since our last discussion on June 23rd,
2021 [3]. At that meeting, we got stuck on whether the use of UTF-8 as
the literal encoding is sufficient for <print> facilities to establish
encoding expectations, with a consensus so weak that we agreed that it
was not possible to forward the paper without a higher level of
confidence.
Does the additional implementation experience described in the latest
revision increase consensus? Is SG16's strong agreement on P2419R0
"Clarify handling of encodings in localized formatting of chrono
types" a helpful indicator of how to address this paper [1]?
- P2361R2: Unevaluated strings (Corentin Jabot, Aaron Ballman)
https://wg21.link/p2361r2
In the unlikely event that we have some time left over, we will
discuss this proposal to improve the specification of strings only at
compile time.
Best regards,
Peter
[1] https://github.com/sg16-unicode/sg16-meetings#august-25th-2021
[2] https://wg21.link/cwg1655 / https://wg21.link/cwg2002
[3] https://github.com/sg16-unicode/sg16-meetings#june-23rd-2021
SG16 will hold a meeting on Wednesday, September 8th at 19:30 UTC.
- D2348R1: Whitespaces Wording Revamp (Corentin Jabot)
https://isocpp.org/files/papers/D2348R1.pdf
In our last meeting [1], we asked the author to rebase the wording on
P2314 "Character sets and encodings", and to fix an unintentional
design change to vertical tab and form feed handling
This new draft incorporates this feedback. If possible, we will poll
to forward the revised proposal to EWG as the recommended resolution
of CWG 1655 and CWG 2002, and with a recommendation to be immediately
forwarded to CWG as having no evolutionary impact [2].
- P2093R8: Formatted output (Victor Zverovich)
https://wg21.link/p2093r8
This paper has been revised since our last discussion on June 23rd,
2021 [3]. At that meeting, we got stuck on whether the use of UTF-8 as
the literal encoding is sufficient for <print> facilities to establish
encoding expectations, with a consensus so weak that we agreed that it
was not possible to forward the paper without a higher level of
confidence.
Does the additional implementation experience described in the latest
revision increase consensus? Is SG16's strong agreement on P2419R0
"Clarify handling of encodings in localized formatting of chrono
types" a helpful indicator of how to address this paper [1]?
- P2361R2: Unevaluated strings (Corentin Jabot, Aaron Ballman)
https://wg21.link/p2361r2
In the unlikely event that we have some time left over, we will
discuss this proposal to improve the specification of strings only at
compile time.
Best regards,
Peter
[1] https://github.com/sg16-unicode/sg16-meetings#august-25th-2021
[2] https://wg21.link/cwg1655 / https://wg21.link/cwg2002
[3] https://github.com/sg16-unicode/sg16-meetings#june-23rd-2021
Received on 2021-09-01 10:28:45