IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@stpeter.im> Tue, 04 June 2013 22:47 UTC

Return-Path: <stpeter@stpeter.im>
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 193AC21F99C9 for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 15:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lnlrPitPlv12 for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 15:47:50 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B6C5021F99C3 for <json@ietf.org>; Tue, 4 Jun 2013 15:47:50 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8FE4B41240; Tue, 4 Jun 2013 17:00:59 -0600 (MDT)
Message-ID: <51AE6E95.3050007@stpeter.im>
Date: Tue, 04 Jun 2013 16:47:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC286AF@xmb-rcd-x10.cisco.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70FC286AF@xmb-rcd-x10.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "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: Tue, 04 Jun 2013 22:47:56 -0000

On 6/4/13 4:45 PM, Joe Hildebrand (jhildebr) wrote:
> On 6/4/13 2:31 PM, "Tim Bray" <tbray@textuality.com> wrote:
> 
>> So how about ³A string is a sequence of zero or more Unicode characters
>> defined in version 6.2 (or any subsequent version) of [UNICODE].²
> 
> Much better.
> 
>> WAS:
>>
>> JSON text SHALL be encoded in Unicode.  The default encoding is
>>   UTF-8.
>>
>> Whether it¹s transmitted or read out of a file is irrelevant.
> 
> My point was that "Unicode" is not an encoding.

Indeed. RFC 6365 is your friend. :-)

>> JSON text takes the form of a Unicode string [UNICODE, section 2.7]; the
>> default encoding is UTF-8.
> 
> That's fine.

Are people using UTF-16 or UTF-32? Is there a good reason not to say
"MUST encode using UTF-8"?

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

v2.23.0 | Report a Bug | By Email