From jjllambias2000@yahoo.com.ar Mon Apr 28 15:12:43 2003 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_6_6); 28 Apr 2003 22:12:43 -0000 Received: (qmail 40989 invoked from network); 28 Apr 2003 21:07:18 -0000 Received: from unknown (66.218.66.218) by m10.grp.scd.yahoo.com with QMQP; 28 Apr 2003 21:07:18 -0000 Received: from unknown (HELO digitalkingdom.org) (204.152.186.175) by mta3.grp.scd.yahoo.com with SMTP; 28 Apr 2003 21:07:18 -0000 Received: from lojban-out by digitalkingdom.org with local (Exim 4.12) id 19AFqI-0002Yl-00 for lojban@yahoogroups.com; Mon, 28 Apr 2003 14:07:18 -0700 Received: from digitalkingdom.org ([204.152.186.175] helo=chain) by digitalkingdom.org with esmtp (Exim 4.12) id 19AFq4-0002Y1-00; Mon, 28 Apr 2003 14:07:04 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 28 Apr 2003 14:07:02 -0700 (PDT) Received: from web20502.mail.yahoo.com ([216.136.226.137]) by digitalkingdom.org with smtp (Exim 4.12) id 19AFpm-0002XI-00 for lojban-list@lojban.org; Mon, 28 Apr 2003 14:06:46 -0700 Message-ID: <20030428210644.20605.qmail@web20502.mail.yahoo.com> Received: from [200.49.74.2] by web20502.mail.yahoo.com via HTTP; Mon, 28 Apr 2003 14:06:44 PDT Date: Mon, 28 Apr 2003 14:06:44 -0700 (PDT) Subject: [lojban] Re: BPFK phpbb To: lojban-list@lojban.org In-Reply-To: <20030428203758.GA99775@allusion.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 4989 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: jjllambias2000@yahoo.com.ar Precedence: bulk X-list: lojban-list From: Jorge "Llambías" Reply-To: jjllambias2000@yahoo.com.ar X-Yahoo-Group-Post: member; u=142311107 X-Yahoo-Profile: jjllambias2000 la djorden cusku di'e > Or how about strange > things like "leka klama keinai cu xamgu". I would say it's equivalent to {na'e bo le ka klama cu xamgu}. > 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"). 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? > Other than the problem with making too many sentences legal, I would > complain that it complicates the parse tree of things like {mi > na.enai do klama}. The first "na" is handled at the same level as > the .e and as part of the structure there. But the second "nai" > (if in UI) is handled at a lower level of the parser (where it > allows UIs after any word). Surely that's transparent to human users. In any case, I believe the official position is that the parse tree is not always related to the semantics. That was mentioned on jboske sometime during the outburst. mu'o mi'e xorxes __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com