- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 22 Nov 2013 19:41:35 +0100
- To: "Matt Miller (mamille2)" <mamille2@cisco.com>, JSON WG <json@ietf.org>
- CC: "www-tag@w3.org" <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
On 2013-11-22 19:33, Matt Miller (mamille2) wrote: > There does seem to be rough consensus that using an encoding other than UTF-8 can have interoperability issues. The also seems to be rough consensus that the current text and table in section 8.1 for detecting the encoding will be inaccurate (and potentially harmful). > > That appears to mean the approach with the most consensus is to remove the encoding detection entirely, leaving only: > > """" > JSON text SHALL be encoded in Unicode. The default encoding is > UTF-8. > """" > > > - Paul Hoffman and Matt Miller Again: "JSON text SHALL be encoded in Unicode." doesn't make any sense. "Unicode" is not a character encoding. Can we please use proper terminology here? Best regards, Julian
Received on Friday, 22 November 2013 18:42:18 UTC