From pycyn@aol.com Sat Aug 25 11:20:23 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_3_2); 25 Aug 2001 18:20:22 -0000 Received: (qmail 77094 invoked from network); 25 Aug 2001 18:20:22 -0000 Received: from unknown (10.1.10.142) by l8.egroups.com with QMQP; 25 Aug 2001 18:20:22 -0000 Received: from unknown (HELO imo-d02.mx.aol.com) (205.188.157.34) by mta3 with SMTP; 25 Aug 2001 18:20:22 -0000 Received: from Pycyn@aol.com by imo-d02.mx.aol.com (mail_out_v31_r1.4.) id r.bc.1944c45c (659) for ; Sat, 25 Aug 2001 14:20:18 -0400 (EDT) Message-ID: Date: Sat, 25 Aug 2001 14:20:18 EDT Subject: RE: mine, etc. To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_bc.1944c45c.28b94662_boundary" X-Mailer: AOL 6.0 for Windows US sub 10531 From: pycyn@aol.com --part1_bc.1944c45c.28b94662_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit It is important to note that the {me ... me'u} in these constructions with MOI have only an accidental connection with the ordinary {me ... me'u}. The regular one converts a sumti into a selbri somehow related to the sumti, the present one converts any sumti into a number-like sumti, it serves merely as a bracketting device and could have been sone as easily (and more clearly) with something usually used for such bracketting, {vei...ve'o} for example. --part1_bc.1944c45c.28b94662_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit It is important to note that the {me ... me'u} in these constructions with
MOI have only an accidental connection with the ordinary {me ... me'u}. The
regular one converts a sumti into a selbri somehow related to the sumti, the
present one converts any sumti into a number-like sumti, it serves merely as
a bracketting device and could have been sone as easily (and more clearly)
with something usually used for such bracketting, {vei...ve'o} for example. --part1_bc.1944c45c.28b94662_boundary--