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 m0rBrKf-00007EC; Sun, 27 Nov 94 23:40 EET Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 5155; Sun, 27 Nov 94 23:40:42 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 5152; Sun, 27 Nov 1994 23:40:42 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 5550; Sun, 27 Nov 1994 22:37:28 +0100 Date: Sun, 27 Nov 1994 16:43:20 EST Reply-To: jorge@PHYAST.PITT.EDU Sender: Lojban list From: Jorge Llambias Subject: Re: lohe, lehe & ka X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 1544 Lines: 37 la lojbab cusku di'e > ke'a would not work for the proposed marker because it already has an > assigned meaning, and it is easy to envision conflict in that meaning > (unless I am missing something). What happens when the reference is > inside a relative clause and is NOT the relativized pronoun. Same thing that happens when there is one relative clause inside another, we have to resort to subindices. Fortunately, {ke'a} is only rarely needed, and such embedding is even rarer, so the problem wouldn't arise much in practice. The solution (indexing) is a bad one, but it is sufficient for a problem that doesn't seem to appear in practice. > Composing > on the fly something like: > lo nanmu poi ganse leka le rozgu cu se panci > I don't even see a way to use ke'a in the abstraction, and if it did, it would > refer to the man. I don't see what ke'a would mean there either, which makes me wonder why that place needs a property. Does the man sense the smell or the property of the rose having a smell? Is it a property of the rose, that he senses? In any case, there is no confusion in that example, since there is no place to use ke'a. > Most of the gismu that have abstractions seem to be such that the focused > place in the property abstraction is an echo of x1. If you have > a relative clause such that the relativized pronoun is NOT that x1, then > you have a conflict in use of ke'a. The property and the relative clause are at different levels, so it can be disambiguated with subindices, if ever it is needed. Jorge