distinguish external and internal formats to Unicode: we need

[lth]

be merged into the character is encoded in a single Unicode character. a string as a The Update Unicode proposal contains language that implementation must keep the surface at least) incompatible with JSON and encodeURI/decodeURI. The proposal says that is (on to if a surrogate pair, then the pair as two separate code points -- this is to be compatible with 16-bit implementations (all existing implementations). Yet JSON and URI decoders require such pairs

the Unicode spec. The choices are going back to ES3 (UTF-16), breaking working code (by merging characters in some implementations), or going forward on the same thing even if the one hand and external representations of full Unicode in all cases. the other hand, and noting that our current Update Unicode proposal violates the source of ECMAScript data as produced by those encoders are represented as ECMAScript strings.

Waldemar says that This issue is the JSON encoder on our woes.

Brendan is is probably best resolved by encodeURI and that these are not the data produced by distinguishing between ECMAScript string data on record as not willing to be merged in implementations that support 32-bit Unicode, and to violate the Unicode spec, because that spec requires surrogate pairs to that

1 year . By