* 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:[email protected] · 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/ _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
