Re: [Json] Unpaired surrogates in JSON strings
Tim Bray <tbray@textuality.com> Thu, 06 June 2013 04:48 UTC
Return-Path: <tbray@textuality.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 A0E9921F961F for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 21:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.073
X-Spam-Level: *
X-Spam-Status: No, score=1.073 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.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 Rdo577MOdfac for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 21:48:36 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3682821F961B for <json@ietf.org>; Wed, 5 Jun 2013 21:48:36 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pa12so1843315veb.39 for <json@ietf.org>; Wed, 05 Jun 2013 21:48:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=s1wjAq4Z5EIhZbThj39tmAdHITrDRuciPzNEZ/z+yzY=; b=k7E6aa3RD+y59RSguoz4cWZPm1F1QE7Uwu799iGCUxQhccYJ3iE9Yli9juCNZbJC1D mnkix9oP4rekzjy9TlEYxW70G4pu9Gg1y4HaWyUQ3Bm1L3HCH2fGCGy8qAqEX60yEAN0 8EsWe8NP32ywL8G+QAkF7YV1rJyNmbD0wz5mqgBGhHLE3QGI3yD4WWtlWYEHTejZ6zbc L0KXKMTdVnuYIM/GGE4oWmaL0b+qA9Dd/vOoIzPjU3Pg2B67kCMs1NRbkYZkXOGUPudo hBGS1nygNgOzWrJhdCnwATnvCZFFUc2AQwGp/1fD0N4kTHwBMv1IBj3d2+ZeWnPUpSqw VtbA==
MIME-Version: 1.0
X-Received: by 10.52.112.5 with SMTP id im5mr2883959vdb.4.1370494115603; Wed, 05 Jun 2013 21:48:35 -0700 (PDT)
Received: by 10.220.48.14 with HTTP; Wed, 5 Jun 2013 21:48:35 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <20130606010945.GA1362@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> <20130606010945.GA1362@mercury.ccil.org>
Date: Wed, 05 Jun 2013 21:48:35 -0700
Message-ID: <CAHBU6isarPqHv0Xteg1c1xKNbZ7N8TE-9qh7N2uwEHU3uQubNA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: multipart/alternative; boundary="bcaec54857e8ed7d1804de750617"
X-Gm-Message-State: ALoCoQnG9f2hk0PibCFj//e+RGnB/T27kYnGUwvlrX1HSs3JBALnaIFlfVrRTR0hk8CQ9KgABWk/
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Douglas Crockford <douglas@crockford.com>, "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 04:48:40 -0000
On Wed, Jun 5, 2013 at 6:09 PM, John Cowan <cowan@mercury.ccil.org> wrote: > > I think anyone who’s delivering those codepoints is already in > > violation of 4627, and I don’t think we should retroactively forgive > > those sins. > > It's already been stated that ECMA can't swallow this change. > I thought ECMA’s indigestion was over dupe keys. It seems to me that if unpaired surrogates are to be allowed, it’s not OK for the spec to assert that strings are made of Unicode characters, because both of these things can’t be correct. -T > > -- > John Cowan cowan@ccil.org http://ccil.org/~cowan > Objective consideration of contemporary phenomena compel the conclusion > that optimum or inadequate performance in the trend of competitive > activities exhibits no tendency to be commensurate with innate capacity, > but that a considerable element of the unpredictable must invariably be > taken into account. --Ecclesiastes 9:11, Orwell/Brown version >
- [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings Paul Hoffman
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] Unpaired surrogates in JSON strings Paul Hoffman
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Tim Bray
- Re: [Json] Unpaired surrogates in JSON strings Paul Hoffman
- Re: [Json] Unpaired surrogates in JSON strings Tim Bray
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings R S
- Re: [Json] Unpaired surrogates in JSON strings Carsten Bormann
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Tim Bray
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Carsten Bormann
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings Douglas Crockford
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Tim Bray
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Paul Hoffman
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] Unpaired surrogates in JSON strings Martin J. Dürst
- Re: [Json] Unpaired surrogates in JSON strings Bjoern Hoehrmann
- [Json] On characters and code points Paul Hoffman
- Re: [Json] On characters and code points Tim Bray
- Re: [Json] On characters and code points Stephen Dolan
- Re: [Json] On characters and code points Stefan Drees
- Re: [Json] On characters and code points Tim Bray
- Re: [Json] On characters and code points Stefan Drees
- Re: [Json] On characters and code points Tim Bray
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] On characters and code points John Cowan
- Re: [Json] On characters and code points John Cowan
- Re: [Json] On characters and code points Tim Bray
- Re: [Json] On characters and code points John Cowan
- Re: [Json] Unpaired surrogates in JSON strings Nico Williams
- Re: [Json] Unpaired surrogates in JSON strings Nico Williams
- Re: [Json] Unpaired surrogates in JSON strings Tatu Saloranta
- Re: [Json] Unpaired surrogates in JSON strings Joe Hildebrand (jhildebr)
- Re: [Json] On characters and code points Bjoern Hoehrmann
- Re: [Json] On characters and code points Tim Bray
- Re: [Json] Unpaired surrogates in JSON strings John Cowan
- Re: [Json] On characters and code points Nico Williams
- Re: [Json] On characters and code points John Cowan
- Re: [Json] On characters and code points Bjoern Hoehrmann
- Re: [Json] On characters and code points Carsten Bormann
- Re: [Json] On characters and code points Stefan Drees
- Re: [Json] On characters and code points Paul Hoffman
- Re: [Json] On characters and code points Carsten Bormann
- Re: [Json] On characters and code points Nico Williams