Received: from mail-bw0-f61.google.com ([209.85.214.61]:49805) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RKW3t-0000Aw-Nf; Sun, 30 Oct 2011 07:08:39 -0700 Received: by bkat2 with SMTP id t2sf255226bka.16 for ; Sun, 30 Oct 2011 07:08:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=usy7bOpiXbIlCXgOlcH8db9NjQlCl5XSbjCRVSoyDF4=; b=iGTcWcXHjBcz4YIAXNyJrJyX08T3SoZovkYjG0PdywnApx6NA285WHrhnHvCc0zSAL jb3OsWBpVNgHjiaDzBed2Ck6xapL52w0fKp6E/0p/Ur2sxy/zjPovTBI03kGO+mRMgr6 I0YNtu5gjWxYWuzCotBrLcBfX+ct6YUon+xzQ= Received: by 10.204.143.24 with SMTP id s24mr877918bku.35.1319983703449; Sun, 30 Oct 2011 07:08:23 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.205.80.78 with SMTP id zt14ls11864105bkb.1.gmail; Sun, 30 Oct 2011 07:08:22 -0700 (PDT) Received: by 10.204.38.195 with SMTP id c3mr745973bke.8.1319983702009; Sun, 30 Oct 2011 07:08:22 -0700 (PDT) Received: by 10.204.38.195 with SMTP id c3mr745972bke.8.1319983701983; Sun, 30 Oct 2011 07:08:21 -0700 (PDT) Received: from mail-fx0-f42.google.com (mail-fx0-f42.google.com [209.85.161.42]) by gmr-mx.google.com with ESMTPS id i17si4808462fai.0.2011.10.30.07.08.21 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 30 Oct 2011 07:08:21 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.161.42 as permitted sender) client-ip=209.85.161.42; Received: by mail-fx0-f42.google.com with SMTP id r15so5271419faa.29 for ; Sun, 30 Oct 2011 07:08:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.91.73 with SMTP id l9mr17526079fam.22.1319983701835; Sun, 30 Oct 2011 07:08:21 -0700 (PDT) Received: by 10.152.5.165 with HTTP; Sun, 30 Oct 2011 07:08:21 -0700 (PDT) In-Reply-To: <20111030044700.GB32586@gonzales> References: <4EA68224.1080406@gmail.com> <20111026033114.GB3119@gonzales> <4EA7BF06.5050103@gmail.com> <4EAA8AC9.2010000@gmail.com> <20111029001437.GA5535@gonzales> <20111029145956.GB9385@gonzales> <20111029221510.GA32586@gonzales> <20111030044700.GB32586@gonzales> Date: Sun, 30 Oct 2011 11:08:21 -0300 Message-ID: Subject: Re: [lojban] {zo'e} as close-scope existentially quantified plural variable From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 209.85.161.42 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / On Sun, Oct 30, 2011 at 1:47 AM, Martin Bays wrote: > > I suppose the point is that effectively forcing *distributivity* is > possible, in this way. But I don't know what could force > non-distributivity, unless we actually have ambiguous predicates. We do have predicates that are non-commital about distributivity. In "ko'a bevri ko'e", and assuming both ko'a and ko'e have more than one referent each, we don't know (and possibly don't care) how the loads were distributed. If we say "the men carried the tools to the shed" we may not know which of the men carried which of the tools, whether some tool was carried by more than one man, whether some man carried more than one tool, and so on. >> She could have said: ".ei no roi ku su'o da poi cinfo zo'u do klama lo >> jibni be da". > > With that being clearer just because it would be perverse to > existentially quantify over a singleton set, indicating that the > intended domain probably has multiple things which cinfo? Right. > But they could > just as well be multiple kinds of lion rather than individual lions? Yes, but that would still be enough to forbid Moople from getting close to any kind of lion, even if he accepted the existence of kinds for a minute. > I think she ought to be able to be even clearer. She should say "su'o do" and "su'o jibni" for extra safety. >> (I first wrote "ko" instead of "do", but that suggests the scope of >> the imperative is within the scope of "no roi", which seems wrong. > > Hmm... I'd have thought that the imperativeness of {ko}, like the > questioniness of {ma} and perhaps the constancy of {lo}, beats ordinary > quantifiers. Any reason to have it otherwise? It just sounds wrong to me. Fortunately in the case of "ko", I can always replace it with ".ei ... do" and place ".ei" at the right level. >> In any case the moral of the story was that there are sound >> evolutionary reasons for the kind approach, since obviously we are all >> descended from Cless and he is the one that got the right meaning. :) > > Somehow this doesn't seem to be the moral I've taken. Maybe Moople had > a cousin with individuating parents? But what language do they speak? Not English, because in English we can say "lions are dangerous, don't go near them". mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en.