From pycyn@aol.com Sat Oct 06 15:56:29 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_4_1); 6 Oct 2001 22:56:29 -0000 Received: (qmail 51964 invoked from network); 6 Oct 2001 22:56:29 -0000 Received: from unknown (10.1.10.26) by l8.egroups.com with QMQP; 6 Oct 2001 22:56:29 -0000 Received: from unknown (HELO imo-d06.mx.aol.com) (205.188.157.38) by mta1 with SMTP; 6 Oct 2001 22:56:29 -0000 Received: from Pycyn@aol.com by imo-d06.mx.aol.com (mail_out_v31_r1.7.) id r.c8.1bac4e29 (3958) for ; Sat, 6 Oct 2001 18:56:24 -0400 (EDT) Message-ID: Date: Sat, 6 Oct 2001 18:56:24 EDT Subject: Re: [lojban] Re: noxemol ce'u To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_c8.1bac4e29.28f0e618_boundary" X-Mailer: AOL 6.0 for Windows US sub 10535 From: pycyn@aol.com X-Yahoo-Message-Num: 11401 --part1_c8.1bac4e29.28f0e618_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 10/6/2001 4:58:32 PM Central Daylight Time, rob@twcny.rr.com writes: > pc, your entire argument seems to revolve around this incorrect statement. > There is no subordinate bridi in {le mamta be ce'u}. You can gripe all you > want > that it would be more "linguistically correct" if that were considered a > bridi, > but at this point it sounds just like tinkit claiming hexadecimal is the > See definition of {bridi} provided in same note. Sloppy usage is common, but no reason why we should follow it or let someone use it to grind us down. Let And keep chinging what he says until he finally gets something that is nontrivial and true. --part1_c8.1bac4e29.28f0e618_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 10/6/2001 4:58:32 PM Central Daylight Time, rob@twcny.rr.com writes:




pc, your entire argument seems to revolve around this incorrect statement.
There is no subordinate bridi in {le mamta be ce'u}. You can gripe all you want
that it would be more "linguistically correct" if that were considered a bridi,
but at this point it sounds just like tinkit claiming hexadecimal is the
default in Lojban, over and over






See definition of {bridi} provided in same note.  Sloppy usage is common, but no reason why we should follow it or let someone use it to grind us down.  Let And keep chinging what he says until he finally gets something that is nontrivial and true. --part1_c8.1bac4e29.28f0e618_boundary--