- From: Carsten Bormann <cabo@tzi.org>
- Date: Wed, 27 Nov 2013 00:00:33 +0100
- To: Nico Williams <nico@cryptonector.com>
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, es-discuss <es-discuss@mozilla.org>, www-tag <www-tag@w3.org>, JSON WG <json@ietf.org>
On 26 Nov 2013, at 23:00, Nico Williams <nico@cryptonector.com> wrote: > But you see, if you have any non-Unicode locales, how would such a shell > encode its JSON values? In UTF-8? > Obviously: not in any UTF (except, maybe, > UTF-7). I don’t see the obviousness here. The locale is irrelevant for the encoding of JSON values. > If you wanted to forbid non-Unicode, non-UTF encodings, then you'd be > preventing such a shell, This is a very strange argument. If your application needs a JSON-like interchange format that is encoded in Windows-1252, just go ahead and create that, it’s not hard. Just don’t call it JSON. (I think KSON is still free except as a radio station call sign.:-) Nothing here is prevented by keeping JSON useful as an interchange format. Grüße, Carsten
Received on Tuesday, 26 November 2013 23:01:10 UTC