Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET> Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #14) id m0p0mnn-0000PaC; Sat, 20 Nov 93 09:32 EET Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP R1.2.2MX) with BSMTP id 6346; Sat, 20 Nov 93 09:32:30 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 6345; Sat, 20 Nov 1993 09:32:30 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 3245; Sat, 20 Nov 1993 08:31:39 +0100 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: Veijo Vilva Content-Length: 825 Lines: 19 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