From lojban+bncCIywt_XDCRCyx_3tBBoEnHhXwg@googlegroups.com Mon May 02 19:09:04 2011 Received: from mail-gw0-f61.google.com ([74.125.83.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1QH52q-0002gZ-7f; Mon, 02 May 2011 19:09:04 -0700 Received: by gwb11 with SMTP id 11sf11249581gwb.16 for ; Mon, 02 May 2011 19:08:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf :x-yahoo-newman-property:x-yahoo-newman-id:message-id:x-ymail-osg :x-mailer:references:date:from:subject:to:in-reply-to:mime-version :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=j/mWnfg/oYtIDEgNnvNG46aQsZhBX3mLUwyErxql+R0=; b=z4tonhTXoigsZ4MJjkSXNthSjrAipEvqoqvsAchnbfhBlYRyEBstcVui8v4Ow98zvw dly7V738vAMKo9+MtFmkJ3/Jiulp1m0JgJaIFhuDXpL2fTTELKP+W7WvN3UBeSEQqMgW Q/vryNA9VenVv1b8Q7Pj1GG0NzeqW0pzfzaRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :message-id:x-ymail-osg:x-mailer:references:date:from:subject:to :in-reply-to:mime-version: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; b=jgMWdULaugx8odAe/bSgo6BvCmGe+yi5jsdrmVUDhuWGVP1JejaWAxMuXNUXfSi/74 zhATaiuAPBXmHG3QYlpOc05pbpQrLkFCzMhdq3xSl+vTbYEZPm0k+z6dCpZZPl+I+qAH 4jqrvCNIZNp90q1b1JJbh3yzn8Tg0khNLmb2Q= Received: by 10.236.146.98 with SMTP id q62mr91847yhj.53.1304388530161; Mon, 02 May 2011 19:08:50 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.150.101.19 with SMTP id y19ls840ybb.5.gmail; Mon, 02 May 2011 19:08:49 -0700 (PDT) Received: by 10.236.109.17 with SMTP id r17mr479521yhg.2.1304388529449; Mon, 02 May 2011 19:08:49 -0700 (PDT) Received: by 10.236.109.17 with SMTP id r17mr479520yhg.2.1304388529408; Mon, 02 May 2011 19:08:49 -0700 (PDT) Received: from nm15-vm0.access.bullet.mail.mud.yahoo.com (nm15-vm0.access.bullet.mail.mud.yahoo.com [66.94.236.17]) by gmr-mx.google.com with SMTP id h44si1217737yhm.6.2011.05.02.19.08.48; Mon, 02 May 2011 19:08:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.236.17 as permitted sender) client-ip=66.94.236.17; Received: from [66.94.237.196] by nm15.access.bullet.mail.mud.yahoo.com with NNFMP; 03 May 2011 02:08:48 -0000 Received: from [66.94.237.105] by tm7.access.bullet.mail.mud.yahoo.com with NNFMP; 03 May 2011 02:08:48 -0000 Received: from [127.0.0.1] by omp1010.access.mail.mud.yahoo.com with NNFMP; 03 May 2011 02:08:48 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 19453.99244.bm@omp1010.access.mail.mud.yahoo.com Received: (qmail 59792 invoked by uid 60001); 3 May 2011 02:08:47 -0000 Message-ID: <862057.19924.qm@web81301.mail.mud.yahoo.com> X-YMail-OSG: PN5zc5oVM1kLYkucbgOsxf7zBz0P3QnbDwj94DfK2yHjUii 4Tk5SG5dym2hYBoPiUjOMfPdIaaYHsDI1V_GtRX2LkaT5JTWT3byE.RXwGxV fENiNedvrRJSddw.tsXA.PgO1Vm8t8iS_0uqMMHZFRDqnaA4C9sTxsBdRGni vDkQPOuMSxTQ1XGeqKUcCBAKxxhSXfyo4Ga6F7ejfe332mi6noV9cQWDH4E8 _GevfUVAiXd0IOKgNxznPp5ITrGHyhND.7yTG5AEK8RhQdK8RSvwdTehDT3G Fxi52EDFPGdzOu2.4Z0022gsouZ0AVhp11zB5n2QCmn15DPsgJqrz9N5F2d6 q1JO3MtfB1G3vEoMPjWcHfIa6KF2pnCcykBi0ztrmXHnDzs8752wt8RBXIeD CZIiVmTEa90ashg-- Received: from [99.92.108.41] by web81301.mail.mud.yahoo.com via HTTP; Mon, 02 May 2011 19:08:47 PDT X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.110.299900 References: Date: Mon, 2 May 2011 19:08:47 -0700 (PDT) From: John E Clifford Subject: Re: [lojban] xorlo and default quantifiers To: lojban@googlegroups.com In-Reply-To: MIME-Version: 1.0 X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.236.17 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.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="0-1962889444-1304388527=:19924" --0-1962889444-1304388527=:19924 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Well, I'm not sure what negating a predicate means -- putting nal- into its= =20 compound somewhere maybe -- but negating a term doesn't do that. It does= =20 however negate the clause of which the predicate is the core. and that nega= tion=20 can eventually get back to a na before the predicate, through various chang= es=20 involving naku, as have been noted. As noted, {mi citke no plise) is the s= ame=20 as (regularly transformable into and from) {mi na citke su'o plise, all of = which=20 has nought to do with {lo}. Why would you assume that {mi viska zo'e} means {mi viska su'o zo'e}? Does= {mi=20 viska la Djan} really mean {mi viska su'o la Djan}? Yet these are all the = same=20 type of terms and very different from, say, {su'o gerku}. ________________________________ From: Luke Bergen To: lojban@googlegroups.com Sent: Mon, May 2, 2011 6:01:50 PM Subject: Re: [lojban] xorlo and default quantifiers Hmm, I understood your following statement: > No, because "no" contains a negation. If you say "mi citka" you can't > expect people to understand that you mean "mi na citka". Similarly, if > you say "mi citka lo plise" you can't expect anyone to understand that > you mean "mi citka no lo plise". to mean that putting {no sumti} in a bridi effectively negates the selbri s= uch=20 that {mi citka no plise} =3D {mi na citka ??? plise}. =20 And the general point that I was trying to make was that when we say that {= lo}=20 has no default quantifiers what we've done is merely shifted the assumption= of=20 what we're talking about to context. Like you said {lo broda} =3D {zo'e noi ke'a broda}. I understand {zo'e} as= =20 meaning "omitted sumti which you may or may not be able to pick up on from= =20 context". So if I see {mi viska zo'e} I would assume something like {mi vi= ska=20 su'o zo'e}. I certainly wouldn't assume {no} or something exotic (but=20 grammatical) like {ka'o}. If {zo'e} implicitly forces a listener to make s= ome=20 assumptions then so too does {lo} 2011/5/2 Jorge Llamb=EDas On Mon, May 2, 2011 at 1:04 AM, Luke Bergen wrote: >> mmm, good points. I guess what I was getting at is, just because there = are >> no default quantifiers doesn't mean that people are going to use context= to >> assume them. (for example, you assume that {ro lo nanmu cu bevri lo pip= no}) > >No, I don't. If I assumed that each man carried the piano, then I >would conclude that at least one of them carried it too. If I was >forced to assume anything, it would be that none of them carried it by >himself. (But please don't interpret that as saying that I read "lo ci >nanmu cu bevri lo pipno" as "no lo ci nanmu cu bevri lo pipno"! Just >because two things happen to be true does not mean that they are >saying the same thing!) > > >> And also that seems weird. {no} is a number just like {pa}, {re}, {su'o= }, >> or {so'i}. It seems weird that using it as a quantifier of a sumti can >> directly effect the selbri in ways that other numbers can't. > >Every quantifier affects the bridi in ways that other quantifiers >don't, otherwise they would be the same quantifier. > >"no ..." is equivalent to "naku su'o ..." and also equivalent to "ro ... n= aku" > >"no" is not the only quantifier that contains a negation. "me'i", >"su'e" and "da'a" also do. > >"me'i PA ..." is equivalent to "naku su'o PA ...", and "su'e PA ..." >is equivalent to "naku za'u PA ..." > >"da'a PA ..." is equivalent to "PA ... naku" > > >> I understand intuitively why that is the case. But it still feels stran= ge. >> I kind of have to wonder if {mi na citka lo plise} and {mi citka no pli= se} >> really are identical (I know that the meanings of the statements are the >> same, but are the statements themselves the same as each other) > >They are quite different, they have different meanings. I don't >understand why you say that I said that they were identical. > > >mu'o mi'e xorxes > >-- >You received this message because you are subscribed to the Google Groups= =20 >"lojban" group. >To post to this group, send email to lojban@googlegroups.com. >To unsubscribe from this group, send email to=20 >lojban+unsubscribe@googlegroups.com. >For more options, visit this group at=20 >http://groups.google.com/group/lojban?hl=3Den. > > --=20 You received this message because you are subscribed to the Google Groups= =20 "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to=20 lojban+unsubscribe@googlegroups.com. For more options, visit this group at=20 http://groups.google.com/group/lojban?hl=3Den. --=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. --0-1962889444-1304388527=:19924 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Well, I'm not sure what negating a predicate means -- putting = nal- into its compound somewhere maybe -- but negating a term doesn't do th= at.  It does however negate the clause of which the predicate is the c= ore. and that negation can eventually get back to a na before the predicate= , through various changes involving naku, as have been noted.  As note= d, {mi citke no plise) is the same as (regularly transformable into and fro= m) {mi na citke su'o plise, all of which has nought to do with {lo}.
Why= would you assume that {mi viska zo'e} means {mi viska su'o zo'e}?  Do= es {mi viska la Djan} really mean {mi viska su'o la Djan}?  Yet these = are all the same type of terms and very different from, say, {su'o gerku}.<= br>


From: Luke Bergen &= lt;lukeabergen@gmail.com>
To: lojban@googlegroups.com
= Sent: Mon, May 2, 2011 6:01:50 PM
Subject: Re: [lojban] xorlo and default quantifiers

Hmm, I understood your following statement:
> No, because "no" contains a negation. If you say "mi citka= " you can't
> expect people to understand that you mean "mi na citka". Similarly, if=
> you say "mi citka lo plise" you can't expect anyone to understand = that
> you mean "mi citka no lo plise".

to mean = that putting {no sumti} in a bridi effectively negates the selbri such that= {mi citka no plise} =3D {mi na citka ??? plise}.  

And the = general point that I was trying to make was that when we say that {lo} has = no default quantifiers what we've done is merely shifted the assumption of = what we're talking about to context.

Like you= said {lo broda} =3D {zo'e noi ke'a broda}.  I understand {zo'e} as me= aning "omitted sumti which you may or may not be able to pick up on from co= ntext".  So if I see {mi viska zo'e} I would assume something like {mi= viska su'o zo'e}.  I certainly wouldn't assume {no} or something exot= ic (but grammatical) like {ka'o}.  If {zo'e} implicitly forc= es a listener to make some assumptions then so too does {lo}

2011/5/2 Jorge Llamb=EDas <jjllambias@gmail.com>
On Mon, May 2, 2011 at 1:04 AM, Luke Bergen <lukeabergen@gmail.com> wrote:
> mmm, good points.  I guess what I was getting at is, just because= there are
> no default quantifiers doesn't mean that people are going to use conte= xt to
> assume them.  (for example, you assume that {ro lo nanmu cu bevri= lo pipno})

No, I don't. If I assumed that each man carried the piano, then I
would conclude that at least one of them carried it too. If I was
forced to assume anything, it would be that none of them carried it by
himself. (But please don't interpret that as saying that I read "lo ci
nanmu cu bevri lo pipno" as "no lo ci nanmu cu bevri lo pipno"! Just
because two things happen to be true does not mean that they are
saying the same thing!)

> And also that seems weird.  {no} is a number just like {pa}, {re}= , {su'o},
> or {so'i}.  It seems weird that using it as a quantifier of a sum= ti can
> directly effect the selbri in ways that other numbers can't.

Every quantifier affects the bridi in ways that other quantifiers
don't, otherwise they would be the same quantifier.

"no ..." is equivalent to "naku su'o ..." and also equivalent to "ro ... na= ku"

"no" is not the only quantifier that contains a negation. "me'i",
"su'e" and "da'a" also do.

"me'i PA ..." is equivalent to "naku su'o PA ...", and "su'e PA ..."
is equivalent to "naku za'u PA ..."

"da'a PA ..." is equivalent to "PA ... naku"

> I understand intuitively why that is the case.  But it still feel= s strange.
>  I kind of have to wonder if {mi na citka lo plise} and {mi citka= no plise}
> really are identical (I know that the meanings of the statements are t= he
> same, but are the statements themselves the same as each other)

They are quite different, they have different meanings. I don't
understand why you say that I said that they were identical.

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@googlegro= ups.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/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.
--0-1962889444-1304388527=:19924--