Le jeudi, 7 mai 2015 à 21:23, Jeff Senn a écrit : > Not to mention the ambiguous case of a surrogate pair where half is literal > and the other half quoted...
I don't think this is an issue. It's not ambiguous: the standard mentions that JSON text shall be encoded in UTF-8, UTF-16 or UTF-32 so what you get in this case is an (UTF-16) character stream decoding error. Best, Daniel
