This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.
Section: 28.5.2.2 [format.string.std] Status: Resolved Submitter: Hubert Tong Opened: 2020-02-29 Last modified: 2023-03-23
Priority: 3
View other active issues in [format.string.std].
View all other issues in [format.string.std].
View all issues with Resolved status.
Discussion:
In 28.5.2.2 [format.string.std], the meaning of "Unicode encoding" in the text added by P1868R2 (the "Unicorn width" paper) is unclear.
One interpretation of what is meant by "Unicode encoding" is "UCS encoding scheme" (as defined by ISO/IEC 10646). Another interpretation is an encoding scheme capable of encoding all UCS code points that have been assigned to characters. Yet another interpretation is an encoding scheme capable of encoding all UCS scalar values. SG16 reflector discussion (with the LWG reflector on CC) indicates that the third option above is the closest to the intent of the study group. The situation of the current wording, which readers can easily read as indicating the first option above, is undesirable.[2020-07-17; Priority set to 3 in telecon]
[2023-03-22 Resolved by the adoption of P2736R2 in Issaquah. Status changed: New → Resolved.]
Proposed resolution: