W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2009

RE: Changes to DOM3 Events Key Identifiers

From: Phillips, Addison <addison@amazon.com>
Date: Mon, 2 Nov 2009 17:05:37 -0500
To: John Cowan <cowan@ccil.org>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <C7A5719F1E562149BA9171F58BEE2CA41298694B32@EX-IAD6-B.ant.amazon.com>
Hi John,

Our W3C WG is discussing this in our TPAC meeting today and have a couple of questions about your note. Could you help us understand the following comments:

> Worse yet, the JSON RFC is self-contradictory, with the result that
> it's not even clear that CESU-8-encoded JSON is illegal.

Can you point out where you think the JSON spec is broken?

Thanks!

Addison

Addison Phillips
Globalization Architect -- Lab126
Chair -- W3C Internationalization WG

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: John Cowan [mailto:cowan@ccil.org]
> Sent: Friday, October 30, 2009 5:48 PM
> To: Phillips, Addison
> Cc: John Cowan; Doug Schepers; Mark Davis �??; www-dom@w3.org; www-
> international@w3.org
> Subject: Re: Changes to DOM3 Events Key Identifiers
> 
> Phillips, Addison scripsit:
> 
> > ECMAScript's "firm commitment" to a 16-bit character model (i.e.
> UTF-16)
> 
> If only.
> 
> JavaScript and JSON strings aren't sequences of characters, they
> are
> sequences of 16-bit unsigned integers.  If you happen to want to
> interpret
> them as UTF-16, you are free to do so, but there is not and never
> will
> be any guarantee that all strings are well-formed UTF-16.  What's
> more,
> the built-in JSON serializer provided by ECMAScript 5th edition
> does
> not generate escape sequences for isolated surrogate codepoints, so
> that
> some strings will be written out in CESU-8 rather than UTF-8.
> 
> Worse yet, the JSON RFC is self-contradictory, with the result that
> it's
> not even clear that CESU-8-encoded JSON is illegal.
> 
> --
> Let's face it: software is crap. Feature-laden and bloated, written
> under
> tremendous time-pressure, often by incapable coders, using
> dangerous
> languages and inadequate tools, trying to connect to heaps of
> broken or
> obsolete protocols, implemented equally insufficiently, running on
> unpredictable hardware -- we are all more than used to brokenness.
>                    --Felix Winkelmann
Received on Monday, 2 November 2009 22:06:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:06:22 GMT