From arosta@uclan.ac.uk Wed Oct 31 08:59:03 2001 Return-Path: X-Sender: arosta@uclan.ac.uk X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_0_0_1); 31 Oct 2001 16:59:03 -0000 Received: (qmail 94908 invoked from network); 31 Oct 2001 16:58:49 -0000 Received: from unknown (10.1.10.142) by 10.1.1.221 with QMQP; 31 Oct 2001 16:58:49 -0000 Received: from unknown (HELO com1.uclan.ac.uk) (193.61.255.3) by mta3 with SMTP; 31 Oct 2001 16:58:49 -0000 Received: from gwise-gw1.uclan.ac.uk by com1.uclan.ac.uk with SMTP (Mailer); Wed, 31 Oct 2001 16:35:22 +0000 Received: from DI1-Message_Server by gwise-gw1.uclan.ac.uk with Novell_GroupWise; Wed, 31 Oct 2001 17:09:55 +0000 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Wed, 31 Oct 2001 17:09:42 +0000 To: lojban Subject: Re: [lojban] a construal of lo'e & le'e Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline From: And Rosta X-Yahoo-Profile: andjamin X-Yahoo-Message-Num: 11812 >>> 10/30/01 07:06pm >>> #arosta@uclan.ac.uk writes: #> Because the first {da} =3D {su'o da}, and (pace pc) the quantifier goes = to=20 #> the prenex of the bridi it occurs in . The su'o can only bind variables= =20 #> within #> its scope (=3D elements following it in the bridi it occurs in), so it c= annot=20 #> bind variables in following sentences. #>=20 #> If {ije} does indeed allow binding to cross sentence boundaries, then th= is #> would require some special rule to get the su'o to have scope over the #> je. On reflection, I think the default position is that absent any such= =20 #> special # #As I have noted before, there is an ambiguity is "sentence" as applied to= =20 #Lojban and And is here taking one very narrow -- and generally disastrous = --=20 #version (it makes it ahrd to make generalizations for example). And also= =20 #complicates this by a peculiar rule (which he says everyone uses though=20 #everyone else seems to violate it regulalry) about where quantifiers reall= y=20 #go. Ignore him or become unable to say very much in normal Lojban.=20 I still think that discussion of this "peculiar rule" had best wait until t= he Elephant, but in the meantime you could see whether you could=20 formulate rules that unambiguously determine quantifier scope for any ... erm ... sentence (replace with better word if you can think of one). That is, rules that could be written up in a textbook and applied to novel sentences, ideally by something as mechanical as a computer.=20 Then, come the Elephant, those rules could serve as a basis for=20 discussion. --And.