Received: from mail-ob0-f191.google.com ([209.85.214.191]:35678) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VnWzy-00012q-M5 for lojban-list-archive@lojban.org; Mon, 02 Dec 2013 09:09:45 -0800 Received: by mail-ob0-f191.google.com with SMTP id gq1sf3467118obb.8 for ; Mon, 02 Dec 2013 09:09:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=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:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=sUzBKiot2DAJ06TjyYiisXE4aIsza6QEoI4I4Ayd05k=; b=njthUyT/xEMr16J5Lwbgi8AsafOq3ZZTosIqtiIKeS/504ExK/Amp0nWbswUAmqfl8 SlFG5Vse3cgRZtORwHHyviaRhk7WtCVdtga+Fc6oc2qOu12NDHEZXcRGs8Dh2tvWoxOx i9urLpgu2UntucNchKPgc88/y60qGGcT5jRJS7O4hlYhnRWZqdKBpUJzLL57zKNPelgl YuPJvScWL5V0gTKQf69HlLWHnR+bGzRebUA4KQosoNKuuebMZqN8ZkePbGZJjXJLbp9z PCn6yJcvqB3/9uv70YcCzLdJfgr98Kd//8ARemxiaUc33kUKfSLcR7QXn8plljia/bhV P3sQ== X-Received: by 10.182.96.135 with SMTP id ds7mr555199obb.1.1386004164329; Mon, 02 Dec 2013 09:09:24 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.182.22.77 with SMTP id b13ls1569402obf.36.gmail; Mon, 02 Dec 2013 09:09:23 -0800 (PST) X-Received: by 10.182.158.4 with SMTP id wq4mr22564867obb.18.1386004163935; Mon, 02 Dec 2013 09:09:23 -0800 (PST) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [2607:f8b0:4001:c03::22d]) by gmr-mx.google.com with ESMTPS id l41si6578301yhi.5.2013.12.02.09.09.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 09:09:23 -0800 (PST) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:4001:c03::22d as permitted sender) client-ip=2607:f8b0:4001:c03::22d; Received: by mail-ie0-x22d.google.com with SMTP id to1so21680818ieb.32 for ; Mon, 02 Dec 2013 09:09:23 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.143.10 with SMTP id sa10mr18533915igb.8.1386004163751; Mon, 02 Dec 2013 09:09:23 -0800 (PST) Received: by 10.64.195.97 with HTTP; Mon, 2 Dec 2013 09:09:23 -0800 (PST) In-Reply-To: References: <20131121134132.GU13501@samsa.fritz.box> Date: Mon, 2 Dec 2013 12:09:23 -0500 Message-ID: Subject: Re: [lojban] An Interesting Use for a Rafsi From: Ian Johnson To: lojban@googlegroups.com X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:4001:c03::22d as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: multipart/alternative; boundary=001a1135fe9ad6757104ec903d12 X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --001a1135fe9ad6757104ec903d12 Content-Type: text/plain; charset=ISO-8859-1 > Yay, one more experimental word in the discussion. > > Ilmen even explained it on IRC as lu .i zo na'ei smuni simsa zo na li'u > > To me it seems to be much closer to {to'e} than {na} though.. > Could you explain the problem this proposed word solves and > the difference to {na} and {to'e} (in the best case by example)? > Otherwise I don't get what you are trying to say. > According to what xorxes said in bpfk group {na'e} is the same as {na} but with a different scope. The author of {na'ei} thought otherwise. {na} and {na'ei} differ in that {na} (supposedly, at least in Wave lessons) negates everything to the right of the bridi. na'ei negates only the selbri following it. Tanru aside, {na'ei} exists in FOPL. It makes a predicate which holds true for its arguments iff the original holds false for its arguments. It's in NAhE but is not really all that semantically similar to the other NAhE. It is also essentially the same as a {naku} at the *end* of a bridi. mi'e la latro'a mu'o -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/groups/opt_out. --001a1135fe9ad6757104ec903d12 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Yay= , one more experimental word in the discussion.

Ilmen even explained it on IRC as lu .i zo na'ei smuni simsa zo na = li'u

To me it seems to be much closer to {to'e} than {na} th= ough..
Could you explain the problem this proposed word solves and
the difference to {na} and {to'e} (in the best case by example)?
Oth= erwise I don't get what you are trying to say.
According to what xorxes said in bpfk group {na'e} is= the same as {na} =A0but with a different scope. The author of {na'ei} = thought otherwise.

{na} and {na'ei} differ in that {na} (supposedly, a= t least in Wave lessons) negates everything to the right of the bridi. na&#= 39;ei negates only the selbri following it.

Tanru= aside, {na'ei} exists in FOPL. It makes a predicate which holds true f= or its arguments iff the original holds false for its arguments. It's i= n NAhE but is not really all that semantically similar to the other NAhE. I= t is also essentially the same as a {naku} at the *end* of a bridi.

mi'e la latro'a mu'o

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.
--001a1135fe9ad6757104ec903d12--