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 #1) id m0qobZx-00001DC; Sat, 24 Sep 94 21:12 EET DST Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 9650; Sat, 24 Sep 94 21:10:43 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 9647; Sat, 24 Sep 1994 21:10:43 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 8751; Sat, 24 Sep 1994 20:09:29 +0200 Date: Sat, 24 Sep 1994 14:12:34 EDT Reply-To: jorge@PHYAST.PITT.EDU Sender: Lojban list From: Jorge Llambias Subject: Re: TECH: Transparence / Opaqueness X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 752 Lines: 20 And: > > > ko dunda ci plise mi > > > Give me 3 apples! > > But contrast: > I hereby command you to make it true that there are 3 apples that > I'm given > There are three apples such that I hereby command you to give > me them > > The transparent/opque distinction (I suggest, out of my depth) has > to do with scope of quantification with resepect to some 'irrealis' > element of meaning, & a command, even in the form of an imperative, > constitutes an irrealis element. (CF. "Give me a book - any book".) You're right, but then the definition of {ko} can't be "make this sentence, replacing {ko} by {do}, to be true". At least in the presence of {xe'e} the meaning of {ko} would be somewhat different. Jorge