On 03/10/2013 07:53 PM, Brian Wolff wrote:
Json standard is pretty clear that any character can
be escaped using \u
<utf-16> code point or you can just have things be utf8. If clients break
because they can't handle that, that is the client's fault. Its not a hard
requirement.
Just a note, the JSON RFC (
https://www.ietf.org/rfc/rfc4627.txt, section
3) explicitly allows any of the main Unicode encodings (UTF-32, UTF-16,
UTF-8) with both endiannesses (except of course UTF-8).
UTF-8 *is* the default encoding, and it's the best choice, but not the
only one.
Matt Flaschen