W3C home > Mailing lists > Public > public-i18n-archive@w3.org > April to June 2022

Re: [bp-i18n-specdev] Consider creating a rule regarding rejecting invalid surrogate pairs (#10)

From: r12a via GitHub <sysbot+gh@w3.org>
Date: Mon, 09 May 2022 12:24:51 +0000
To: public-i18n-archive@w3.org
Message-ID: <issue_comment.created-1121032031-1652099090-sysbot+gh@w3.org>

A "surrogate code point" refers here to the use of code points in the range U+D800 through U+DFF, inclusive. These code points only exist to allow the UTF-16 encoding to address supplementary characters, and are always used in pairs.  A single  surrogate code point is referred to as an "unpaired surrogate" and should never be used.

I'm not sure it needs to be in a note.  It's just an explanation like many others of a piece of mustard.

I think it would also improve understanding (since the explanation is not always alongside the mustard) to change the guideline to say:

Specifications MUST NOT allow the use of unpaired surrogate code point.

GitHub Notification of comment by r12a
Please view or discuss this issue at https://github.com/w3c/bp-i18n-specdev/issues/10#issuecomment-1121032031 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 May 2022 12:24:53 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 18:09:47 UTC