W3C home > Mailing lists > Public > www-tag@w3.org > November 2013

Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 21 Nov 2013 13:39:09 +0000
Message-ID: <CADnb78iJUNjdGFPt-D6kXHz-SF1OvotaYPRdPMLZrqHTJNbpfg@mail.gmail.com>
To: Henri Sivonen <hsivonen@hsivonen.fi>
Cc: John Cowan <cowan@mercury.ccil.org>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "www-tag@w3.org" <www-tag@w3.org>, Paul Hoffman <paul.hoffman@vpnc.org>, Pete Cordell <petejson@codalogic.com>, JSON WG <json@ietf.org>, es-discuss <es-discuss@mozilla.org>
On Thu, Nov 21, 2013 at 1:35 PM, Henri Sivonen <hsivonen@hsivonen.fi> wrote:
> UTF-32 harms JSON interchange, because Gecko removed all UTF-32
> support throughout the engine (other engines probably did, too, but
> I'm too busy to check) and, therefore, XHR responseType = "json"
> doesn't support UTF-32.

XHR's responseType = "json" only supports UTF-8 (optionally with a
leading BOM), across the board.

Received on Thursday, 21 November 2013 13:39:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:00 UTC