Hello,

Here is a revision of P1885 that expands the revision and modify the
wording to reflect the
wording https://isocpp.org/files/papers/D1885R8.pdf

The strategy I have chosen is to first describe the encoding of each static
function as being an implementation-defined encoding scheme, and then
substitute that by UTF-16 if needed.
the literal functions are specified to return the encoding of the object
representation, as discussed.

In addition, these papers will be in the mailing list:

Relax requirements on wchar_t to match existing practices
https://isocpp.org/files/papers/P2460R0.pdf

Unevaluated Strings
https://isocpp.org/files/papers/P2361R3.pdf

Conversion to literal encoding should not lead to loss of meaning
https://isocpp.org/files/papers/P1854R1.pdf

Whitespaces Wording Revamp
https://isocpp.org/files/papers/P2348R2.pdf


I am exhausted, so the likelihood these are full of typos is non-negligible.
I am not sure I will have time to address further feedback or concerns this
week, but please send them my way anyway, things will get fixed, eventually.

Have a great week,

Corentin