Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
JP22: maybe typo? #90
Probably supposed to be an issue not a pull request? The offending text is in clause 2. I have no idea what "If the adopted ISO/IEC 10646-1 subset is not otherwise specified, it is presumed to be the Unicode set, collection 10646" means or is intended to clarify...
Collection 10646 is defined in ISO 10646, just a few lines down from collection 308. It allows for the entire code space of Unicode except for non-characters, with no restriction based on Unicode versions.
If this causes confusion, I'd suggest removing it entirely. De facto, ECMA-262 imposes no restrictions on the contents of string values, and where it interprets the contents of strings or source code, it does so based on the Unicode Standard, not based on ISO 10646. I think the references to ISO 10646 exist primarily to smooth promotion from ECMA-262 to ISO 16262; they don't add any normative value.