From nicholas@uci.edu Mon Aug 20 16:27:36 2001 Return-Path: X-Sender: nicholas@uci.edu X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_3_1); 20 Aug 2001 23:27:35 -0000 Received: (qmail 61325 invoked from network); 20 Aug 2001 23:26:39 -0000 Received: from unknown (10.1.10.26) by l10.egroups.com with QMQP; 20 Aug 2001 23:26:39 -0000 Received: from unknown (HELO e4e.oac.uci.edu) (128.200.222.10) by mta1 with SMTP; 20 Aug 2001 23:26:39 -0000 Received: from localhost (nicholas@localhost) by e4e.oac.uci.edu (8.9.3/8.9.3) with ESMTP id QAA12090; Mon, 20 Aug 2001 16:26:38 -0700 (PDT) X-Authentication-Warning: e4e.oac.uci.edu: nicholas owned process doing -bs Date: Mon, 20 Aug 2001 16:26:38 -0700 (PDT) X-Sender: To: Cc: Nick NICHOLAS Subject: Re: [lojban] Brochure updates Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From: Nick NICHOLAS cu'u la rab.spir. >{nu} is defined as "generalized event abstractor: x1 is >state/process/achievement/activity of [bridi]". Wouldn't "state" encompass >{du'u}? Event != Fact; and State != Fact. Lesson 7 explicitly goes through this. {nu} *was* formerly understood to be generic. That was before {du'u} was invented; and that's why we now have {su'u}. {nu} generalises from {za'i}, {zu'e}, {pu'u}, maybe {li'i}; but not {du'u}. -- == == == == == == == == == == == == == == == == == == == Nick Nicholas, Breathing {le'o ko na rivbi fi'inai palci je tolvri danlu} nicholas@uci.edu -- Miguel Cervantes tr. Jorge LLambias