From a.rosta@dtn.ntl.com Fri Apr 20 08:57:19 2001 Return-Path: X-Sender: a.rosta@dtn.ntl.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_1_2); 20 Apr 2001 15:57:19 -0000 Received: (qmail 5870 invoked from network); 20 Apr 2001 15:57:19 -0000 Received: from unknown (10.1.10.27) by l8.egroups.com with QMQP; 20 Apr 2001 15:57:19 -0000 Received: from unknown (HELO mta05-svc.ntlworld.com) (62.253.162.45) by mta2 with SMTP; 20 Apr 2001 15:57:18 -0000 Received: from andrew ([62.252.12.248]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20010420154819.NVKD283.mta01-svc.ntlworld.com@andrew> for ; Fri, 20 Apr 2001 16:48:19 +0100 To: Subject: RE: [lojban] Q Date: Fri, 20 Apr 2001 16:47:25 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 From: "And Rosta" X-Yahoo-Message-Num: 6718 Jorge: > la and cusku di'e > > > x1 describes x2 > > x1 discusses x2 > > x1 notices similarities among members of x2 > > &c. > > > >-- in all these, x2 could equally well be a nu or a ka or > >a du'u. > > Right, and also there is the typical "x1 likes x2", in which > people are said to like the strangest things. I agree there is > a possible distinction to be made between discussing a proposition > and discussing an event that the proposition describes, but such > cases are really rare. Agreed. > In all of the above examples the most > natural interpretation would put a nu in the x2, and when you > wanted something else you could say {le jufra be le nu ...} and > things like that. I wouldn't agree that du'u should be derived from nu, though others would. > >But yes, the distinction is usually redundant. > > On the other hand, redundancy is not necessarily bad, > sometimes it can be helpful. If you are not sure about the > meaning of some predicate, the fact that a nu or a du'u or a ka > is used in a given place can be a clue as to the meaning > of the predicate. True for the distinction nu vs. du'u/ka, but the distinction du'u vs. ka is primarily motivated (a) so that ce'u can be left implicit & (b) so that one knows to expect a ce'u even if it's deep within the clause. > But sometimes it is a pain. For example, I have seen both > {le nu ... cu krinu le nu ...} and {le du'u ... cu krinu > le du'u ...}. I don't remember seeing a mix of nu in one > of the places and du'u in the other, but I might. I have > no idea which one is right, they both mean the same thing > as far as I can tell. And like that one there are plenty > of others that make me stop and choose when there is no > point in having to choose. I very much agree, tho for the example you give, I'd argue that nu...krinu...nu is much more sensible than du'u...krinu...du'u. But this is something that the dictionary must specify (i.e. whether or not krinu means "x1 being true is the reason for x2 being true"). Needless to say, the let-usage-decide policy invariably results in ambiguity and illogicality. After all, natural languages are the way they are precisely because they have been decided by usage. --And.