IETF Logo Mail Archive

Re: [Json] On characters and code points

John Cowan <cowan@mercury.ccil.org> Sat, 08 June 2013 03:06 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 A50B411E80A6 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 20:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.335
X-Spam-Level:
X-Spam-Status: No, score=-3.335 tagged_above=-999 required=5 tests=[AWL=0.264, 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 CPKFlxVBGEyX for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 20:06:31 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id A299721E805D for <json@ietf.org>; Fri, 7 Jun 2013 20:06:26 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Ul9Tw-0000un-KI; Fri, 07 Jun 2013 23:06:21 -0400
Date: Fri, 07 Jun 2013 23:06:20 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Nico Williams <nico@cryptonector.com>
Message-ID: <20130608030620.GA2528@mercury.ccil.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC2E7E1@xmb-rcd-x10.cisco.com> <51B06F38.8050707@crockford.com> <CAHBU6iuFBuW-RfgBLQF5q4BnUOzs088QXW3uOQG1OjBFjZttkw@mail.gmail.com> <51B1B4E7.8090101@it.aoyama.ac.jp> <9ld3r8pc0tufif18dohb2fmi0ijna1vs4n@hive.bjoern.hoehrmann.de> <56A163E9-E7CD-46B3-9984-8F009EBFF500@vpnc.org> <CA+mHimO-bUvodjgM89Nskg+tqWrsTAfL8EWRx++fd16t1hFR_g@mail.gmail.com> <o4a4r8ldc0sp12k310b9gv3486ht4sis2l@hive.bjoern.hoehrmann.de> <CAHBU6ivCEYhSoZo6pSg+wt6J2q+qnPB5aKV8_NgGfGF--h2tUw@mail.gmail.com> <CAK3OfOicD1sMbpJV3F+FLjmM50_48shpO_TE8w50HPRZznYYng@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAK3OfOicD1sMbpJV3F+FLjmM50_48shpO_TE8w50HPRZznYYng@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Stephen Dolan <stephen.dolan@cl.cam.ac.uk>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] On characters and code points
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: Sat, 08 Jun 2013 03:06:36 -0000

Nico Williams scripsit:

> But corrigendum #9 does make me think that the best thing to do is to
> pass them through, as with any other noncharacters and private-use
> code points.  If nothing else it's one less thing to check for in a
> parser.

If the parser provides an internal representation other than UTF-16,
however, that just isn't possible.

-- 
John Cowan <cowan@ccil.org>             http://www.ccil.org/~cowan
Awk!" sed Grep. "A fscking python is perloining my Ruby; let me bash
    him with a Cshell!  Vi didn't I mount it on a troff?" --Francis Turner

v2.23.0 | Report a Bug | By Email