From sentto-44114-17472-1038897819-lojban-in=lojban.org@returns.groups.yahoo.com Mon Dec 02 22:44:14 2002 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 02 Dec 2002 22:44:14 -0800 (PST) Received: from n38.grp.scd.yahoo.com ([66.218.66.106]) by digitalkingdom.org with smtp (Exim 4.05) id 18J6mw-0006o3-01 for lojban-in@lojban.org; Mon, 02 Dec 2002 22:44:10 -0800 X-eGroups-Return: sentto-44114-17472-1038897819-lojban-in=lojban.org@returns.groups.yahoo.com Received: from [66.218.67.193] by n38.grp.scd.yahoo.com with NNFMP; 03 Dec 2002 06:43:39 -0000 X-Sender: lojbab@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_2_3_0); 3 Dec 2002 06:43:38 -0000 Received: (qmail 97162 invoked from network); 3 Dec 2002 06:43:38 -0000 Received: from unknown (66.218.66.216) by m11.grp.scd.yahoo.com with QMQP; 3 Dec 2002 06:43:38 -0000 Received: from unknown (HELO lakemtao02.cox.net) (68.1.17.243) by mta1.grp.scd.yahoo.com with SMTP; 3 Dec 2002 06:43:38 -0000 Received: from lojban.lojban.org ([68.100.206.153]) by lakemtao02.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20021203064336.FXGC2203.lakemtao02.cox.net@lojban.lojban.org> for ; Tue, 3 Dec 2002 01:43:36 -0500 Message-Id: <5.2.0.9.0.20021203003633.03242a10@pop.east.cox.net> X-Sender: rlechevalier@pop.east.cox.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 To: lojban@yahoogroups.com In-Reply-To: References: <20021202163912.GB37047@allusion.net> From: Robert LeChevalier X-Yahoo-Profile: lojbab MIME-Version: 1.0 Mailing-List: list lojban@yahoogroups.com; contact lojban-owner@yahoogroups.com Delivered-To: mailing list lojban@yahoogroups.com Precedence: bulk Date: Tue, 03 Dec 2002 01:36:51 -0500 Subject: [lojban] Re: ka'enai (was: Re: A question on the new baseline policy) Content-Type: text/plain; charset=US-ASCII X-archive-position: 2959 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: lojbab@lojban.org Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list At 01:22 AM 12/3/02 +0000, And Rosta wrote: >Jordan: > > On Mon, Dec 02, 2002 at 12:51:52PM -0000, And Rosta wrote: > > > Jordan to Craig: > > > > Why aren't you complaining that you can't say "za'onai"? > > > He well could be. In a former discussion about how to translate > > > English "still" and "already", {ba'o nai} emerged as the best > > > candidate for rendering "still" (as I recall). I guess {na'e > > > ba'o} would do the job too, but it is certainly not true that > > > nobody has hitherto supposed ZAhO+NAI useful > > > > I meant to say ze'u nai. There's a *bunch* of tenses you can't put > > nai on. People presenting the 'case' for ka'e+nai generally claim > > that it improves "consistency", when it does the opposite > >You're right in one sense, but I think the underlying idea is that >if there were a grammar change it would be to give NAI the distribution >of UI, so that its distribution would be overall less arbitrary and >more learnable. I think that NAI treated as a UI would cause more (semantics) problems than you can imagine (and we did consider it, albeit VERY briefly). You are the one who wants better semantics definition. Grammatically it would be a major change because NAI is in so many rules. pa re nai ci? (pa re .uinai ci passes the parser) It would mean that the logical connectives are handled by hodgepodge: je and naje would be lexer tokens, but najenai would grammatically be naje with an absorbed nai as part of the je hence implying "na (je nai)" which is not correct. You would fix something by breaking other things, and raise far more questions that you would answer. > > > The general thrust of the pro CAhA+NAI camp is that the unofficial > > > rule "NAI has the distribution of UI" is what many people have > > > internalized, through naturalistic inductive methods of learning > > > the grammar. The argument is therefore that the unofficial rule > > > has proved itself to be more natural, and since it is harmless > > > and has the added virtue of simplifying the grammar a little, it > > > is a candidate for being officially formalized > > > > This "unofficial rule" is simply an error. NAI is not a UI. It > > is not a CAI either. I *highly* doubt the BF even has the authority > > to change a cmavo to a different selma'o, so if they were to accept > > ka'enai it would likely be done by hacking the tense grammar to > > allow NAI after CAhA, and not by changing NAI to UI > >Do you understand that I am trying to explain to how how the opposing >side sees things? The actual debate should go to the BF. I was just >trying to point out to you that everybody else isn't as stupid as >you think they are. Just the "opposing side" that sees things that way %^) > > I am confident that the more ka'enai users who give a bit of effort > > to understand why it is not allowed, the more of them that will > > abandon ka'e+nai of their own accord. I've not seen a single > > argument for CAhA+NAI that didn't consist of "It's more consistent", > > which is completely false, so I believe people can be convinced on > > this issue > >Is "It's more consistent that NAI be in UI rather than be able to >cooccur with an apparently arbitrary and deductively unpredictable >subset of selmaho" completely false? Yes. nai is far less arbitrary and difficult to learn than the elidability terminators, or the places where free modifiers are and are not allowed. There are some things is the language that are restricted by the need to have LALR1. Resorting to UI is a copout since UI has no grammatical interaction OTHER THAN with the prior word (and the prior word determines its scope which I don't think would be true with nai). lojbab -- lojbab lojbab@lojban.org Bob LeChevalier, President, The Logical Language Group, Inc. 2904 Beau Lane, Fairfax VA 22031-1303 USA 703-385-0273 Artificial language Loglan/Lojban: http://www.lojban.org To unsubscribe, send mail to lojban-unsubscribe@onelist.com Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/