[i18n-activity] Note about choice of USVString imprecise (#901)

aphillips has just created a new issue for https://github.com/w3c/i18n-activity:

== Note about choice of USVString imprecise ==
WebShare
https://w3c.github.io/web-share/#sharedata-dictionary

> These members are USVString (as opposed to DOMString) because they are not allowed to contain invalid UTF-16 surrogates. This means the user agent is free to re-encode them in any Unicode encoding (e.g., UTF-8). 

The above "Note" about the choice of USVString over DOMString is imprecise. I would suggest the following wording instead:

> These members are USVString (as opposed to DOMString) because they are not allowed to contain surrogate code points (i.e. half of a UTF-16 surrogate pair). Among other things, this means that the user agent can serialize them into any Unicode encoding, such as UTF-8, without change or loss of data or the generation of replacement characters.

---
Instructions: 

Follow the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. **CREATE A PROPOSED REVIEW COMMENT BY REPLACING THE PROMPTS ABOVE THIS PARAGRAPH, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** Then ask the i18n WG to review your comment.

2. After discussion with the i18n WG, raise this issue to the WG that owns the spec. Use the text above this para as the basis for that comment.

3. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue. Do NOT remove the initial '§ '.

4.  Edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. 



**This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**


§ link_to_issue_raised


Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/901 using your GitHub account

Received on Thursday, 7 May 2020 17:05:54 UTC