Subject: Re: Agenda for the 2021-07-14 SG16 telecon
From: Hubert Tong (hubert.reinterpretcast_at_[hidden])
Date: 2021-07-11 11:23:19
The assumed prerequisite paper is P2314 and not P2223? I see "translation
character set" present in "unchanged context" in the wording.
For the requirement to provide a mechanism, this might be an improvement:
An implementation shall provide a mechanism to specify the result of the
determination that is independent of the content of the source file.
For the note, I think this is an improvement that would reduce the time
spent in CWG:
A command line option that specifies the encoding scheme to use as the
result of the determination is such a mechanism.
In the third paragraph of phase 1:
[ ... ], then the physical source file shall be a well-formed UTF-8
Each UCS scalar value encoded in the UTF-8 sequence is mapped to the
corresponding element of the translation character set.
I'm not sure what to make of the situation around end-of-line indicators
yet. P2348, "Whitespaces Wording Revamp", is also floating in the mix.
On Sun, Jul 11, 2021 at 4:27 AM Corentin Jabot via SG16 <
> We added a note to explicitly say that we expect implementation to provide
> a command line option.
> I am sure that core will want to tweak that note, but hopefully it leaves
> little room for interpretation
> On Sun, Jul 11, 2021 at 12:12 AM Tom Honermann via SG16 <
> sg16_at_[hidden]> wrote:
>> SG16 will hold a telecon on Wednesday, July 14th at 19:30 UTC (timezone
>> The agenda is:
>> - P2295R4: Support for UTF-8 as a portable source file encoding
>> - Review updated wording produced through collaboration between
>> Corentin, Jens, Hubert, and Peter.
>> - https://lists.isocpp.org/sg16/2021/04/2353.php
>> - https://lists.isocpp.org/sg16/2021/06/2429.php
>> - P2362R0: Make obfuscating wide character literals ill-formed
>> - LWG 3565: Handling of encodings in localized formatting of chrono
>> types is underspecified <https://cplusplus.github.io/LWG/issue3565>
>> - Discuss and poll the proposed resolution.
>> The agenda is a result of discussion between Peter and I; we feel that
>> further information is needed to improve consensus for P2093R6
>> <https://wg21.link/p2093r6> and no such information has appeared since
>> the last telecon. We'll therefore take a break from that paper to allow
>> for progress on other papers.
>> We've had several discussions regarding the wording for P2295. Please
>> review the latest wording in P2295R4 <https://wg21.link/p2295r4> and, if
>> *objections* (not just desired tweajs) remain, reply to this email to
>> state them ahead of the meeting. My intention is to poll forwarding this
>> paper with the expectation that core will further tweak the wording pending
>> EWG acceptance. The SG16 obligation is to ensure that the intent of the
>> paper is clear and that the proposed wording reasonably reflects it; I
>> don't want to hold this paper up further unless it is felt that the wording
>> misrepresents the intent.
>> Based on our prior discussions of P2093R6 <https://wg21.link/p2093r6>,
>> I'm anticipating considerable discussion will be needed for LWG 3565
>> <https://cplusplus.github.io/LWG/issue3565>. It has been moved to the
>> end of the agenda in hopes that we'll be able to dispense with the other
>> papers first and then spend the remaining time on it.
>> SG16 mailing list
> SG16 mailing list
SG16 list run by firstname.lastname@example.org