IETF Logo Mail Archive

Re: [Json] On characters and code points

Bjoern Hoehrmann <derhoermi@gmx.net> Sat, 08 June 2013 08:47 UTC

Return-Path: <derhoermi@gmx.net>
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 7B15E21F898B for <json@ietfa.amsl.com>; Sat, 8 Jun 2013 01:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Hz129oPWc5Ii for <json@ietfa.amsl.com>; Sat, 8 Jun 2013 01:47:42 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id C782A21F9362 for <json@ietf.org>; Sat, 8 Jun 2013 01:47:41 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MRyq4-1UvZcE2e3W-00THLE for <json@ietf.org>; Sat, 08 Jun 2013 10:47:40 +0200
Received: (qmail invoked by alias); 08 Jun 2013 08:47:40 -0000
Received: from p54B4EB09.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [84.180.235.9] by mail.gmx.net (mp020) with SMTP; 08 Jun 2013 10:47:40 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+FFeUTe+yF2Y9aNfye8NX5s9vDvfq6ZEpITHKSuf Pf+u0Q7vg/dQ4f
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John Cowan <cowan@mercury.ccil.org>
Date: Sat, 08 Jun 2013 10:47:42 +0200
Message-ID: <0rq5r8hmbdum0aj6l1usdb9ciulaghf0lc@hive.bjoern.hoehrmann.de>
References: <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> <20130608030620.GA2528@mercury.ccil.org>
In-Reply-To: <20130608030620.GA2528@mercury.ccil.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "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 08:47:46 -0000

* John Cowan wrote:
>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.

Unpaired surrogate code points cannot be represented in UTF-16 and you
can easily use e.g. `UTF-32-but-allow-unpaired-surrogates` internally.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

v2.23.0 | Report a Bug | By Email