Received: from mail-ye0-f189.google.com ([209.85.213.189]:52623) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Th2Wv-0005M8-8x; Fri, 07 Dec 2012 10:20:25 -0800 Received: by mail-ye0-f189.google.com with SMTP id r9sf409234yen.16 for ; Fri, 07 Dec 2012 10:20:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; 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=UE1JY3Mx1ar3RatFVKERcCMMplZqLf2W/6NovQVs4Z4=; b=J+t8pNxLXd/AIbyUrP/TtmGlRiWPHmIccePhv1o0sBpXYGxqNgcoreHD37bf0lb+3j FJxueb0fKDjeUjtYoQCsyC/Os4tc+F+T/ZrWYx5xU3ks1KkHARouT2heKG5x9tIDhc/n 6pboSnU5yp1rWt8mWk5PiWj2f3FKjKG1TYB2VCR/ZBwjtYyWwIbAuwNLe1XKxIGwpE5w DHJXb0yTv148t6InM6vpI7dUGNylhqu04hMq0SzlQMeczL1+hYBvgmWzCCISFIw/ZAn5 CpPA74MO27jDzLqmko/u9CPG0OoDzb+j11TjbnwixPwjxefKNKT/GfnhfYcj0Jum7ruI 8+Iw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; 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=UE1JY3Mx1ar3RatFVKERcCMMplZqLf2W/6NovQVs4Z4=; b=03UPNhdGqMnEBFkYUppBcT7TtHHVgw2bFaFQLFFQW3S19zBKqn/U4MFW3ku/qaPVk6 Dj86B8/ev5x5atEyKMeeMlgdgfW9h24lv2nth00kI6x/oRW5Fk6nzq+n36zvMUduypCD TlTXnuWpem+CDXn1ha87YOwqcqS6Yg3Ejk3+EZ/uHa56H8Qb1EWvUSL13c27S1pwzikt Y2LknV/woiK7cXPf74/JZfgM5aebPhK4OxjmfQHm8wA4oXQvi9iZoVp4AMHPQrJVL3fw +WwLaPV3ZEsxKUfF384t2odUTuzdKPbk8g8P+zQiSejUDWLzk3tDVhyjXBCplE9jt/wm ZokA== Received: by 10.49.95.68 with SMTP id di4mr1385905qeb.0.1354904402085; Fri, 07 Dec 2012 10:20:02 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.98.34 with SMTP id ef2ls2493073qeb.21.gmail; Fri, 07 Dec 2012 10:20:00 -0800 (PST) Received: by 10.58.191.68 with SMTP id gw4mr2005690vec.20.1354904400729; Fri, 07 Dec 2012 10:20:00 -0800 (PST) Received: by 10.58.191.68 with SMTP id gw4mr2005688vec.20.1354904400701; Fri, 07 Dec 2012 10:20:00 -0800 (PST) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by gmr-mx.google.com with ESMTPS id es5si1960045vdb.2.2012.12.07.10.20.00 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Dec 2012 10:20:00 -0800 (PST) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 209.85.212.54 as permitted sender) client-ip=209.85.212.54; Received: by mail-vb0-f54.google.com with SMTP id l1so706003vba.41 for ; Fri, 07 Dec 2012 10:20:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.59.5.229 with SMTP id cp5mr4512661ved.32.1354904400547; Fri, 07 Dec 2012 10:20:00 -0800 (PST) Received: by 10.220.13.197 with HTTP; Fri, 7 Dec 2012 10:20:00 -0800 (PST) In-Reply-To: References: Date: Fri, 7 Dec 2012 13:20:00 -0500 Message-ID: Subject: Re: [lojban] polysemy of {nai} 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 209.85.212.54 as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass 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: multipart/alternative; boundary=047d7b86e4547fceca04d0474355 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --047d7b86e4547fceca04d0474355 Content-Type: text/plain; charset=ISO-8859-1 (I should add that there is no dispute as to what naku means.) mu'o mi'e la latro'a On Fri, Dec 7, 2012 at 1:19 PM, Ian Johnson wrote: > {na'e} is definitely not "in the middle or on the opposite end", it is > just somewhere on the scale that isn't the point being tagged. Note that > the scale needn't even be 1 dimensional, which is one reason why {to'e}, > {no'e} etc. needn't make sense even when {na'e} does. > > {na}, unlike everything else, is taken straightforwardly from logic; there > are no questions about what it means, and it is orthogonal to both {na'i} > and {na'e}. The only possible issue with {na} is the dispute as to how its > scope works. CLL considers selbri-na to be equivalent to bridi-initial > naku; standard idiom seems to consider selbri-na to be equivalent to naku > in the exact position of the na. In situations where any confusion might > arise I prefer to avoid selbri-na for this reason, using explicit naku or > {na'ei} instead. > > mu'o mi'e la latro'a > > > On Fri, Dec 7, 2012 at 4:37 AM, la gleki wrote: > >> Let me see if I understand negators correctly (scheme attached in a file >> to this post). >> >> {na'e} says that we are somewere at another point but on the same scale. >> {no'e} says we are in the middle of the same scale. >> {to'e} says that we are at the opposite point of the same scale. >> {na'i} says that we are outside this scale (i.e. this predicate >> relationship) >> {na}. Here I have a problem. According to what I draw {na} means that we >> are not at this point of this scale and may be even outside this scale. >> So for me {na} is (warning! bad grammar follows) {na'i ja na'e}. >> >> But may be you prove me wrong (I'm not sure myself). >> >> *Anyway, I want all types of negation to fit on the same scheme.* >> Last time when I draw a similar scheme I could completely solve (at least >> for myself) the problem of subjunctives in lojban. >> Now it's time for negation. >> >> >> On Friday, December 7, 2012 12:28:51 AM UTC+4, lojbab wrote: >>> >>> I think this is more appropriate for the main list. >>> >>> la gleki wrote: >>> > 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). >>> >>> There is one "meaning" - a syntactically appropriate afterthought >>> negation of a single word. The semantics of that negation are specific >>> to what is being negated, but generally it is a scalar/contrary negation >>> (cf. na'e) of the specific word being marked. Sometimes the nature of >>> the construct means that a scalar negation is effectively equivalent to >>> a contradictory negation (cf. na) (this is especially the case for >>> logical connectives, by intent). >> >> >> I understand that on boolean scale {na'e=to'e} but what is {na} then? >> >> >>> >>> As a scalar negation, it is NOT the equivalent of to'e when attached to >>> a UI, but rather na'e (generalized rather than extreme contrary >>> negation). >> >> >> na'e is {cu'i ja to'e} (grammar ignored), isn't it? >> >> naicai would be the afterthought "nai"-like equivalent of >>> to'e when attached to UI. That said, sometimes a scalar situation >>> degenerates to the point where to'e and na'e are equivalent in meaning. >> >> >> This is not the case with some UI that have {cu'i} as an appropriate >> point on the scale. >> >>> >>> The separate words exist for those situations when the scale is NOT >>> degenerate. >>> >>> > Next question is why {nai} should move to CAI and then to UI when UI >>> > have no truth value? >>> >>> It shouldn't, and I have no idea why such a thing would be proposed (I >>> haven't read the cited proposal, and personally don't consider any >>> proposals until/unless formally brought before byfy - not that I know >>> what the procedure for doing so would be these days). >>> >> >> One more vite that it shouldn't be done. Therefore, the poll is closed. >> moving to CAI - may be. >> moving to UI - no. >> :) >> >> >>> We specifically considered that when solving the negation problem. Most >>> languages have oversimplified and degenerate forms of negation (probably >>> because logical complexity is "inconvenient for newbies"). TLI Loglan >>> does so. Lojban specifically tried to improve on that situation. >>> >>> > 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? >>> >>> They can't be so replaced, unless some proposal screws up the language >>> in an attempt to oversimplify the negation problem. Having multiple >>> words allows the semantics of each situation to resolve over time with >>> usage evolving the way each word is interpreted. >>> >> >> That's what I'm proposing. Separate words for different meanings. >> >> >>> >>> Note also that nai is afterthought (like UI) while the NAhE family of >>> words are forethought and can be used with larger constructs than a >>> single word. >>> >> >> UI/CAI can be used with larger constructions, don't they? >> >>> >>> lojbab >> >> -- >> You received this message because you are subscribed to the Google Groups >> "lojban" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/lojban/-/3mwxUYZC6TUJ. >> 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. >> > > -- 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. --047d7b86e4547fceca04d0474355 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable (I should add that there is no dispute as to what naku means.)

mu= 9;o mi'e la latro'a

On Fri, Dec 7= , 2012 at 1:19 PM, Ian Johnson <blindbravado@gmail.com>= wrote:
{na'e} is definitely not "in the mi= ddle or on the opposite end", it is just somewhere on the scale that i= sn't the point being tagged. Note that the scale needn't even be 1 = dimensional, which is one reason why {to'e}, {no'e} etc. needn'= t make sense even when {na'e} does.

{na}, unlike everything else, is taken straightforwardly from logic; th= ere are no questions about what it means, and it is orthogonal to both {na&= #39;i} and {na'e}. The only possible issue with {na} is the dispute as = to how its scope works. CLL considers selbri-na to be equivalent to bridi-i= nitial naku; standard idiom seems to consider selbri-na to be equivalent to= naku in the exact position of the na. In situations where any confusion mi= ght arise I prefer to avoid selbri-na for this reason, using explicit naku = or {na'ei} instead.

mu'o mi'e la latro'a


On Fri, Dec 7, 2012 at 4:37 AM, la glek= i <gleki.is.my.name@gmail.com> wrote:
Let me see if I understand negator= s correctly (scheme attached in a file to this post).

{na'e} says that we are somewere at another point but on= the same scale.
{no'e} says we are in the middle of the same scale.=
{to'e} says that we are at the opposite point of the same sc= ale.
{na'i} says that we are outside this scale (i.e. this predicate re= lationship)
{na}. Here I have a problem. According to what I draw= {na} means that we are not at this point of this scale and may be even out= side this scale.
So for me {na} is (warning! bad grammar follows) {na'i ja na'e= }.

But may be you prove me wrong (I'm not sure= myself).

Anyway, I want all types of negation = to fit on the same scheme.
Last time when I draw a similar scheme I could completely solve (at le= ast for myself) the problem of subjunctives in lojban.
Now it'= ;s time for negation.


On Friday, December 7, 2012 12:28:51 AM UTC+4, lojbab wrote:
I think this is more appropriate for the main list.=A0

la gleki wrot= e:=A0
> Even the current grammar has two meanings of {nai}.=A0
>= ; Such "polysemy" (although lacking ambiguity in any case) might = lead to=A0
> inconvenience for newbies.=A0
> Why {nai} actually means=A0
&= gt; 1. to'e (UInai)=A0
> 2. na (NU NAI =3D NU NA KU ZOhU, the sam= e with connectives and BAI)?=A0
>=A0
> The proposal=A0http://ww= w.lojban.org/tiki/Move+NAI+to+CAI=A0adds the third=A0
> meaning (na'e).=A0

There is one "meaning" - a syn= tactically appropriate afterthought=A0
negation of a single word. =A0The= semantics of that negation are specific=A0
to what is being negated, bu= t generally it is a scalar/contrary negation=A0
(cf. na'e) of the specific word being marked. =A0Sometimes the nature o= f=A0
the construct means that a scalar negation is effectively equivalen= t to=A0
a contradictory negation (cf. na) (this is especially the case f= or=A0
logical connectives, by intent).

I understa= nd that on boolean scale {na'e=3Dto'e} =A0but what is {na} then?



As a scalar negation, it is NOT the equivalent of to'e when att= ached to=A0
a UI, but rather na'e (generalized rather than extreme c= ontrary=A0
negation).

na'= ;e is {cu'i ja to'e} (grammar ignored), isn't it?

=A0naicai would be the afterthoug= ht "nai"-like equivalent of=A0
to'e when attached to UI. =A0That said, sometimes a scalar situation=A0=
degenerates to the point where to'e and na'e are equivalent in = meaning.

This is not the case with some UI = that have {cu'i} =A0as an appropriate point on the scale.

=A0 The separate words exist for those situations when= the scale is NOT=A0
degenerate.=A0

> Next question is why {nai} should move to CAI an= d then to UI when UI=A0
> have no truth value?=A0

It shouldn&#= 39;t, and I have no idea why such a thing would be proposed (I=A0
haven&= #39;t read the cited proposal, and personally don't consider any=A0
proposals until/unless formally brought before byfy - not that I know=A0what the procedure for doing so would be these days).=A0
<= div>
One more vite that it shouldn't be done. Therefore, = the poll is closed.
moving to CAI - may be.
moving to UI - no.
:)


We specifically considered that when solving the negation problem. =A0M= ost=A0
languages have oversimplified and degenerate forms of negation (p= robably=A0
because logical complexity is "inconvenient for newbies&= quot;). =A0TLI Loglan=A0
does so. =A0Lojban specifically tried to improve on that situation.=A0
<= br>> If so why having {to'e}, {no'e} and {na'e} and if they = can be always=A0
> optionally replaced with {nai}, {cu'i} and som= e experimental cmavo (e.g.=A0
> {ne'e}) correspondingly?=A0

They can't be so replaced, = unless some proposal screws up the language=A0
in an attempt to oversimp= lify the negation problem. =A0Having multiple=A0
words allows the semant= ics of each situation to resolve over time with=A0
usage evolving the way each word is interpreted.=A0
That's what I'm proposing. Separate words for differen= t meanings.
=A0

Note also that nai is afterthought (like UI) while the NAhE family of= =A0
words are forethought and can be used with larger constructs than a= =A0
single word.=A0

UI/CAI can be us= ed with larger constructions, don't they?=A0

lojbab=A0

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To view this discussion on the web visit https://groups.google.com= /d/msg/lojban/-/3mwxUYZC6TUJ.
=20 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/lojba= n?hl=3Den.


--
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.
--047d7b86e4547fceca04d0474355--