Received: from mail-pz0-f61.google.com ([209.85.210.61]:62101) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1RRard-0003qy-8y; Fri, 18 Nov 2011 18:41:14 -0800 Received: by pzk33 with SMTP id 33sf2000729pzk.16 for ; Fri, 18 Nov 2011 18:41:03 -0800 (PST) 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 :content-transfer-encoding; bh=IGnDxvP4H0Qa8VOeq/iJrgkZxvHFSMZTLmbw7Fde6nk=; b=qGivGmK2yl6DHaQ1LMvIkNBt87WWkVWJ12FPd/1EOPk9+Eu/t1kozblPxNQFBYzYku Fp0LifaMusIVVy26/Sx44FGaje3jIzCkibrVREfmtuavEL+yPxvTTq6pS43WzXl2/qlY Ek7GfxgvvOJUXWHeQny989Eql2rn3YMTl3YDs= Received: by 10.68.39.74 with SMTP id n10mr1072911pbk.8.1321670460431; Fri, 18 Nov 2011 18:41:00 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.68.3.45 with SMTP id 13ls1572490pbz.4.gmail; Fri, 18 Nov 2011 18:40:59 -0800 (PST) Received: by 10.68.39.100 with SMTP id o4mr4111868pbk.0.1321670459621; Fri, 18 Nov 2011 18:40:59 -0800 (PST) Received: by 10.68.39.100 with SMTP id o4mr4111867pbk.0.1321670459612; Fri, 18 Nov 2011 18:40:59 -0800 (PST) Received: from mail-pz0-f46.google.com (mail-pz0-f46.google.com [209.85.210.46]) by gmr-mx.google.com with ESMTPS id h2si8380935pba.0.2011.11.18.18.40.59 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Nov 2011 18:40:59 -0800 (PST) Received-SPF: pass (google.com: domain of maikxlx@gmail.com designates 209.85.210.46 as permitted sender) client-ip=209.85.210.46; Received: by pzk2 with SMTP id 2so7951155pzk.5 for ; Fri, 18 Nov 2011 18:40:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.4.38 with SMTP id h6mr9797774pbh.5.1321670459400; Fri, 18 Nov 2011 18:40:59 -0800 (PST) Received: by 10.142.224.8 with HTTP; Fri, 18 Nov 2011 18:40:59 -0800 (PST) In-Reply-To: References: <1321501066.64722.YahooMailRC@web81306.mail.mud.yahoo.com> Date: Fri, 18 Nov 2011 21:40:59 -0500 Message-ID: Subject: Re: [lojban] Lions and levels and the like From: maikxlx To: lojban@googlegroups.com X-Original-Sender: maikxlx@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of maikxlx@gmail.com designates 209.85.210.46 as permitted sender) smtp.mail=maikxlx@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 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / 2011/11/18 Jorge Llamb=EDas : > You seemed to think the given definitions made sense... > I think that the given definitions of {ka'e} make some sense from a naturalistic point of view, and that they follow mostly from {kakne}. I am not saying that I think that it should be this way, just that it is. >> Well since you asked, from what I see, I would >> definitely assume the x1, given the glosses, proposed keywords, and >> examples in the CLL and BPFK. =A0In particular the CLL examples indicate >> very clearly that {ka'e} and related CAhA are some sort of short-scope >> selbri modifiers and emphatically _not_ true modal operators with >> scope over the whole bridi. > > But CAhAs are tags, and all other tags are bridi operators. If "ka'e > citka" and "ka'e se citka" have different meanings (besides reordered > places), CAhA works nothing like other tags. > > And I don't know what you would do with "ka'e na broda", or "ka'e ku > na ku broda", given that "na" has bridi scope, and "ka'e" appears to > have scope over "na" in those cases. > If you're saying that CAhA should not stand in for {kakne}, then I agree with you for the reasons you give. But people are going to learn {ka'e} by what they read in the reference materials, and from established usage, not by what the formal grammar's scope rules imply, and the reference materials describe something closer to {kakne} than to {cumki}, and this includes the somewhat muddled BPFK definition. The established usage I cannot speak to due to my limited familiarity with it. But now that Bob LeChevalier weighed in, but I would be astounded if {ka'e} is closer to {cumki} than to {kakne}. >> ci'a =A0=3D "it is possible that; possibly; may/might" (looks vaguely li= ke 'cumki') >> ne'e =3D "it is necessary that; necessarily; must" (looks vaguely like >> 'necessary') > > In my experience, it is usually more effective to work with existing > cmavo and nudge their definitions in the right direction than propose > completely new cmavo. > > mu'o mi'e xorxes > I didn't come here to make unwelcome suggestions, but this is an issue that Lojban should not monkey around with. Modal-logical operators are both extremely useful in ordinary conversation and are primitive in logic. They are essential in Montague's program and will be needed by Martin Bays or anyone else who is going to take a crack at a model-theoretical formalization. At the minimum I urge the admission of {ne'e}, which would be very useful in its own right and would fill a major gap in Lojban (with an added benefit that its uncontaminated counterpart can be gotten from {naku ne'eku naku} if desired). I highly doubt that there will ever arise a better reason to assign an unassigned CV'V cmavo . Just my 2 cents. --=20 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@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.