On 24/08/2020 06.12, Tom Honermann via Core wrote:
> Perhaps it is time to re-title this paper to "Rewrite [lex.ccon] and [lex.string]" :)
>
> An update of D2029R3 is available at https://rawgit.com/sg16-unicode/sg16/master/papers/d2029r3.html. This addresses the feedback provided at the July 20th, 2020, core issues processing telecon. The relevant changes include:
>
> * Changed the introductory and proposed resolution overview to remove incorrect uses of "narrowing integer conversion" in prose intended to describe something more like an "integral conversion".
> * [lex.ccon]pY: Added footnotes explaining that, for nonencodable character literals and multicharacter literals, the associated character encoding may be used solely to determine encodability and not to actually encode values.

Footnotes Y1 and Y3: Suggestion:

Y1) The associated character encoding for ordinary character literals
determines encodability, but does not determine the value of
non-encodable ordinary character literals or ordinary multicharacter
literals.

Jens