Re: Next step
Frank Ellermann <nobody@xyzzy.claranet.de> Fri, 26 January 2007 22:35 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HAZfD-00015p-23; Fri, 26 Jan 2007 17:35:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HAZfA-00015f-Vz
for discuss@apps.ietf.org; Fri, 26 Jan 2007 17:35:18 -0500
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAZf9-00042O-Lz
for discuss@apps.ietf.org; Fri, 26 Jan 2007 17:35:16 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1HAZf2-00085B-DP
for discuss@apps.ietf.org; Fri, 26 Jan 2007 23:35:08 +0100
Received: from d254130.dialin.hansenet.de ([80.171.254.130])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <discuss@apps.ietf.org>; Fri, 26 Jan 2007 23:35:08 +0100
Received: from nobody by d254130.dialin.hansenet.de with local (Gmexim 0.1
(Debian)) id 1AlnuQ-0007hv-00
for <discuss@apps.ietf.org>; Fri, 26 Jan 2007 23:35:08 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: discuss@apps.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: Next step
Date: Fri, 26 Jan 2007 23:34:46 +0100
Organization: <URL:http://purl.net/xyzzy>
Lines: 26
Message-ID: <45BA8206.3532@xyzzy.claranet.de>
References: <B1930392E9C03720F9E495F8@p3.JCK.COM>
<20070124153126.GA12389@nic.fr>
<48AE8F8343DFAA3BC6DEB491@p3.JCK.COM>
<20070125080118.GE18174@finch-staff-1.thus.net>
<9A1900D9A9C2207B3C75C33A@p3.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: d254130.dialin.hansenet.de
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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
John C Klensin wrote: [􂍅 might be ugly] > 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 No C trigraph for "&", but "#" has "??=". IMO that's a historic foot note, nobody used weird "national variants" of ASCII for at least a decade. And we're talking about US ASCII anyway. > the ability to get help from common programming-oriented > editors and syntax-checkers, favors paired delimiters over > subjectively unmatched ones Is that about protocols needing a new escape mechanism, or about the prose in RFCs ? In the former case some piece of software will do it, in the latter case an editor macro can take care of the raw UTF-8 or whatever it is. An example is <http://purl.net/xyzzy/kex/x-wiki.kex> for an XEDIT-clone. Frank
- Next step (Was: I-D ACTION:draft-klensin-unicode-… John C Klensin
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… Stephane Bortzmeyer
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… der Mouse
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… John C Klensin
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… John C Klensin
- Re: Next step Frank Ellermann
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… John C Klensin
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… Clive D.W. Feather
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… Clive D.W. Feather
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… Clive D.W. Feather
- Re: Next step Clive D.W. Feather
- Re: Next step (Was: I-D ACTION:draft-klensin-unic… John C Klensin
- Re: Next step Frank Ellermann
- Re: Next step Frank Ellermann