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.

FR [format.string.escaped] aggressive escaping

GitHub nbballot issue #408.


The intent of "escaped strings" is unclear and unsuited to many spoken languages As it stands, this features escapes

It is not clear that all these behaviours should be regrouped in the same facility. In particular, escaping all combining codepoints is not suitable for many languages, especially Korean.

Proposed change:

Please consider either:

SG16 chair notes:

The discussion and polls taken during the 2022-10-19 SG16 telecon are consistent with the first bullet of the proposed change:

The poll consensus indicates the following behavior for these examples (assuming UTF-8 for the ordinary literal encoding):

Candidate polls: