- From: Carsten Bormann <cabo@tzi.org>
- Date: Wed, 27 Nov 2013 00:20:25 +0100
- To: Nico Williams <nico@cryptonector.com>
- Cc: JSON WG <json@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, www-tag <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
On 27 Nov 2013, at 00:07, Nico Williams <nico@cryptonector.com> wrote: > Do you want to say anything about other encodings? What would that be? JSON is encoded in UTF-8. There is no need to discuss JSON in other encodings, because it wouldn’t be JSON. (And no, I see no need to handle UTF-16LE, UTF-16BE, UTF-32LE or UTF-32BE in any special way, even if RFC 4627 was written at a time when it still seemed useful to pay them lip service. But I recognize that there appears to be WG consensus to keep these corpses on life support, maybe because UTF-16 is the internal encoding of the programming language that gave JSON its name.) Grüße, Carsten
Received on Tuesday, 26 November 2013 23:20:58 UTC