Received: from mail-pa0-f61.google.com ([209.85.220.61]:39255)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <bpfk-list+bncBCRZPH6MCMIK7XX3QUCRUBGVDHEPK@googlegroups.com>)
	id 1Tg8qU-0007O6-4u; Tue, 04 Dec 2012 22:52:47 -0800
Received: by mail-pa0-f61.google.com with SMTP id bg2sf3757115pad.16
        for <multiple recipients>; Tue, 04 Dec 2012 22:52:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20120806;
        h=x-beenthere:date:from:to:message-id:subject:mime-version
         :x-original-sender: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=KLNU6ILCujNZQxeS+X4KxVCfPmHRWbaWJqinoPAngpU=;
        b=PppMWO+J+BsHjTig4EoC7TkH65fDjw5IpyEMIvxpuhL5m741t/X0hBx4VKUfAwP+n/
         uAANkfKO2JXK5tTFfImlqmmmzB4nJrHEdxxeEPQ/UUCGbqcAhqJOeEzAXWl5Lr1EydXb
         pzlfWqjFLbRf8MGXJtLL+Kt00yrlRlciL3Eq2mrik/vCYZ4+yq5vu16NjK2BmlswkM9T
         7EtYFrylJSKpgVVySfsMJ6Mcm71vaCnna5zpWIj7FDV9P+DiFD6yK49OzTouWrRGwXPw
         hXlEVbHmqHESDCs3lrWxZdH5JrrE238hK5YgIfw1AR4c3hU/1iG4ItlfpdB+VGsIlpV9
         2mDQ==
Received: by 10.50.169.103 with SMTP id ad7mr330271igc.2.1354690351722;
        Tue, 04 Dec 2012 22:52:31 -0800 (PST)
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.50.104.199 with SMTP id gg7ls1136553igb.34.canary; Tue, 04 Dec
 2012 22:52:31 -0800 (PST)
Received: by 10.50.207.74 with SMTP id lu10mr170781igc.11.1354690351364;
        Tue, 04 Dec 2012 22:52:31 -0800 (PST)
Date: Tue, 4 Dec 2012 22:52:30 -0800 (PST)
From: la gleki <gleki.is.my.name@gmail.com>
To: bpfk-list@googlegroups.com
Message-Id: <95cdbee4-7ddc-4f7d-bb48-4591b7c3d915@googlegroups.com>
Subject: [bpfk] polysemy of {nai}
MIME-Version: 1.0
X-Original-Sender: gleki.is.my.name@gmail.com
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
List-ID: <bpfk-list.googlegroups.com>
X-Google-Group-Id: 972099695765
List-Post: <http://groups.google.com/group/bpfk-list/post?hl=en_US>, <mailto:bpfk-list@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:bpfk-list+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/bpfk-list?hl=en_US>
Sender: bpfk-list@googlegroups.com
List-Subscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>,
 <mailto:googlegroups-manage+972099695765+unsubscribe@googlegroups.com>
Content-Type: multipart/alternative; 
	boundary="----=_Part_652_445201.1354690350697"
X-Spam-Score: 0.0 (/)
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /
Content-Length: 2782

------=_Part_652_445201.1354690350697
Content-Type: text/plain; charset=ISO-8859-1

Even the current grammar has two meanings of {nai}.
Such "polysemy" (although lacking ambiguity in any case) might lead to 
inconvenience for newbies.
Why {nai} actually means
1. to'e (UInai)
2. na (NU NAI = NU NA KU ZOhU, the same with connectives and BAI)?

The proposal http://www.lojban.org/tiki/Move+NAI+to+CAI adds the third 
meaning (na'e).

Next question is why {nai} should move to CAI and then to UI when UI have 
no truth value?
It puts {nai} into strange relation with {na'i} that is already in UI.

If so why having {to'e}, {no'e} and {na'e} and if they can be always 
optionally replaced with {nai}, {cu'i} and some experimental cmavo (e.g. 
{ne'e}) correspondingly?

-- 
You received this message because you are subscribed to the Google Groups "BPFK" group.
To view this discussion on the web visit https://groups.google.com/d/msg/bpfk-list/-/YD3qRWa0J68J.
To post to this group, send email to bpfk-list@googlegroups.com.
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.


------=_Part_652_445201.1354690350697
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Even the current grammar has two meanings of {nai}.<div>Such "polysemy" (al=
though lacking ambiguity in any case) might lead to inconvenience for newbi=
es.</div><div>Why {nai} actually means</div><div>1. to'e (UInai)</div><div>=
2. na (NU NAI =3D&nbsp;NU NA KU ZOhU,&nbsp;the same with connectives and BA=
I)?</div><div><br></div><div>The proposal&nbsp;http://www.lojban.org/tiki/M=
ove+NAI+to+CAI adds the third meaning (na'e).</div><div><br></div><div>Next=
 question is why {nai} should move to CAI and then to UI when UI have no tr=
uth value?</div><div>It puts {nai} into strange relation with {na'i} that i=
s already in UI.</div><div><br></div><div>If so why having&nbsp;{to'e}, {no=
'e}&nbsp;and&nbsp;{na'e} and if they can be always optionally replaced with=
 {nai}, {cu'i} and some experimental cmavo (e.g. {ne'e}) correspondingly?</=
div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups "=
BPFK" group.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/bpfk-list/-/YD3qRWa0J68J">https://groups.google.com/d/msg/bpfk-lis=
t/-/YD3qRWa0J68J</a>.<br />=20
To post to this group, send email to bpfk-list@googlegroups.com.<br />
To unsubscribe from this group, send email to bpfk-list+unsubscribe@googleg=
roups.com.<br />

For more options, visit this group at http://groups.google.com/group/bpfk-l=
ist?hl=3Den.<br />



------=_Part_652_445201.1354690350697--