Received: from mail-qa0-f61.google.com ([209.85.216.61]:33822) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1UqRGC-0006TN-LN for lojban-list-archive@lojban.org; Sat, 22 Jun 2013 10:06:26 -0700 Received: by mail-qa0-f61.google.com with SMTP id u10sf746320qaz.16 for ; Sat, 22 Jun 2013 10:05:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:x-yahoo-newman-property:x-yahoo-newman-id:x-ymail-osg :x-rocket-mimeinfo: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=O9C6qMBVQBAdUUJXTettAjIOovsJbuqzQ4T6Qxt+Ia8=; b=hWaY7Q3rGWXv2jsjNku9vaUuTd2HRWKFvgI9nL0dXNp74hrNU8tALVkxkdgsBAv/qG 7oQBL47eo5yPWvk0ZQHYW0l2UijoietNSfYo9ksh3gfYe0o83bLq1o7izsFMwaGzcsHK fGp8oDYjOi/wIUCCuk5D44zFHYyqIX+ZEuoIHoQTJm7gNksYph+LJIwgymv6q5ECdVfk ZyxdUCOoNX9eLtXRPsTy6a5eV69OSnXc/aZWDdoK45jlzdNWxpK8QiXBaij3435Obc/3 PYg4jH3HSPBnqk3pZLtrRS5KpfLcIEBVKzBqRp8teXYqOiV9/xXNXr1NtkLgIDIkwv/6 RbHw== X-Received: by 10.50.20.162 with SMTP id o2mr168651ige.9.1371920753561; Sat, 22 Jun 2013 10:05:53 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.61.230 with SMTP id t6ls1491149igr.7.canary; Sat, 22 Jun 2013 10:05:53 -0700 (PDT) X-Received: by 10.43.71.78 with SMTP id yj14mr12577487icb.1.1371920753056; Sat, 22 Jun 2013 10:05:53 -0700 (PDT) Received: from nm15.access.bullet.mail.mud.yahoo.com (nm15.access.bullet.mail.mud.yahoo.com. [66.94.237.216]) by gmr-mx.google.com with ESMTPS id b5si230490igx.3.2013.06.22.10.05.52 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 22 Jun 2013 10:05:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.237.216 as permitted sender) client-ip=66.94.237.216; Received: from [66.94.237.196] by nm15.access.bullet.mail.mud.yahoo.com with NNFMP; 22 Jun 2013 17:05:52 -0000 Received: from [66.94.237.113] by tm7.access.bullet.mail.mud.yahoo.com with NNFMP; 22 Jun 2013 17:05:52 -0000 Received: from [127.0.0.1] by omp1018.access.mail.mud.yahoo.com with NNFMP; 22 Jun 2013 17:05:52 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 282645.71224.bm@omp1018.access.mail.mud.yahoo.com Received: (qmail 99656 invoked by uid 60001); 22 Jun 2013 17:05:51 -0000 X-YMail-OSG: N9UBqAIVM1k4Ny5GkLA6vKhMeYGEHfJr1Tyq93cUVclUhLP WJu_L7e7Li.dt_kP.Nz1mwlyIGKhCD3IeV5u8fLOy2rw6BFFOEUmxA25A.C1 WvvNStuWybFTO9sKHbztVwCuBBD7cLAXF48.yb.7cnA_ikXVchcEuMp_.bW7 cbKyHycOFbNKH0X2WTJqUBdDSZlmm8un.a5SOnZmAfJuOzmlrrC41zyqYbIg umPXWTsvrgniASQ6GIbvLrv9zbQrsRsowYZ8xzCaicFziqRGuOqKlt0Lb5K5 6wnxYvXDiZ5Xm0WSXIKbEsRfwTEo5IzXnZ02Rtn7IXVILKAsU9N_ndf46Csd ZO7.cZpbwQUcMYGh7ebyGIV6KaZCa6Z2mXxBnF8EjSZBKQD9hCTo_pywOrYf q4SL4DeCRuN.VCNSp_27eoO7C7qmm6upouvQ0ffBV1BcCDhLuYvXkzeOHos7 EO2.QeJUJLsgmJapfxzpx2dqkE3OlBUe_PO4m7.VrTYUucvqTWjFWZYFX_LD nDgRtZbDVQhgNzsTNK.O05xjuPE7R3tYgJa2yUsBz9nImFbY.v4MbLZbQcRg .nGRnh83fA9NEukP48kIWnEwSRTAHbqGUQisq6OrLJ4dZCSulHNiDIg10oOy 829IUoiaONZzqUcq0EBsZStckZ3YPLP0FD49oz9DuJy1C7_zpfr23n1q1VNp 9HqnTsE3TS6MIBmqbLD2PLbBIHG_UbFbWaBwyoFUtHKOOStBVZmFVvrE9YlQ REA-- Received: from [99.92.108.194] by web184404.mail.bf1.yahoo.com via HTTP; Sat, 22 Jun 2013 10:05:51 PDT X-Rocket-MIMEInfo: 002.001,Tm90IHN1cmUgd2hhdCB7dGFpfSBkb2VzIGhlcmUsIG5vIE5QIGFmdGVyIGl0LiAoSSBwYXNzIG92ZXIge2NpJ29tbGV9LCB5b3UncmUgZW50aXRsZSB0byBtYWtlIHlvdXIgY29tcG91bmRzIG1lYW4gd2hhdGV2ZXIgeW91IHdhbnQgdGhlbSB0by4pClNheWluZyBhbGwge2xvIGdlcmt1fSByZWZlciB0byBEb2cgaXMgYSByZXRyb2dyYWRlIHN0ZXAsIGJhY2sgaW50byB0aGUgSnVyYXNzaWMgbGV2ZWxzIG9mIHRoZSBoaXN0b3J5IG9mIHtsb30gYW5kIHhvcmxvLsKgIEl0IGlzIG9jY2FzaW9uYWxseSB0cnVlLCABMAEBAQE- X-Mailer: YahooMailWebService/0.8.148.554 References: <5d7f238f-ff93-40ab-af24-fc6320d91b23@googlegroups.com> <17821802.qV9RLdx1PL@caracal> <1371908730.25787.YahooMailNeo@web184404.mail.bf1.yahoo.com> <51C5B15F.8070903@gmx.de> Message-ID: <1371920751.98036.YahooMailNeo@web184404.mail.bf1.yahoo.com> Date: Sat, 22 Jun 2013 10:05:51 -0700 (PDT) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] Please, the best explanation of {le} vs. {lo} To: "lojban@googlegroups.com" In-Reply-To: <51C5B15F.8070903@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 66.94.237.216 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass 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="-420974808-2123200223-1371920751=:98036" X-Spam-Score: 0.1 (/) X-Spam_score: 0.1 X-Spam_score_int: 1 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Not sure what {tai} does here, no NP after it. (I pass over {ci'omle}, you're entitle to make your compounds mean whatever you want them to.) Saying all {lo gerku} refer to Dog is a retrograde step, back into the Jurassic levels of the history of {lo} and xorlo. It is occasionally true, but rarely, and -- given enough metaphysical argle-bargle -- always true in a sense, but not one useful to point out in most cases. [...] Content analysis details: (0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kali9putra[at]yahoo.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid ---420974808-2123200223-1371920751=:98036 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Not sure what {tai} does here, no NP after it. (I pass over {ci'omle}, you'= re entitle to make your compounds mean whatever you want them to.) Saying all {lo gerku} refer to Dog is a retrograde step, back into the Jura= ssic levels of the history of {lo} and xorlo.=A0 It is occasionally true, b= ut rarely, and -- given enough metaphysical argle-bargle -- always true in = a sense, but not one useful to point out in most cases. ________________________________ From: selpa'i To: lojban@googlegroups.com=20 Sent: Saturday, June 22, 2013 9:14 AM Subject: Re: [lojban] Please, the best explanation of {le} vs. {lo} =20 la .pycyn. cu cusku di'e > This seems essentially backward prractice to me.=A0 {lo karce} refers to > the salient car(s).=A0 After it has been used o9nce, that forces the > car(s) there referred to to be the salient ones. It doesn't have to, however. Consider: =A0=A0=A0 "I just saw a dog. Dogs are so cute!" =A0=A0=A0 mi pu zi viska lo gerku .i lo gerku cu tai ci'omle Nothing forbids one to use {lo} twice with different referents each time. (= Or one could say that the referent is always the same, it's Dog.) It might not be super obvious in such a case if the second {lo gerku} is th= e same as the one I just saw, but it's nevertheless "legal" to say it like = that. mu'o mi'e la selpa'i =A0=A0=A0=20 -- You received this message because you are subscribed to the Google Group= s "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/groups/opt_out. --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/groups/opt_out. ---420974808-2123200223-1371920751=:98036 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Not sure what {tai} d= oes here, no NP after it. (I pass over {ci'omle}, you're entitle to make yo= ur compounds mean whatever you want them to.)
Saying all {lo gerku} refe= r to Dog is a retrograde step, back into the Jurassic levels of the history= of {lo} and xorlo.  It is occasionally true, but rarely, and -- given= enough metaphysical argle-bargle -- always true in a sense, but not one us= eful to point out in most cases.



From: selpa'i <seladwa@gmx.de>
To: lojban@googlegroups.com
Sent: Saturday, June 22, 2013 9:14 AM
Subject: Re: [lojban] Please, the= best explanation of {le} vs. {lo}

la .pycyn. cu cusku di'e
> This seems essentially backward prractice = to me.  {lo karce} refers to
> the salient car(s).  After i= t has been used o9nce, that forces the
> car(s) there referred to to = be the salient ones.

It doesn't have to, however. Consider:

&= nbsp;   "I just saw a dog. Dogs are so cute!"
  &nbs= p; mi pu zi viska lo gerku .i lo gerku cu tai ci'omle

Nothing forbid= s one to use {lo} twice with different referents each time. (Or one could s= ay that the referent is always the same, it's Dog.)

It might not be = super obvious in such a case if the second {lo gerku} is the same as the on= e I just saw, but it's nevertheless "legal" to say it like that.

mu'= o mi'e la selpa'i

   


-- You received thi= s message because you are subscribed to the Google Groups "lojban" group.To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com<= /a>.
To post to this group, send email to
lojban@googlegroups= .com.
Visit this group at http://groups.google.com/group/lojban.
= For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
---420974808-2123200223-1371920751=:98036--