IETF Logo Mail Archive

Re: [Json] Unpaired surrogates in JSON strings

John Cowan <cowan@mercury.ccil.org> Thu, 06 June 2013 03:58 UTC

Return-Path: <cowan@ccil.org>
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 6EA3521F8F9E for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 20:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 UHsZ2ycHhq+U for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 20:58:54 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 212EA21F8D79 for <json@ietf.org>; Wed, 5 Jun 2013 20:58:54 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UkRLf-0000Rv-HX; Wed, 05 Jun 2013 23:58:51 -0400
Date: Wed, 05 Jun 2013 23:58:51 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Douglas Crockford <douglas@crockford.com>
Message-ID: <20130606035851.GB1362@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <51AFE107.7020301@crockford.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
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 03:58:58 -0000

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.

-- 
John Cowan  cowan@ccil.org  http://ccil.org/~cowan
In computer science, we stand on each other's feet.
        --Brian K. Reid

v2.23.0 | Report a Bug | By Email