IETF Logo Mail Archive

Re: [Json] Proposed change: update the Unicode version

John Cowan <cowan@mercury.ccil.org> Wed, 05 June 2013 17:00 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 DC78821F9A19 for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 10:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 1o1dkpEJTW9B for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 10:00:36 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 2BFBD21F99A8 for <json@ietf.org>; Wed, 5 Jun 2013 10:00:31 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UkH4X-0000JD-Aq; Wed, 05 Jun 2013 13:00:29 -0400
Date: Wed, 05 Jun 2013 13:00:29 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tim Bray <tbray@textuality.com>
Message-ID: <20130605170028.GJ3680@mercury.ccil.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC286AF@xmb-rcd-x10.cisco.com> <51AE6E95.3050007@stpeter.im> <CAHBU6iu083Q+tFcBt=CshS68DWFZ-8JH3ahquXKGW1t1GgCyjg@mail.gmail.com> <51AE736D.7030209@stpeter.im> <BF7E36B9C495A6468E8EC573603ED9411527BCD5@xmb-aln-x11.cisco.com> <5DC8FE77-10A8-4835-8415-ACC3FC323663@tzi.org> <CAHBU6itdKgenDnKPP94VWGro+p0GkC-3aDnwqdgztVknu89WJA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAHBU6itdKgenDnKPP94VWGro+p0GkC-3aDnwqdgztVknu89WJA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Carsten Bormann <cabo@tzi.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposed change: update the Unicode version
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: Wed, 05 Jun 2013 17:00:43 -0000

Tim Bray scripsit:

> Hm? The first paragraph says “A Unicode string data type is simply an
> ordered sequence of code units. Thus a Unicode 8-bit string is an ordered
> sequence of 8-bit code units, a Unicode 16-bit string is an ordered
> sequence of 16-bit code units, and a Unicode 32-bit string is an  ordered
> sequence of 32-bit code units.”

Yes, but is that what you actually want?  If so, you probably want the
"sequence of 16-bit code units" language.  This matches JavaScript and
at least some implementations of JSON.

However, I want a JSON string to be an ordered sequence of codepoints/
characters, not of code units.

-- 
Only do what only you can do.               John Cowan <cowan@ccil.org>
  --Edsger W. Dijkstra's advice
    to a student in search of a thesis

v2.23.0 | Report a Bug | By Email