Received: from wnt.dc.lsoft.com ([205.186.43.7]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id QAB01645 for ; Sun, 21 Jan 1996 16:15:10 -0500 Message-Id: <199601212115.QAB01645@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by wnt.dc.lsoft.com (LSMTP for Windows NT v1.0a) with SMTP id 31461BC0 ; 21 Jan 1996 15:43:21 -0500 Date: Sun, 21 Jan 1996 17:27:10 +0000 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: Re: TECH: Nested relative clauses To: lojban@cuvmb.cc.columbia.edu Status: OR X-Mozilla-Status: 0011 Content-Length: 1029 X-From-Space-Date: Mon Jan 22 03:43:38 1996 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU Kolin: > In Lojban we have invariable words, but clearly defined categories: > 'xirma' is a brivla; it can therefore function as a selbri, or a > bridi, or indeed a jufra. It cannot be a sumti - it needs an explicit > converter, normally a gadri. Now my objection to 're xirma' is that a > laivla (quantifier word) is being used as this converter. Clearly it > can be made to work because it has been; but in my view it's a kludge, > in large part because it means 're lo xirma' and that 'lo' is part of > the skeleton of the phrase. (The presence of 'le re xirma' complicates > the issue further) John has made {re xirma} and {re lo xirma} nonequivalent in either one or two ways (they're different with respect to dogbiting behaviour ("2 men bite 3 dogs" - how many dogs?) and possibly with respect to existential import. But anyway, if {re xirma} were equivalent to {re lo xirma}, and deserves your criticism, it would be a very mild offender, since the rule by which it is abbreviated is so straightforward. coo, mie and