Received: from mail-ve0-f192.google.com ([209.85.128.192]:56868) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TzpKS-00032v-1Z; Mon, 28 Jan 2013 06:05:05 -0800 Received: by mail-ve0-f192.google.com with SMTP id d10sf758330vea.29 for ; Mon, 28 Jan 2013 06:04:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :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=hhTxRlplCTrkjnao97+OuzWTvaQ7yu3Cd34+X5Tl5PQ=; b=pi5KWCO2qkgp8CwG4aBx8gB2X44jZC+WXa28MA0wJHqP/qiWrXEmVUq7NsqbQzHyQg Qyv73CrwPId4mgH098DJoyKLA48+Ku2mWDgli2GNjvXdVYkn+p0489Pe7DwDsVPSNnb1 tNbkPDmPS5DPRRUdAfQNb4RGQahEEfBA6sXaLMwTLPRbCmqn+XlkxkA3xKzFEjTYcajR AQbCVVPQzWt5zZ1Ix5Txyi+YOqHaNtkCabGYNflVP7zVcX+dQZA9S0YjjGlNkvnepEAP tWv7odobSGUBu1vITwB9ZS9trAsSOi0oVzXk5SsLKVHRKqdG9zpFiKVyQT6tN6k1jwNB X1Tw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:date:from:to:message-id :in-reply-to:references:subject:mime-version:x-original-sender :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=hhTxRlplCTrkjnao97+OuzWTvaQ7yu3Cd34+X5Tl5PQ=; b=zFc5NlBaU0UBy+is6S6+fsq59WGno4/8gQYYQ/+6xywGxi7FLq07X+uaf68TaSlpsF Gt/Ts4kVbVhNNkbQ2d1QagK2FrNYO9KqyWGfRxyZE70BADagF/sNwpEqa+rUy5zayjH1 jex4uaowC8xjfxAPkif8ARlWEQqIJPEvJMcCRLbYJCkEWa59RA1sitFFGW6X/jkxMv14 eSn1nI2XPBp8U8rrrKexELNLAzuMFk/oWSfTWGllAwUl3XX0wsgfeVJ2eeQRwHCxy8qQ 0kmIA6Ij7eDvBfNk9XzK54FhZxDKhFoVd3gjAZodoZxL7PBGt2ExBrFLUH31olevqfY/ eomA== X-Received: by 10.49.71.169 with SMTP id w9mr2275720qeu.7.1359381889463; Mon, 28 Jan 2013 06:04:49 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.24.243 with SMTP id x19ls998164qef.7.gmail; Mon, 28 Jan 2013 06:04:48 -0800 (PST) X-Received: by 10.49.72.169 with SMTP id e9mr2302185qev.3.1359381887939; Mon, 28 Jan 2013 06:04:47 -0800 (PST) Date: Mon, 28 Jan 2013 06:04:47 -0800 (PST) From: la gleki To: lojban@googlegroups.com Message-Id: In-Reply-To: References: <1696426.fuu6unn560@caracal> <47fd82fb-126d-41a3-aa58-fca6ab2fdbde@googlegroups.com> <20130128102447.GH20956@samsa.fritz.box> <567c078e-13fa-45c1-b22d-c57a45eed8af@googlegroups.com> <20130128125103.GI20956@samsa.fritz.box> Subject: Re: [lojban] Re: Aesop's "The Wolf and the Crane" MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@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="----=_Part_1274_7083579.1359381887658" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_1274_7083579.1359381887658 Content-Type: text/plain; charset=ISO-8859-1 On Monday, January 28, 2013 5:53:47 PM UTC+4, tsani wrote: > > FWIW, I recall the CLL mentioning that using lo and le in a manner > analogous to "a" and "the", for back-referencing, is bad. I'm just not sure > how many of you will agree with the CLL. (Also, I can't be bothered to look > it up.) > > {lo} *can* refer to things in context, and have definite referents. It's > the *generic* article in the sense that we *don't know* if it's being > definite or indefinite. The definite-indefinite distinction seems to slowly > be dying in IRC Lojban, which is -- I'd wager -- where the majority of > "spoken" Lojban happens. If there is such a thing as conversational Lojban, > it's on IRC. > > As for the "any" discussion, I'm slowly beginning to see the merits of > sisku2 as a property. If we use a simple article plus a selbri, we invoke > {zo'e} and somewhere, there are definite referents that appear. {.i mi > sisku lo plise} has the awful problem of having semi-definite referents > (quantifierless {lo} doesn't actually need to for strange xorlo reasons). > However, assuming xorlo strangeness doesn't happen, the formal definition > says we can plug in {zo'e noi ke'a plise} (the formal definition should > change, IMVHO, to reflect the fact that {lo} can be quite bullshit-y.) -> > {.i mi sisku zo'e noi ke'a plise}. Here's the proof that actual referents > appear. {zo'e} has referents. Now, if any apple will do, there *shouldn't* > be referents. Now, maybe it's possible to hack our way around this with > {da}-magics, but it seems like invoking the property that is being searched > for is a more succinct solution, as -- and here's the important part -- > *any* object satisfying that predicate will work. > > I haven't really analysed this to a greater degree that might suggest that > using properties can most of the time / always work. I think however that > exploring this possibility is worthwhile, unless we all get our facts > straight about xorlo. (As it is, everyone has their own interpretation. > Please don't say otherwise. In fact, I used to think I knew what I was > talking about when I said "xorlo", but I realise that I don't. I used to > think I agreed with certain people about xorlo, but I realise that I don't.) > > .i mi'e la tsani mu'o > > P.S. if this is going to degenerate into a full-blown discussion about > articles and scopes and everything awful in the world, shouldn't we make a > new topic? > *Yes, let's close the topic and continue where we left last time. * "Any" and {ro} https://groups.google.com/d/topic/lojban/yh8-ChFLanM/discussion *Other similar topics:* Discussion of {da} https://groups.google.com/forum/#!topic/lojban/wtp1pNm8Nvc Discussion of {da} https://groups.google.com/forum/#!topic/lojban/R1-Bi8p_xmg Quantifier exactness https://groups.google.com/forum/#!topic/lojban/cJHKEf8kE3Q -- 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. Visit this group at http://groups.google.com/group/lojban?hl=en. For more options, visit https://groups.google.com/groups/opt_out. ------=_Part_1274_7083579.1359381887658 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Monday, January 28, 2013 5:53:47 PM UTC+4, tsani wrote:FWIW, I recall the CLL mentioning that = using lo and le in a manner analogous to "a" and "the", for back-referencin= g, is bad. I'm just not sure how many of you will agree with the CLL. (Also= , I can't be bothered to look it up.)

{lo} *can* refer to things in context, and have definite ref= erents. It's the *generic* article in the sense that we *don't know* if it'= s being definite or indefinite. The definite-indefinite distinction seems t= o slowly be dying in IRC Lojban, which is -- I'd wager -- where the majorit= y of "spoken" Lojban happens. If there is such a thing as conversational Lo= jban, it's on IRC.

As for the "any" discussion, I'm slowly beginning to se= e the merits of sisku2 as a property. If we use a simple article plus a sel= bri, we invoke {zo'e} and somewhere, there are definite referents that appe= ar. {.i mi sisku lo plise} has the awful problem of having semi-definite re= ferents (quantifierless {lo} doesn't actually need to for strange xorlo rea= sons). However, assuming xorlo strangeness doesn't happen, the formal defin= ition says we can plug in {zo'e noi ke'a plise} (the formal definition shou= ld change, IMVHO, to reflect the fact that {lo} can be quite bullshit-y.) -= > {.i mi sisku zo'e noi ke'a plise}. Here's the proof that actual refere= nts appear. {zo'e} has referents. Now, if any apple will do, there *shouldn= 't* be referents. Now, maybe it's possible to hack our way around this with= {da}-magics, but it seems like invoking the property that is being searche= d for is a more succinct solution, as -- and here's the important part -- *= any* object satisfying that predicate will work.

I haven't really analysed this to a greater degree that= might suggest that using properties can most of the time / always work. I = think however that exploring this possibility is worthwhile, unless we all = get our facts straight about xorlo. (As it is, everyone has their own inter= pretation. Please don't say otherwise. In fact, I used to think I knew what= I was talking about when I said "xorlo", but I realise that I don't. I use= d to think I agreed with certain people about xorlo, but I realise that I d= on't.)

.i mi'e la tsani mu'o

P.S. if = this is going to degenerate into a full-blown discussion about articles and= scopes and everything awful in the world, shouldn't we make a new topic?

Yes, let's close the topic and cont= inue where we left last time.
"Any" and {ro} https://group= s.google.com/d/topic/lojban/yh8-ChFLanM/discussion

Other similar topics:
Discussion of {da} https://gr= oups.google.com/forum/#!topic/lojban/wtp1pNm8Nvc
Discussion of {d= a} https://groups.google.com/forum/#!topic/lojban/R1-Bi8p_xmg
Quantifier exactness https://groups.google.com/forum/#!topic/loj= ban/cJHKEf8kE3Q

--
You received this message because you are subscribed to the Google Groups &= quot;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.
Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
------=_Part_1274_7083579.1359381887658--