- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Tue, 26 Nov 2013 21:15:38 +0100
- To: Nico Williams <nico@cryptonector.com>
- Cc: JSON WG <json@ietf.org>, www-tag <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
* 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. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 26 November 2013 20:16:06 UTC