Received: from ELI.CS.YALE.EDU by NEBULA.SYSTEMSZ.CS.YALE.EDU via SMTP; Sat, 20 Nov 1993 02:32:17 -0500 Received: from YALEVM.YCC.YALE.EDU by eli.CS.YALE.EDU via SMTP; Sat, 20 Nov 1993 02:32:13 -0500 Message-Id: <199311200732.AA13555@eli.CS.YALE.EDU> Received: from CUVMB.CC.COLUMBIA.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2) with BSMTP id 7691; Sat, 20 Nov 93 02:31:52 EST Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 3460; Sat, 20 Nov 93 02:31:05 EDT Date: Sat, 20 Nov 1993 02:30:52 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: TECH: tu'e/tu'u X-To: lojban@cuvmb.cc.columbia.edu To: Erik Rauch Status: RO X-Status: X-From-Space-Date: Fri Nov 19 21:30:52 1993 X-From-Space-Address: @YaleVM.YCC.YALE.EDU:LOJBAN@CUVMB.BITNET John Cowan answering Nick: >> # .i mu'i tu'e >> >> Instead of .imu'ibotu'e... does this parse right? I mean, with the right >> constituent structure? I guess it does, since you used it :) > >Yup. You are explicitly allowed to put either a or a prenex >before a "tu'e...tu'u" structure. Indeed, this structure was the reason for putting tu'e and tu'u in the language. It allows you to do with multi-sentences what you can do with .i+construct to join individual sentences. very useful when you want to, for example, expand a compound sentence into its component parts. In addition, using tenses and mu'i and ni'i you can do things like append explanations, mathematical derivations, and write sequential instructions, where each step might take more than one sentence to write and/or explain. lojbab