From lojban-out@lojban.org Mon Apr 28 18:00:16 2003 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_6_6); 29 Apr 2003 01:00:16 -0000 Received: (qmail 92036 invoked from network); 29 Apr 2003 01:00:15 -0000 Received: from unknown (66.218.66.217) by m5.grp.scd.yahoo.com with QMQP; 29 Apr 2003 01:00:15 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta2.grp.scd.yahoo.com with SMTP; 29 Apr 2003 01:00:15 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.12) id 19AJTi-0006RQ-00 for lojban@yahoogroups.com; Mon, 28 Apr 2003 18:00:14 -0700 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.12) id 19AJTU-0006Qz-00; Mon, 28 Apr 2003 18:00:00 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 28 Apr 2003 17:59:58 -0700 (PDT) Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root) by digitalkingdom.org with esmtp (Exim 4.12) id 19AJTK-0006Qn-00 for lojban-list@lojban.org; Mon, 28 Apr 2003 17:59:51 -0700 Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1]) by cs6668125-184.austin.rr.com (8.12.6p2/8.12.3) with ESMTP id h3T1Bbsr001293 for ; Mon, 28 Apr 2003 20:11:38 -0500 (CDT) (envelope-from fracture@cs6668125-184.austin.rr.com) Received: (from fracture@localhost) by cs6668125-184.austin.rr.com (8.12.6p2/8.12.3/Submit) id h3T1BWSD001290 for lojban-list@lojban.org; Mon, 28 Apr 2003 20:11:32 -0500 (CDT) Date: Mon, 28 Apr 2003 20:11:32 -0500 To: lojban-list@lojban.org Subject: [lojban] Re: BPFK phpbb Message-ID: <20030429011132.GA1205@allusion.net> References: <20030428203758.GA99775@allusion.net> <20030428210644.20605.qmail@web20502.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <20030428210644.20605.qmail@web20502.mail.yahoo.com> User-Agent: Mutt/1.5.1i X-archive-position: 4994 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: fracture@allusion.net Precedence: bulk X-list: lojban-list X-eGroups-From: Jordan DeLong From: Jordan DeLong Reply-To: fracture@allusion.net X-Yahoo-Group-Post: member; u=116389790 X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 19472 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 28, 2003 at 02:06:44PM -0700, Jorge Llamb=EDas wrote: > la djorden cusku di'e > > Or how about strange > > things like "leka klama keinai cu xamgu". >=20 > I would say it's equivalent to {na'e bo le ka klama cu xamgu}. But this is a contradiction of what you say below... > > Anyway, I dunno why the text rule allows a nai at the start, but > > you're ignoring camgusmis' point by focusing on that---namely that > > if nai is in UI, it can be used *anywhere*, and thus it should be > > a word which makes sense to be used anywhere (like "ui"). >=20 > But it _is_ a word that makes sense used anywhere: it changes the > previous word into an opposite. Isn't that how it works now, > except now it only works with a selected set of previous words? [...] It's not how it works now, and if it were how it worked and it were in UI, then using nai after a terminator as I suggested above would have Weird Effects; it could not be equivalent to a na'ebo in front of the last sumti. What does nu'inai mean? nu'i nai ge do mi gi mi do nu'u citka --=20 Jordan DeLong - fracture@allusion.net lu zo'o loi censa bakni cu terzba le zaltapla poi xagrai li'u sei la mark. tuen. cusku --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline [Attachment content not displayed.] --2oS5YaxWCcQjTEyO--