Received: from mail-qc0-f189.google.com ([209.85.216.189]:56070) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T6Xvq-0007GG-6v; Tue, 28 Aug 2012 19:23:11 -0700 Received: by qcac11 with SMTP id c11sf43659qca.16 for ; Tue, 28 Aug 2012 19:22:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :x-ymail-osg:x-mailer:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=c8nD7IYRPrs9xubSuzb4HOQZkfHuFCZRd9isltP6aPM=; b=CrlhrwiiaH03ICmb8DZJLwmjur//QjNwdzs84+y2iaYdS/02z3ITuMvOb34qDgqvqU 1QcNOV7Bzhrxhd3ZT8jNJ4IuC07ab5qUa9TjN9SzAWw/VnMJ9eQL/hgv2SAOmxZiRds8 39g/V3kGh13v13ZRa2wqTxOyOYg9fcEumrsGNvJXHLMM7HLxUbCvMgMYNTmj5RK/oR/z 56uHVtbgVHBVhv7f6Eyoo73tnap8ZcIr5aqvd+TZT6liQQcFGL2Wc8fnvrNHJfNvlGI5 mXMMOYSozboWLDNh6VEv7gWDERrEUA3ItibPeLgWmkNG+yoGsVyJPQ9CHfoqvHnJYzcJ RZzA== Received: by 10.50.183.200 with SMTP id eo8mr34649igc.6.1346206973145; Tue, 28 Aug 2012 19:22:53 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.231.74.223 with SMTP id v31ls1992875ibj.0.gmail; Tue, 28 Aug 2012 19:22:52 -0700 (PDT) Received: by 10.43.13.137 with SMTP id pm9mr42297icb.0.1346206972143; Tue, 28 Aug 2012 19:22:52 -0700 (PDT) Received: by 10.43.13.137 with SMTP id pm9mr42295icb.0.1346206972110; Tue, 28 Aug 2012 19:22:52 -0700 (PDT) Received: from nm11-vm0.bullet.mail.ac4.yahoo.com (nm11-vm0.bullet.mail.ac4.yahoo.com. [98.139.53.196]) by gmr-mx.google.com with SMTP id xd1si146861igb.1.2012.08.28.19.22.51; Tue, 28 Aug 2012 19:22:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.139.53.196 as permitted sender) client-ip=98.139.53.196; Received: from [98.139.52.196] by nm11.bullet.mail.ac4.yahoo.com with NNFMP; 29 Aug 2012 02:22:51 -0000 Received: from [66.94.237.123] by tm9.bullet.mail.ac4.yahoo.com with NNFMP; 29 Aug 2012 02:22:51 -0000 Received: from [127.0.0.1] by omp1028.access.mail.mud.yahoo.com with NNFMP; 29 Aug 2012 02:22:51 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 388979.46951.bm@omp1028.access.mail.mud.yahoo.com Received: (qmail 13596 invoked by uid 60001); 29 Aug 2012 02:22:50 -0000 X-YMail-OSG: uiJ991IVM1nm9xkLcOfHu5XgkGW2wcV_4WY6WurFMryw3Dm Bd.2VDtSB6DU.r31F.o4tqdxYSjQufbfCy6lT_ljM_nvbGMgc12k4MBjaRdf HSFgepHbb4tXTPCf7FAJubzPmeFnKSv2p0.Ff5xLQP3uv4O9KDXdvpV8DlIe 2LNnsvV6Lv5Lz1i1Xobne6yLZsZaD7eK9viVUL6jMfj.nzNWYfauaSLSfXkY 1C5Fgl.1u_1yIkhsOl0JpaHQsrAhrkrR6IvYRsEijiOGYkO7U1IC0bZxJOcV vxC50.hiRKUtDWwMPlkZnBgNyfxFBCzCso2ukfoX0wDEk4bpXWlqocW2mPDE xm00UHHdmQci01PEVXmBsgpN6BT7CPwQHaqIXNdU_wWDpXPArSIDlBg4TwyP proEVNMqYwCembkXI5daDdNIsQ3snwnZ83e2xPybtanLpfTNXSbPdELyoPnP CMrYSvaM6p_scUEjKUBQ1Usl7RnBDjhJpwG2fVf.Am2Ts5HOYHeROlBOjwgr c3WMuX7CuNSISQW6V7NlyKlKbWERuUmRy1D_IV1U7sRcn7ZghGycjhWpTw8v tYO9LgPOm1wZRK2slNV9aLppyfYUXqlUDuTPo_Y1RJMgzaQ-- Received: from [99.92.108.194] by web184401.mail.bf1.yahoo.com via HTTP; Tue, 28 Aug 2012 19:22:50 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <44e6fb5c-91f3-47ba-817c-8560c9c6ca14@googlegroups.com> <502B9E61.8060808@gmx.de> <502BA634.3030007@gmx.de> <502C50EB.3090704@gmail.com> <7e604d79-8ecd-4690-bc39-bf48b601d46f@googlegroups.com> <5036D423.5050101@gmail.com> <5038CEC3.4050708@gmail.com> <5039204B.1060401@gmail.com> <325f818f-76ce-4f3c-b0c0-03dc4db2e9d8@googlegroups.com> <503B8ED4.200@gmail.com> <9019D4E1-8993-4AF4-BD70-AC76E5A9620F@yahoo.com> <1346161778.18681.YahooMailNeo@web184406.mail.bf1.yahoo.com> <503D5119.9020702@gmx.de> Message-ID: <1346206970.13338.YahooMailNeo@web184401.mail.bf1.yahoo.com> Date: Tue, 28 Aug 2012 19:22:50 -0700 (PDT) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] "Any" and {ro} To: "lojban@googlegroups.com" In-Reply-To: <503D5119.9020702@gmx.de> 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 98.139.53.196 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.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="1009959307-452541414-1346206970=:13338" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --1009959307-452541414-1346206970=:13338 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am sorry to see {le} and {lo} here again, since I thought we got through = those many years ago.=A0 I am old school enough to still think that {le pli= se} refers to some thing(s) that I have specified to myself and hope you wi= ll understand and that I am calling apples to help you get the right thing(= s), whether they really are apples or not.=A0 {lo plise} refers to apples, = but which ones is left up to context, etc. etc.; I haven't anything specifi= c in mind and maybe don't even care.=A0 xorlo has clarified this in various= ways, but does not -- to me -- seem to have changed the basic character.= =A0 As a consequence, I dislike expressions like {ci lo plise} since they s= eem to me to be partitive on a given (how ever indefinitely) bunch of apple= s.=A0 To be sure, in this case, the bunch is given: the ones in the basket.= =A0 But the expression is still discommoding.=A0 Since we are on about "any= " officially, it seems best to stick, as much as possible, to quantified variables, where "any" mainly is.=A0 Unfortunately, some of the examples a= sked about did not lend themselves to that sort of translation -- the ones = requiring specifics, which quantifiers cannot generally give.=A0 {da poi pl= ise} is just about as inspecific (and indefinite) as possible, while still = sticking to apples. {lo plise} moves from that somewhat, if only pragmatica= lly.=A0 {le plise} moves to very specific, but leaves apples behind, in pri= nciple, though rarely in practice. I suppose that {ci lo ro da poi plise} is somehow grammatical, though I can= 't quite work it out.=A0 It seems to amount to just {ci lo ro plise}, three= of all the apples there are. {ci da plise} says that there are exactly three apples in the universe. {ci= da poi plise zo'u mi citka da}, like {mi citka ci da poi plise}, says I ea= t three apples -- without any comment about how many remain uneaten.=A0=20 ________________________________ From: selpa'i To: lojban@googlegroups.com=20 Sent: Tuesday, August 28, 2012 6:15 PM Subject: Re: [lojban] "Any" and {ro} =20 Am 29.08.2012 00:52, schrieb Jacob Errington: > >=20 >On 28 August 2012 12:39, la gleki wrote: >=20 >OK. Please everyone translate the following sentences. >>1. "I'm gonna eat three apples from that basket" [some specific apples, n= amely the red one. the yellow one and the green one but I'm too lazy to men= tion it] >>2. "I'm gonna eat any three apples from that basket" >>3. "Give me any three apples from the basket" >>4. "Give me three apples from the basket" [not known whether I need some = specific apples or not] >> >> > > >gleki, =A0Lojban doesn't really distinguish this. What real information is= being conveyed that is so important by that addition of "any"?=A0 >There are n apples in the basket. You tell someone you're going to eat thr= ee. They expect that at some time in the future, after you've eaten them, t= hat there will be n-3 apples. That's it. If the listener *cares* about whic= h apples you're planning on eating, they'll *ask*. The distinction is unnec= essary, as evidenced in selpa'i's reply, i.e. the one you thought was a jok= e. > > >.i mi citka ci lo plise >I'm going to eat three apples.=A0 > > >Whether those apples are specific or not isn't really important, and thus = isn't specified.=20 But this doesn't say which three apples you are going to eat, and it does so explicitly. The outer quantifier gives you unspecific referents. =20 This is a lot like tense, in Lojban. Specifying tense can become superfluou= s in the same way that specificity can too. > > >However, I do agree, there are few ways to incorporate specificity into de= termining lojban referent sets. In my opinion, {lo} is unspecific as to spe= cificity, which makes it the all-purpose article. I personally dislike {le}= , but I don't think that it should disappear because it does form the only = way to really be specific. {lo} can be as specific as {le}, but {le} should= always be specific. In that sense, {le} just represents a special case of = {lo}, namely when the referents are desired to be marked as explicitly spec= ific. > > >{.i mi citka ci le plise pe lo lanka} >I'm going to eat three specific apples from the basket. Same problem as before, the apples are not specific, because you used an outer quantifier. This sentence would mean "I will eat three of the apples I have in mind", which helps you very little.=20 =20 {.i mi citka ci lo plise pe lo lanka} >I'm going to eat three apples, maybe particular ones, maybe random ones, f= rom the basket. Again, the three apples are explicitly unspecific. Any three apples you eat will make this true. =20 {.i mi citka ci lo ro da poi plise gi'e se lanka ta >I'm going to eat three unspecific apples from that basket. Okay. The problem is that even though you call it "specific" in the gloss, the listener has no idea what referents you have in mind. "le" doesn't help you at all to convey to the listener which apples you want. The only way to do that is to either point at them, or describe them otherwise, for instance, you could say "lo plise poi zunle traji" or something, which is much more specific than "le plise pe lo lanka". =20 I elected to use {ci lo ro da poi broda} because simple {.i ci da poi plise= gi'e se lanka ta zo'u mi citka da} says that there are exactly three thing= s in the universe that are apples and are in the basket, and that I'm going= to eat all three of them. It says there are three things that are apples and are in the basket that you will eat, which is true with or without prenex. mu'o mi'e la selpa'i =20 --=20 pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo ^:i \jl= /flr sen |ziu \su xn go kror ^:i \sym tfn /zu viw \xn jy ^jaiw --=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. --=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. --1009959307-452541414-1346206970=:13338 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I am sorry to see {le= } and {lo} here again, since I thought we got through those many years ago.=   I am old school enough to still think that {le plise} refers to some= thing(s) that I have specified to myself and hope you will understand and = that I am calling apples to help you get the right thing(s), whether they r= eally are apples or not.  {lo plise} refers to apples, but which ones = is left up to context, etc. etc.; I haven't anything specific in mind and m= aybe don't even care.  xorlo has clarified this in various ways, but d= oes not -- to me -- seem to have changed the basic character.  As a co= nsequence, I dislike expressions like {ci lo plise} since they seem to me t= o be partitive on a given (how ever indefinitely) bunch of apples.  To= be sure, in this case, the bunch is given: the ones in the basket.  But the expression is still discommoding.  Since we are= on about "any" officially, it seems best to stick, as much as possible, to= quantified variables, where "any" mainly is.  Unfortunately, some of = the examples asked about did not lend themselves to that sort of translatio= n -- the ones requiring specifics, which quantifiers cannot generally give.=   {da poi plise} is just about as inspecific (and indefinite) as possi= ble, while still sticking to apples. {lo plise} moves from that somewhat, i= f only pragmatically.  {le plise} moves to very specific, but leaves a= pples behind, in principle, though rarely in practice.

I suppose tha= t {ci lo ro da poi plise} is somehow grammatical, though I can't quite work= it out.  It seems to amount to just {ci lo ro plise}, three of all th= e apples there are.
{ci da plise} says that there are exactly three appl= es in the universe. {ci da poi plise zo'u mi citka da}, like {mi citka ci da poi plise}, says I eat three apples -- without any comment abo= ut how many remain uneaten. 


=

From:<= /b> selpa'i <seladwa@gmx.de>
Sent: Tuesday, August 28, 2012 6:15 PM
Subject: Re: [lojban] "Any" and {ro}

=20 =20 =20
Am 29.08.2012 00:52, sch= rieb Jacob Errington:


On 28 August 2012 12:39, l= a gleki <gleki.is.my.name@gmail.com> wrote:
OK. Please everyone translate the following sentences.
1. "I'm gonna eat three apples from that basket" [some specific apples, namely the red one. the yellow one and the green one but I'm too lazy to mention it]
2. "I'm gonna eat any three apples from that basket"
3. "Give me any three apples from the basket"
4. "Give me three apples from the basket" [not known whether I need some specific apples or not]


gleki,  Lojban doesn't really distinguish this. What real information is being conveyed that is so important by that addition of "any"? 
There are n apples in the basket. You tell someone you're going to eat three. They expect that at some time in the future, after you've eaten them, that there will be n-3 apples. That's it. If the listener *cares* about which apples you're planning on eating, they'll *ask*. The distinction is unnecessary, as evidenced in selpa'i's reply, i.e. the one you thought was a joke.

.i mi citka ci lo plise
I'm going to eat three apples. 

Whether those apples are specific or not isn't really important, and thus isn't specified.

But this doesn't say which three apples you are going to eat, and it does so explicitly. The outer quantifier gives you unspecific referents.

This is a lot like tense, in Lojban. Specifying tense can become superfluous in the same way that specificity can too.

However, I do agree, there are few ways to incorporate specificity into determining lojban referent sets. In my opinion, {lo} is unspecific as to specificity, which makes it the all-purpose article. I personally dislike {le}, but I don't think that it should disappear because it does form the only way to really be specific. {lo} can be as specific as {le}, but {le} should always be specific. In that sense, {le} just represents a special case of {lo}, namely when the referents are desired to be marked as explicitly specific.=

{.i mi citka ci le plise pe lo lanka}
I'm going to eat three specific apples from the basket.

Same problem as before, the apples are not specific, because you used an outer quantifier. This sentence would mean "I will eat three of the apples I have in mind", which helps you very little.

{.i mi citka ci lo plise pe lo lanka}
I'm going to eat three apples, maybe particular ones, maybe random ones, from the basket.

Again, the three apples are explicitly unspecific. Any three apples you eat will make this true.

{.i mi citka ci lo ro da poi plise gi'e se lanka ta
I'm going to eat three unspecific apples from that basket.

Okay.

The problem is that even though you call it "specific" in the gloss, the listener has no idea what referents you have in mind. "le" doesn't help you at all to convey to the listener which apples you want. The only way to do that is to either point at them, or describe them otherwise, for instance, you could say "lo plise poi zunle traji" or something, which is much more specific than "le plise pe lo lanka".

I elected to use {ci lo ro da poi broda} because simple {.i ci da poi plise gi'e se lanka ta zo'u mi citka da} says that there are exactly three things in the universe that are apples and are in the basket, and that I'm going to eat all three of them.

It says there are three things that are apples and are in the basket that you will eat, which is true with or without prenex.

mu'o mi'e la selpa'i
--=20
pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo

^:i \jl /flr sen |ziu \su xn go kror
^:i \sym tfn /zu viw \xn jy ^jaiw
--
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.


--
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.
--1009959307-452541414-1346206970=:13338--