Re: Syntax

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 09 January 2007 08:18 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4CBP-0006rM-38; Tue, 09 Jan 2007 03:18:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4CBN-0006rE-Ju for cosmogol@ietf.org; Tue, 09 Jan 2007 03:18:09 -0500
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4CBM-0002uD-9z for cosmogol@ietf.org; Tue, 09 Jan 2007 03:18:09 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.nic.fr (Postfix) with ESMTP id 8679026C225; Tue, 9 Jan 2007 09:17:56 +0100 (CET)
X-Virus-Scanned: by amavisd-new at mx2.nic.fr
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id B55CC26C206; Tue, 9 Jan 2007 09:17:53 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id B30D058EBC3; Tue, 9 Jan 2007 09:17:53 +0100 (CET)
Date: Tue, 9 Jan 2007 09:17:53 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Clive D.W. Feather" <clive@demon.net>
Message-ID: <20070109081753.GA1875@nic.fr>
References: <45A129E9.50905@gmx.de> <20070107205255.GA14621@sources.org> <45A20F62.9060306@gmx.de> <20070108204618.GA29407@sources.org> <20070109000704.GB17340@finch-staff-1.thus.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20070109000704.GB17340@finch-staff-1.thus.net>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.17-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: cosmogol@ietf.org
Subject: Re: Syntax
X-BeenThere: cosmogol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: DIscussion on state machine specification in IETF protocols <cosmogol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/cosmogol>, <mailto:cosmogol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/cosmogol>
List-Post: <mailto:cosmogol@ietf.org>
List-Help: <mailto:cosmogol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/cosmogol>, <mailto:cosmogol-request@ietf.org?subject=subscribe>
Errors-To: cosmogol-bounces@ietf.org

On Tue, Jan 09, 2007 at 12:07:04AM +0000,
 Clive D.W. Feather <clive@demon.net> wrote 
 a message of 48 lines which said:

> I seem to have missed a message or two. What is the problem you're trying
> to solve.

Julian Reschke expressed it here:

http://www1.ietf.org/mail-archive/web/cosmogol/current/msg00007.html

Do note that we could be "partly Unicode". We could decide to allow
Unicode only in comments or only in comments and quoted identifiers.

> If it's identifiers using characters outside the ASCII regime, then
> you want people to be able to write them in their own language,

Hmmm, RFC authors are a small minority. RFC readers are more
numerous. An encoding solution, like in RFC 4646 ("Proven&#xE7;al"),
painful for the writer but allowing translators like Shadok to display
nice Unicode characters for the readers (assuming that Graphviz or
other back-ends are Unicode-aware) would be already a big step, it
seems.

> The way we solved this in the C Standard is that you can use such
> characters directly, or you can encode them as \u#### or \U########
> (where # represents a hexadecimal digit). So I can write "xán" or
> "x\u00E1n", and the two are interchangeable.

In C, only in strings, no, not in identifiers? (Cosmogol has only
identifiers.)


_______________________________________________
Cosmogol mailing list
Cosmogol@ietf.org
https://www1.ietf.org/mailman/listinfo/cosmogol