From Wclodius@aol.com  Fri Feb 26 05:31:25 1999
Received: from imo22.mx.aol.com (imo22.mx.aol.com [198.81.17.66])
	by dkuug.dk (8.8.7/8.8.7) with ESMTP id FAA24969
	for <SC22WG5@dkuug.dk>; Fri, 26 Feb 1999 05:31:24 +0100 (CET)
	(envelope-from Wclodius@aol.com)
From: Wclodius@aol.com
Received: from Wclodius@aol.com
	by imo22.mx.aol.com (IMOv18.1) id VXPOa09892
	 for <SC22WG5@dkuug.dk>; Thu, 25 Feb 1999 23:26:09 +1900 (EST)
Message-ID: <42a504c9.36d62261@aol.com>
Date: Thu, 25 Feb 1999 23:26:09 EST
To: SC22WG5@dkuug.dk
Mime-Version: 1.0
Subject: Re: (SC22WG5.1573)  (SC22WG5.1572) (SC22WG5.1571) ISO names for new characters in the Fortran 2000 character set
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Mailer: AOL for Macintosh sub 54


In a message dated 2/25/99 3:51:08 PM, walt@swcp.com writes:

>Ugh! "Curly brackets"  ????
>  [ ] are brackets
>  { } are braces
>I guess this must not be accepted by the international community.
>

I'm surprised you didn't object to

	/	Solidus
	. 	Full Stop

I failed to note in my previous post other differences in ISO 10646 from
Fortran 95's character definitions

	_	Low line
	-	Hyphen-minus
	$	Dollar sign
	 	Space
	%	Percent sign
	<	Less than sign
	>	Greater than sign
	=	Equals sign
	+	Plus sign

I don't know how much importance you want to attach to the additional "sign"
that ISO attaches to many of the above special character definitions, or the
fact that ISO 10646 consistently refers to Fortran's letters as Latin letters.