W3C home > Mailing lists > Public > www-tag@w3.org > November 2013

Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 26 Nov 2013 21:22:28 +0100
Message-ID: <52950304.8080403@gmx.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>, Nico Williams <nico@cryptonector.com>
CC: es-discuss <es-discuss@mozilla.org>, www-tag <www-tag@w3.org>, JSON WG <json@ietf.org>
On 2013-11-26 21:15, Bjoern Hoehrmann wrote:
> * Nico Williams wrote:
>> We must not require encoding detection functionality in parsers.  We
>> must not forbid it either.  We might need to say that encodings other
>> than UTF-8/16/32 may not be reliably detected, therefore they are highly
>> discouraged, even forbidden except where protocols specifically call for
>> them.
> When I pass a fully conforming UTF-8 encoded application/json entity to
> a fully conforming JSON parser I do not want the parser to do something
> funny like interpreting the document as if it were Windows-1252 encoded.
> I am amazed how many people here think a parser that does that should
> not be considered broken.

Received on Tuesday, 26 November 2013 20:22:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:00 UTC