From pycyn@aol.com Tue Jun 27 08:45:46 2000 Return-Path: Received: (qmail 18088 invoked from network); 27 Jun 2000 14:47:49 -0000 Received: from unknown (10.1.10.26) by m2.onelist.org with QMQP; 27 Jun 2000 14:47:49 -0000 Received: from unknown (HELO imo-d06.mx.aol.com) (205.188.157.38) by mta1 with SMTP; 27 Jun 2000 14:47:48 -0000 Received: from Pycyn@aol.com by imo-d06.mx.aol.com (mail_out_v27.10.) id a.48.7566d50 (4554) for ; Tue, 27 Jun 2000 10:16:05 -0400 (EDT) Message-ID: <48.7566d50.268a1125@aol.com> Date: Tue, 27 Jun 2000 10:16:05 EDT Subject: RE:character names To: lojban@egroups.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 3.0 16-bit for Windows sub 41 From: pycyn@aol.com It is important to note that these names are not for the characters per se but for them in some particular function. That is pretty much what the description of {bu} suggests, but it can lead to minor confusions when the same character is used in different functions: slash for division and subaddressing, say, and when the same function is ma5rked by different characters -- in different programming languages, for example. It might also be sueful to have use-independent names for the characters, for discussion of their various uses.