Author akira
Recipients Julian, akira, cvrebert, ezio.melotti, haypo, jleedev, ncoghlan, pitrou, rhettinger, serhiy.storchaka
Date 2014-05-16.02:39:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400207983.09.0.241343275669.issue17909@psf.upfronthosting.co.za>
In-reply-to
Content
Both json standard (ECMA-404) [1] and the new json rfc 7159 [2] do not mention
the encoding detection.

[1] http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
[2] https://tools.ietf.org/html/rfc7159#section-8.1

From the rfc:

> JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32.  The default
  encoding is UTF-8, and JSON texts that are encoded in UTF-8 are
  interoperable in the sense that they will be read successfully by the
  maximum number of implementations; there are many implementations
  that cannot successfully read texts in other encodings (such as
  UTF-16 and UTF-32).

  Implementations MUST NOT add a byte order mark to the beginning of a
  JSON text.  In the interests of interoperability, implementations
  that parse JSON texts MAY ignore the presence of a byte order mark
  rather than treating it as an error.
History
Date User Action Args
2014-05-16 02:39:43akirasetrecipients: + akira, rhettinger, ncoghlan, pitrou, haypo, ezio.melotti, cvrebert, Julian, serhiy.storchaka, jleedev
2014-05-16 02:39:43akirasetmessageid: <1400207983.09.0.241343275669.issue17909@psf.upfronthosting.co.za>
2014-05-16 02:39:43akiralinkissue17909 messages
2014-05-16 02:39:41akiracreate