Skip to content

Commit 0bf8c67

Browse files
authored
Fix Encoding considerations description of codepoint escape sequences. (#339)
The previous text suggested that the \U escape sequence form could only be used with codepoints starting at U+10000, and that both \u and \U forms had to use uppercase hexadecimal characters. This commit updates to correctly reflect that \U escapes can use any codepoint (U+0 to U+10FFFF) and the hexadecimal characters are case-insensitive.
1 parent 9527af6 commit 0bf8c67

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

spec/index.html

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12674,7 +12674,8 @@ <h2>Internet Media Type, File Extension and Macintosh File Type</h2>
1267412674
<dd>The syntax of the SPARQL Query Language is expressed over code points in Unicode
1267512675
[[UNICODE]]. The encoding is always UTF-8 [[RFC3629]].</dd>
1267612676
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or
12677-
\UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
12677+
\UXXXXXXXX syntax (U+0 to U+10FFFF), where X is a hexadecimal digit [0-9A-Fa-f],
12678+
excluding U+D800 to U+DFFF, the <a data-cite="I18N-GLOSSARY#dfn-surrogate">surrogate code points</a>.</dd>
1267812679
<dt>Security considerations:</dt>
1267912680
<dd>
1268012681
See SPARQL Query appendix C, <a href="#security">Security Considerations</a> as well as

0 commit comments

Comments
 (0)