From lojban+bncCIywt_XDCRDcmPvtBBoECReMxw@googlegroups.com Mon May 02 08:23:24 2011 Received: from mail-yw0-f61.google.com ([209.85.213.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1QGuxy-0004XD-Gd; Mon, 02 May 2011 08:23:23 -0700 Received: by ywg8 with SMTP id 8sf10622365ywg.16 for ; Mon, 02 May 2011 08:23:12 -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=3El64AzXsd7+1fovofLtUT4sDwASA6GVCLlqUhg+gd8=; b=ZrsxIFkw8+CnC+s8SmJdZ/10g8wwMQsdV48BJhn8yxZVD8b+Xrwgqi7QsI5QgMYt/Y P8Wm/ewQks4HF+34qtcbJQpKZVSEbWiboWkk4PaTQ4bp3hqKN+p9gqxsHhBVzjxMLF/r 6N50CVh6Mq+nLC93rUKvxd1e4U+5HdJVX8akY= 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=PCLyUVfZKAXD7TzKO0Bn60e+a6hIxnEmGGc1KtQQp+q2pRaqOSHDlT9o2Vhjhu1/8l sG7xA5IKQhUdySbXhF377dayZBeALzz44mEP1OMEyRImz1EZtTQF/bxr5PiU799JtKbN 5diKd8kCFBSPJVv6WTKm2ezcNDUi2lnE7xgSI= Received: by 10.151.19.2 with SMTP id w2mr1070107ybi.57.1304349788828; Mon, 02 May 2011 08:23:08 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.151.33.30 with SMTP id l30ls3280529ybj.0.gmail; Mon, 02 May 2011 08:23:08 -0700 (PDT) Received: by 10.236.189.33 with SMTP id b21mr1470428yhn.68.1304349788153; Mon, 02 May 2011 08:23:08 -0700 (PDT) Received: by 10.236.189.33 with SMTP id b21mr1470427yhn.68.1304349788125; Mon, 02 May 2011 08:23:08 -0700 (PDT) Received: from nm18.access.bullet.mail.mud.yahoo.com (nm18.access.bullet.mail.mud.yahoo.com [66.94.237.219]) by gmr-mx.google.com with SMTP id 51si1107787yhl.13.2011.05.02.08.23.07; Mon, 02 May 2011 08:23:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.237.219 as permitted sender) client-ip=66.94.237.219; Received: from [66.94.237.197] by nm18.access.bullet.mail.mud.yahoo.com with NNFMP; 02 May 2011 15:23:07 -0000 Received: from [66.94.237.96] by tm8.access.bullet.mail.mud.yahoo.com with NNFMP; 02 May 2011 15:23:07 -0000 Received: from [127.0.0.1] by omp1001.access.mail.mud.yahoo.com with NNFMP; 02 May 2011 15:23:07 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 778530.32415.bm@omp1001.access.mail.mud.yahoo.com Received: (qmail 40476 invoked by uid 60001); 2 May 2011 15:23:07 -0000 Message-ID: <412353.33616.qm@web81303.mail.mud.yahoo.com> X-YMail-OSG: C75YpVEVM1mSXMHbWY0XzAS4i8quqtX3_qoH1ihvz69OL.h aa1w.1nsXqKBHxsKECK9b8zvdzWIWXfZqfKIbH3D5FmzYR84oMMZQVMaaS.L 4MjT4W1VRbAkw33ofJyoo1Rbrv2QCTnoaKAZCyyZz8ZTp9NdFCvg1iJINzc_ N5MF03OssPkDox6mr6FsJ5Qpu8cXEc3fmQd9WTq6tUeltbq9.AirngQ7wltC 5nz9INg03L1R2bnblVmWFNHnZIc779shFAz4GEbcoyrfffYTmk8pPNYUaDwG ebfe3QrHrkLejyyHYiiWizU4qiyBbyCFqoD3i5I_JESRW4y0pLCLER.bCG52 Lo9RHdHOirN5jYh8ej4ehiFCNuHqF8PnF5gExN1r88hLxMwVpd3WelIwi Received: from [99.92.108.41] by web81303.mail.mud.yahoo.com via HTTP; Mon, 02 May 2011 08:23:07 PDT X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.110.299900 References: Date: Mon, 2 May 2011 08:23:07 -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.237.219 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-1887827373-1304349787=:33616" --0-1887827373-1304349787=:33616 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If you do assume thatt lo nanmu cu bevri lo pipno has an implicit ro in fro= nt,=20 you will misunderstand what it says. no is not a number like the others, being defined by a negation, though it= does=20 represent a digit. used on an argument, it affects the whole proposition (a= s=20 does every quantifier), in this case by putting a negation somewhere in it. Incidentally, whether you take noun phrases as referring to objects or L-se= ts,=20 no is not a permissible internal quantifier. The apple eating examples are not equivalent, since 'lo plise' in one need = not=20 have the same referent as 'plise' in the second. In the second 'plise' ref= ers=20 to all apples (in the domain), in the first 'lo plise' refers to apples whi= ch=20 may be contextually specified (less than all). So the second imples the fi= rst=20 but not conversely. (What do you mean by "are teh statements the same?" ot= her=20 than "do they mean the same thing" -- clearly they are different sentences.= ) ________________________________ From: Luke Bergen To: lojban@googlegroups.com Sent: Sun, May 1, 2011 11:04:56 PM Subject: Re: [lojban] xorlo and default quantifiers mmm, good points. I guess what I was getting at is, just because there are= no=20 default quantifiers doesn't mean that people are going to use context to as= sume=20 them. (for example, you assume that {ro lo nanmu cu bevri lo pipno}) And also that seems weird. {no} is a number just like {pa}, {re}, {su'o}, = or=20 {so'i}. It seems weird that using it as a quantifier of a sumti can direct= ly=20 effect the selbri in ways that other numbers can't. I understand intuitively why that is the case. But it still feels strange.= I=20 kind of have to wonder if {mi na citka lo plise} and {mi citka no plise} re= ally=20 are identical (I know that the meanings of the statements are the same, but= are=20 the statements themselves the same as each other) 2011/5/1 Jorge Llamb=EDas On Sun, May 1, 2011 at 5:08 PM, Luke Bergen wrote: >> So I was thinking about this earlier today and came to a realization. I= f >> xorlo says that there are no default quantifiers for {lo} then wouldn't = {no} >> be a reasonable possibility for the assumed quantifier? > >No, there isn't an assumed quantifier either. > > >> e.g. {mi citka lo plise}. {lo plise} has no outer quantifier (implicit = or >> explicit), but I suspect that most people will pick up from context that= I >> in fact {citka pa lo su'opa plise} or something like it. > >It will depend on the context, but as an isolated sentence I would >translate it as "I eat apples". It doesn't even have to be about any >specific occasion. I suspect that "I eat exactly one of the at least >one apples" is not one of the most common interpretations. > > >> Furthermore, if I >> said {mi nelci lo nu tcidu .i mi ponse lo cukta} I would think that peop= le >> would read that as something like {mi ponse so'o lo so'i cukta} or somet= hing >> like it. > >I would read it as "I like reading. I own books." I don't think I >would read it as "I own several of many books". > > >> So if context can change the assumptions that the tecusku makes about th= e >> secusku, then couldn't one of those assumptions be {no lo cukta} since t= here >> is no proscribed default? > >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". > > >> Either the default quantifiers of {lo} should be {su'o} or it should be >> reasonable to assume that {mi xebni lo nu tcidu .ija'ebo mi ponse lo cuk= ta} >> could be understood as {mi xebni lo nu tcidu .ija'ebo mi ponse no lo cuk= ta}. > >But "lo" has no quantifiers, default or otherwise. Why do you want to >force one on it? > > >> In my mind the latter is an unsafe assumption and I suspect that most >> tecusku would respond with something like {.ue do cusku lo du'u brodado = na >> nelci lo nu tcidu .iku'i do ji'a cusku lo nu do ponse lo cukta .i va'o l= o nu >> broda kei mi sruma lo nu na brode}. Therefore, I argue that even if the >> grammar claims that {lo} has no default quantifiers, people read lojban = with >> the assumption that {lo}'s implicit quantifiers are {su'o}. >> Thoughts? > >I at least don't. > >Here is an example where "su'o" fails: > >lo ci nanmu ca'o bevri lo pipno. >"Three men are carrying a piano." > >It would not occur to me to conclude that at least one of the three >men is carrying a piano, my assumption would be that they are all >three doing it together. > >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-1887827373-1304349787=:33616 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
If you do assume thatt lo nanmu cu bevri lo pipno has an = implicit ro in front, you will misunderstand what it says.
no is not a n= umber  like the others, being defined by a negation, though it does re= present a digit. used on an argument, it affects the whole proposition (as = does every quantifier), in this case by putting a negation somewhere in it.=
Incidentally, whether you take noun phrases as referring to objects or = L-sets, no is not a permissible internal quantifier.
The apple eating ex= amples are not equivalent, since 'lo plise' in one need not have the same r= eferent as 'plise' in the second.  In the second 'plise' refers to all= apples (in the domain), in the first 'lo plise' refers to apples which may= be contextually specified (less than all).  So the second imples the first but not conversely.  (What do you mean by "are teh statemen= ts the same?" other than "do they mean the same thing" -- clearly they are = different sentences.)


From: Luke Bergen <lukeabergen@gmail.com>
To: lojban@googlegroups.com
Sent: Sun, May 1, 2011 11:04:56 PM
Subject: Re: [lojban] xorlo and defau= lt quantifiers

mmm, good points.  I guess what I was getting at is, just because ther= e are no default quantifiers doesn't mean that people are going to use cont= ext to assume them.  (for example, you assume that {ro lo nanmu cu bev= ri lo pipno})

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 quan= tifier of a sumti can directly effect the selbri in ways that other numbers= can't.

I understand intuitively why that is the case.  Bu= t it still feels 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 meani= ngs of the statements are the same, but are the statements themselves the s= ame as each other)

2011/5/1 Jorge Llamb=EDas = <jjllambias@gmail.com>
On Sun, May 1, 2011 at 5:08 PM, Luke Bergen <lukeabergen@gmail.com> wrote:
> So I was thinking about this earlier today and came to a realization. =  If
> xorlo says that there are no default quantifiers for {lo} then wouldn'= t {no}
> be a reasonable possibility for the assumed quantifier?

No, there isn't an assumed quantifier either.

> e.g. {mi citka lo plise}.  {lo plise} has no outer quantifier (im= plicit or
> explicit), but I suspect that most people will pick up from context th= at I
> in fact {citka pa lo su'opa plise} or something like it.

It will depend on the context, but as an isolated sentence I would translate it as "I eat apples". It doesn't even have to be about any
specific occasion. I suspect that "I eat exactly one of the at least
one apples" is not one of the most common interpretations.

> Furthermore, if I
> said {mi nelci lo nu tcidu .i mi ponse lo cukta} I would think that pe= ople
> would read that as something like {mi ponse so'o lo so'i cukta} or som= ething
> like it.

I would read it as "I like reading. I own books." I don't think I
would read it as "I own several of many books".

> So if context can change the assumptions that the tecusku makes about = the
> secusku, then couldn't one of those assumptions be {no lo cukta} since= there
> is no proscribed default?

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".

> Either the default quantifiers of {lo} should be {su'o} or it should b= e
> reasonable to assume that {mi xebni lo nu tcidu .ija'ebo mi ponse lo c= ukta}
> could be understood as {mi xebni lo nu tcidu .ija'ebo mi ponse no lo c= ukta}.

But "lo" has no quantifiers, default or otherwise. Why do you want to=
force one on it?

>  In my mind the latter is an unsafe assumption and I suspect that= most
> tecusku would respond with something like {.ue do cusku lo du'u brodad= o na
> nelci lo nu tcidu .iku'i do ji'a cusku lo nu do ponse lo cukta .i va'o= lo nu
> broda kei mi sruma lo nu na brode}.  Therefore, I argue that even= if the
> grammar claims that {lo} has no default quantifiers, people read lojba= n with
> the assumption that {lo}'s implicit quantifiers are {su'o}.
> Thoughts?

I at least don't.

Here is an example where "su'o" fails:

lo ci nanmu ca'o bevri lo pipno.
"Three men are carrying a piano."

It would not occur to me to conclude that at least one of the three
men is carrying a piano, my assumption would be that they are all
three doing it together.

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-1887827373-1304349787=:33616--