It was previously agreed that P2348 is editorial in nature and
thus doesn't need to go in before the C++23 CD.
"Editorial" also could also be understood to imply that it's not
in scope for SG16, which feeds into LEWG or EWG, since the paper
is definitely out of scope for them.

P2348 was finally reviewed by CWG on 2022-09-09.
and feedback given to the author.

https://wiki.edg.com/bin/view/Wg21telecons2022/Teleconference2022-09-09

CWG is awaiting an updated paper; in the interim, it is my understanding
that a US NB comment will ask for a minimal fix to [lex.phases]p1
so that e.g. CR/LF becomes a valid line terminator for UTF-8 files.

Jens


On 26/10/2022 17.56, Tom Honermann via SG16 wrote:
> Please review the following. If you agree with the proposed change and have no further information to add, then there is no need to respond. If you disagree with the proposed change, have corrections or new information to offer, or have comments on the candidate polls, then *please reply by Monday, October 31st*.
>
>
> GB 5.2 [lex.phases] <http://eel.is/c++draft/lex.phases> Clarification of wording on new-line and whitespace
>
> GitHub nbballot issue #432 <https://github.com/cplusplus/nbballot/issues/432>.
>
>
> Comment:
>
> Clarification of wording on new-line and whitespace.
>
> The specification of new-line and whitespace should be updated following changes to the C++ working paper, such as P2314 adopted in Oct 2021.
>
>
> Proposed change:
>
> We propose adopting a revision of P2348 ("Whitespaces Wording Revamp").
>
>
> SG16 chair notes:
>
> Did SG16 review P2348? I can't recall.
>
> Link to CWG review of P2348.
>
>
> Candidate polls:
>
> * [GB-XX]: SG16 recommends accepting the comment in the direction of the proposed change.
> * [GB-XX]: SG16 recommends rejecting the comment as not a defect.
>
> Tom.
>
>