From pycyn@aol.com Wed Apr 19 02:01:42 2000 Return-Path: Received: (qmail 10312 invoked from network); 19 Apr 2000 09:01:42 -0000 Received: from unknown (10.1.10.26) by m1.onelist.org with QMQP; 19 Apr 2000 09:01:42 -0000 Received: from unknown (HELO imo25.mx.aol.com) (152.163.225.69) by mta1 with SMTP; 19 Apr 2000 09:01:42 -0000 Received: from Pycyn@aol.com by imo25.mx.aol.com (mail_out_v25.3.) id h.4e.461044a (3927) for ; Wed, 19 Apr 2000 05:01:38 -0400 (EDT) Message-ID: <4e.461044a.262ecff1@aol.com> Date: Wed, 19 Apr 2000 05:01:37 EDT Subject: RECORD: some negation details To: lojban@onelist.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Windows sub 33 X-eGroups-From: Pycyn@aol.com From: pycyn@aol.com nai always negates the immediately preceding word, so no ambiguity follows from je ge'e nai. It may, however, be the wrong thing to say, if it were intended to be from je nai by inserting the UI ge'e. The move is legal, but the preparser takes ge'e nai as a complex UI (nai goes with the immediately preceding word, remember) and blots it out, leaving the je alone, not the je nai. na'e attaches to the immediately following component of a selbri (na'e ke is needed, to attach to the whole selbri, if it is complex). The place structure of na'e broda is the same as that of broda, so na'e and se can be interchanged when not part of a tanru.