« Bugzilla Issues Index

#503 — Issues in 7.8.4 String Literals

(1) For string literals, it is essential that we interpret them as Unicode code points, not Unicode characters. The Unicode standard doesn't define the term "Unicode character", but from the usage it's clear that it's a subset of Unicode code points that certainly excludes all code points that are reserved for future allocation. String literals must be able to express all possible values of String values, i.e., all sequences of 16-bit integers.

(2) First note: "Basic MultilingualPlane" -> "Basic Multilingual Plane"

(3) First note: Representing Unicode code points in the BMP as single code units is part of UTF-16 just like encoding supplementary characters as two code units. The note could just say that the source code point sequence is mapped to its corresponding UTF-16 code unit sequence.

corrected in editor's draft

fixed in rev10, Sept. 27 2012 draft

Verified in rev 26 draft.