Re: Next step (Was: I-D ACTION:draft-klensin-unicode-escapes-00.txt

John C Klensin <john-ietf@jck.com> Thu, 25 January 2007 11:58 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HA3Fc-0003oH-Fe; Thu, 25 Jan 2007 06:58:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HA3Fb-0003nw-Mk for discuss@apps.ietf.org; Thu, 25 Jan 2007 06:58:43 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HA3Fa-0002Na-BO for discuss@apps.ietf.org; Thu, 25 Jan 2007 06:58:43 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1HA3FY-000ACX-PK; Thu, 25 Jan 2007 06:58:40 -0500
Date: Thu, 25 Jan 2007 06:58:40 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Clive D.W. Feather" <clive@demon.net>
Subject: Re: Next step (Was: I-D ACTION:draft-klensin-unicode-escapes-00.txt
Message-ID: <9A1900D9A9C2207B3C75C33A@p3.JCK.COM>
In-Reply-To: <20070125080118.GE18174@finch-staff-1.thus.net>
References: <B1930392E9C03720F9E495F8@p3.JCK.COM> <20070124153126.GA12389@nic.fr> <48AE8F8343DFAA3BC6DEB491@p3.JCK.COM> <20070125080118.GE18174@finch-staff-1.thus.net>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org


--On Thursday, 25 January, 2007 08:01 +0000 "Clive D.W. Feather"
<clive@demon.net> wrote:

> John C Klensin said:
>>> But there is (may be) a rough consensus that every scheme
>>> with explicit delimiters (&#xNNNN; or \u{NNNNN}) is better
>>> than any scheme without them? If so, it would be a progress.
>> Much as I would personally prefer that answer, I haven't seen
>> such a consensus emerge yet.
> 
> Well, let's start by seeing if there is.
> 
> I've seen three people here in favour of it. I've seen you
> saying that one variety (the XML one) is ugly, but I don't
> know if you think that that outweighs the benefits of explicit
> delimiters.
> 
> So: is there anybody here - including John - who thinks that
> the chosen format SHOULD NOT use explicit delimiters?

I personally favor explicit delimiters, I have all along.  My
definition of "ugly" involves two things.  The first may be
unavoidable, the second is not:

(i) Use of a sequence of special characters, none of which may
be completely familiar to those who don't regularly use a fairly
full set of Roman characters and both of which, IIR, are
assigned to "national use" positions in ISO 646 BV, meaning that
they may show up in even more different ways in some
presentations.

(ii) If we are going to use explicit delimiters, my aesthetic
and historical sense, and the ability to get help from common
programming-oriented editors and syntax-checkers, favors paired
delimiters over subjectively unmatched ones, e.g.,
   X(nnnn...)
or
   U'nnnn...'
in preference to
   &#nnnn...;

These are, however, just matters of personal taste.

     john