Re: [Json] Unpaired surrogates in JSON strings

Douglas Crockford <douglas@crockford.com> Thu, 06 June 2013 10:57 UTC

Return-Path: <douglas@crockford.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 939FF21F9633 for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 03:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.624
X-Spam-Level:
X-Spam-Status: No, score=-1.624 tagged_above=-999 required=5 tests=[AWL=0.975, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePIu50mhZT8i for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 03:57:37 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id B099B21F96E9 for <json@ietf.org>; Thu, 6 Jun 2013 03:57:37 -0700 (PDT)
Received: from [192.168.0.108] (173-228-7-202.dsl.static.sonic.net [173.228.7.202]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MNIR7-1Uid063AfR-006xGT; Thu, 06 Jun 2013 06:57:36 -0400
Message-ID: <51B06B10.8050308@crockford.com>
Date: Thu, 06 Jun 2013 03:57:20 -0700
From: Douglas Crockford <douglas@crockford.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: John Cowan <cowan@mercury.ccil.org>
References: <20130605162246.GG3680@mercury.ccil.org> <51AF7988.6040009@crockford.com> <20130605184702.GB6999@mercury.ccil.org> <51AF8A09.50806@crockford.com> <AE081E5F-82AB-416F-A690-E8373C0369B0@vpnc.org> <CAHBU6is9NBuicPm=mNSTLRUvXjrAt8BA5KH=A4pSeCNJy=vTNQ@mail.gmail.com> <51AFE107.7020301@crockford.com> <20130606035851.GB1362@mercury.ccil.org>
In-Reply-To: <20130606035851.GB1362@mercury.ccil.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:SgbUkIn8w/BU7L7raLou6WtQxVQ9OuRLF7bcgSSLcq4 G8Bo2zAUd4aAzSdQ+gU4YhzAfjVJH2U3LW17AEfuVMO63Zinwn R4PLNPlEZXrIRytxIPZCY3sYUUpm1v8mRDJsej2/p4SBzZCH/Q 4AwyaFw1SJXH52rz/Qj7qjCOOAo3V7EfYWzlXltHjKzW4qvBjZ 4CiE3Xhnali8EPSi51PvlPUYUxh7HjOHKQ3yh2opN8rhr6Nep/ 8Ms32qJ+L6SIx2vZg1p6BI8I5I7oL2MaEfFG5SfPAnNA20Cmq8 412Nl2OsJQ+7yl9lzCUlCmu6PesWXzwXO9PlgPWtuJB68oN1hs GYs6EHEo90BFiEj5dXEA=
Cc: Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Unpaired surrogates in JSON strings
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 10:57:43 -0000

On 6/5/2013 8:58 PM, John Cowan wrote:
> Douglas Crockford scripsit:
>
>> When the RFC talks about Unicode Characters, it is in the sense
>> of Unicode Characters  and not EBCDIC Characters.
> That's just confusing.  "Unicode character" means something quite
> definite in Unicode.  If you mean "character in the Unicode repertoire",
> that's fine -- but all EBCDIC characters, in all variants of EBCDIC,
> are just a subset of that.  There seems to me no reason why JSON
> couldn't be encoded in EBCDIC, with appropriate escapes.
>
Of course it is confusing. The text must be clarified to talk about 
codepoints.