Received: from mail-gh0-f186.google.com ([209.85.160.186]:55456) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TzrUr-0004mp-C9; Mon, 28 Jan 2013 08:24:02 -0800 Received: by mail-gh0-f186.google.com with SMTP id f18sf1760480ghb.13 for ; Mon, 28 Jan 2013 08:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf :x-yahoo-newman-property:x-yahoo-newman-id:x-ymail-osg :x-rocket-mimeinfo:x-mailer:message-id:date:from:reply-to:subject: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=HyX/ZBWdxWUoqepblYpwksK1aBDd5UFjCD+8IHpEIak=; b=ISzhc2hSkTAml6B7CFKJv7Zd1Wc3NksBmJLO0IuCBZ4y4KqrGrA9CxbZPQvt/dF3sT zebOU2eXcdCO7Lb023XCoIqQCKXHaxvy7pIVQ+FhS1CAPC4IcX/FO2EpClnWnZOlkzg4 vB8Hgecf/RSV18Y2KipBkIkdt9T9hS805TMwWtgXrJe5AqAvkTvrrTqr913p0VLXCqUB tJuLE1TBupxUMRC28rmUKrNwy1V+RbovS86NCTO2V4bqbSzX+uNQ3B3LSGdsasVISHyX n9uXTkjMYvUhLjqRfauqn9IeIPul72S9c6ybramz4ltoDcnmtfM4AMRPNCWJBJ7VSE7a a2jQ== X-Received: by 10.49.96.196 with SMTP id du4mr2332726qeb.37.1359390222861; Mon, 28 Jan 2013 08:23:42 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.74.42 with SMTP id q10ls1132831qev.65.gmail; Mon, 28 Jan 2013 08:23:41 -0800 (PST) X-Received: by 10.101.106.24 with SMTP id i24mr1723026anm.18.1359390221250; Mon, 28 Jan 2013 08:23:41 -0800 (PST) X-Received: by 10.101.106.24 with SMTP id i24mr1723025anm.18.1359390221218; Mon, 28 Jan 2013 08:23:41 -0800 (PST) Received: from nm26-vm0.access.bullet.mail.mud.yahoo.com (nm26-vm0.access.bullet.mail.mud.yahoo.com. [66.94.236.225]) by gmr-mx.google.com with ESMTPS id s58si483431yhi.6.2013.01.28.08.23.40 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 28 Jan 2013 08:23:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.236.225 as permitted sender) client-ip=66.94.236.225; Received: from [66.94.237.192] by nm26.access.bullet.mail.mud.yahoo.com with NNFMP; 28 Jan 2013 16:23:40 -0000 Received: from [66.94.237.111] by tm3.access.bullet.mail.mud.yahoo.com with NNFMP; 28 Jan 2013 16:23:40 -0000 Received: from [127.0.0.1] by omp1016.access.mail.mud.yahoo.com with NNFMP; 28 Jan 2013 16:23:40 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 368521.35170.bm@omp1016.access.mail.mud.yahoo.com Received: (qmail 23057 invoked by uid 60001); 28 Jan 2013 16:23:39 -0000 X-YMail-OSG: fcVDHIoVM1lvIpPjPfslcEhHmRSqyZlSBlTP1i.CPyOvo3l cKwktX7j7T5Pq.VN7Jl_fd_RIoI63MKqKi6xuqj41PKhvPok.BbJu8SeJAlW kK_CTHiedX_WPhGA4RIOnB6aDpXrZYt1iz2yQYGTO5j5QfS3c0Fs5Q4exncC hgi2d6BlO3.dcs1XCTaGNLozucjXI44aUnA3cHnJbNu1QeOEbkHwGyeTL6sM 1FE_VGrPa736h0.88ZTJmGIHEU9s6yLgzDMRSJt2NuFBQG9bk2K7l6voRMsv WW0ZsFXv6i45FNk7wK50UoQzrPYs3lFAOELzb_DRYRZNXpdD2qHtA41A_YFO lZoBARRbHI7wWefbXWQYZE_MW1xtqAGnZddY3ryvs83D.xzyiidAWRKYxbtc PLswHo5kaiCDJ5SRnubW2OgLPV6IxZ69efPs.wykfmuxBpXSCz7TDztygay1 MJj_BWkHQqRXnW8MZfZjT4twqlrEpqYbxpU6LijJLvNCv9td0HwhEyCDkI89 KwP_hODlRjwuxLNnHMEWaH3qo0929M8xByIbRSq1iog7GeJ0BQFZXKt5LdMU QzwVeEwjv6ohulakbxrQkTN6XcFr.9f8w1aSVCLMqKDmL.lcCRuS.ktpyruQ zjN34UIT4FFly2UffZ0.t4zB7ZmyPaOxCp_a1nig5Lp99kcrhFYVdt796mID w.bcigk6uxgqBFNbqq3gKo0rFaupgvflpEyahHTej.MH4Ao41BbDb4UqqFLv ywEr9GpguJA4k2ZJ.0FDp_5LCoGu_R_n2Zx_yQAHlvQV.OvZO_RgmbpX9.MX MV443ydZUK.JJlg-- Received: from [99.92.108.194] by web184403.mail.bf1.yahoo.com via HTTP; Mon, 28 Jan 2013 08:23:39 PST X-Rocket-MIMEInfo: 001.001,V2VsbCwgSSB0aGluayB3aGF0IHdlIHNlcmlvdXNseSBuZWVkIGlzIHNvbWUgbG9naWMgbGVzc29ucy7CoCBJIGRvbid0IAp0aGluayB0aGF0IGFsbCB0aGUgcHJvYmxlbXMgaGF2ZSBiZWVuIHNvbHZlZCAoYW5kIGZvciBzb21lIEkgZG9uJ3Qgc2VlIApob3cgdG8gc29sdmUgdGhlbSBpbiBMb2piYW4pLCBidXQgdGhpbmdzIGFyZSBub3QgbmVhcmx5IGFzIG11ZGRsZWQgYXMgCnNvbWUgcGVvcGxlIHBlcnNpc3QgaW4gY2xhaW1pbmcuwqAgdGhhdCBiZWluZyBzYWlkLCBhIG51bWJlciBvZiBleGFtcGxlcyAKd28BMAEBAQE- X-Mailer: YahooMailWebService/0.8.131.499 Message-ID: <1359390219.55415.YahooMailNeo@web184403.mail.bf1.yahoo.com> Date: Mon, 28 Jan 2013 08:23:39 -0800 (PST) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: [lojban] Re: lo and le and ro and any and ol' unca Tom Cobbley 'n' all. (was something about Aesop) To: lojban list 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.225 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="-6906265-22077271-1359390219=:55415" X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / ---6906265-22077271-1359390219=:55415 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Well, I think what we seriously need is some logic lessons.=A0 I don't=20 think that all the problems have been solved (and for some I don't see=20 how to solve them in Lojban), but things are not nearly as muddled as=20 some people persist in claiming.=A0 that being said, a number of examples= =20 would be helpful to make the points already established clear and=20 forceful to all. ________________________________ From: la gleki Subject: On Monday, January 28, 2013 7:24:39 PM UTC+4, clifford wrote: Yes, let's do get this away from Aesop (does anyone remember what the=20 connection was?) and stick to meddlesome quantifiers and operators. >To start.=A0 1) "any" is fairly peculiar to English=A0 (and related langua= ges) but it seems that all its logical roles are related to scope issues,= =20 whether the scope at variance with the quantifier's, conditional or=20 imperative or intensional.=A0 Lojban doesn't do the scopes other than the= =20 propositional ones well (hardly at all), so we are left to context or jury-= rigging: how do we=20 indicate that the "an apple" is best scoped as within, rather than=20 outside the command (and the underlying intensional bit about what would ha= ppen were I to get an apple or were my request to be acted upon positively)= ?=A0 Tossing {tu'a}s around, while justifiable, seems=20 inelegant at best. >2.=A0 Yes, {le} makes purely denotative terms (God, how that phrase brings= =20 back seminars and symposia of old).=A0 It is pragmatically urged that the= =20 predicate involved be somehow connected to the object in the view of the ot= her participants than the speaker but that is not strictly required.=A0 a l= e phrase points to a particular definite (or is it specific?) thing=20 (in the xorlo sense) and just that, so that thing must be in UD, but is=20 otherwise not restricted. >3.=A0 As I have said, the main feature of {lo} is salience.=A0 A lo phrase= =20 refers to the things with the indicated property that currently are of=20 interest -- including bringing them to our attention as one possible=20 way.=A0 What things is quite open to contextual determination: {lo broda}= =20 may, depending on context, refer to the physical mass of all brodas, or=20 the class of them or some subclass or or broda alone or various chunks=20 of one or several brodas taken separately or en masse.=A0 There are=20 various auxiliary devices (not all well-developed) for disambiguating if co= ntext doesn't work. >4 Neither {le} nor {lo} correlate in any regular way to English "the" or= =20 "a", though, because of salience, repeated {lo broda} comes to be "the" reg= ularly.=A0=20 > >5.=A0 But {lo} is always bad for "any" because salience -- or any specifyi= ng factor -- is just what "any" does not have. > My suggestion is that we create a list of many many examples and each lojba= nist is given opportunity to translate them. Otherwise this problem will never be solved. Probably people here don't=20 understand what all those terms like "specific" or =A0"salience" or other= =20 terms. vau zo'onai Yes, seriously =A0i dont remember when i=20 started that thread on "any". Long ago. No solution that has been=20 approved by at least 90% of lojbanists. The same questions and answers arise again and again. We need a huge list of examples. mu'o ________________________________ From: la gleki To: loj...@googlegroups.com=20 Sent: Monday, January 28, 2013 8:04 AM Subject: Re: [lojban] Re: Aesop's "The Wolf and the Crane" =20 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 analogou= s=20 to "a" and "the", for back-referencing, is bad. I'm just not sure how=20 many of you will agree with the CLL. (Also, I can't be bothered to look=20 it up.) > > >{lo} *can* refer to things in context, and have definite=20 referents. It's the *generic* article in the sense that we *don't know*=20 if it's being definite or indefinite. The definite-indefinite=20 distinction seems to slowly be dying in IRC Lojban, which is -- I'd=20 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 sis= ku2 as a=20 property. If we use a simple article plus a selbri, we invoke {zo'e} and so= mewhere, there are definite referents that appear. {.i mi sisku lo=20 plise} has the awful problem of having semi-definite referents=20 (quantifierless {lo} doesn't actually need to for strange xorlo=20 reasons). However, assuming xorlo strangeness doesn't happen, the formal de= finition says we can plug in {zo'e noi ke'a plise} (the formal=20 definition should change, IMVHO, to reflect the fact that {lo} can be=20 quite bullshit-y.) -> {.i mi sisku zo'e noi ke'a plise}. Here's the=20 proof that actual referents appear. {zo'e} has referents. Now, if any=20 apple will do, there *shouldn't* be referents. Now, maybe it's possible=20 to hack our way around this with {da}-magics, but it seems like invoking th= e property that is being searched for is a more succinct solution, as -- an= d here's the important part -- *any* object satisfying that predicate will = work. > > >I haven't really analysed this to a greater degree=20 that might suggest that using properties can most of the time / always=20 work. I think however that exploring this possibility is worthwhile,=20 unless we all get our facts straight about xorlo. (As it is, everyone=20 has their own interpretation. Please don't say otherwise. In fact, I=20 used to think I knew what I was talking about when I said "xorlo", but I re= alise that I don't. I used to think I agreed with certain people=20 about xorlo, but I realise that I don't.) > > >.i mi'e la tsani mu'o > > >P.S.=20 if this is going to degenerate into a full-blown discussion about=20 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}=A0https://groups.google. com/d/topic/lojban/yh8- ChFLanM/dis= cussion Other similar topics: Discussion of {da} https://groups.google.com/ forum/#!topic/lojban/ wtp1pNm= 8Nvc Discussion of {da}=A0https://groups.google. com/forum/#!topic/lojban/R1- Bi= 8p_xmg Quantifier exactness=A0https://groups. google.com/forum/#!topic/ lojban/cJH= KEf8kE3Q --=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. Visit this group at http://groups.google.com/group/lojban?hl=3Den. For more options, visit https://groups.google.com/groups/opt_out. ---6906265-22077271-1359390219=:55415 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Well, I think wh= at we seriously need is some logic lessons.  I don't=20 think that all the problems have been solved (and for some I don't see=20 how to solve them in Lojban), but things are not nearly as muddled as=20 some people persist in claiming.  that being said, a number of example= s=20 would be helpful to make the points already established clear and=20 forceful to all.



From: la gleki <gleki.is.my.name@gmail.com>

Subject:

On Monday, January 28, 2013 7:24:39 PM UTC+4, clifford wrote:
Yes, let's do get this away from Aesop (does anyone remember what the=20 connection was?) and stick to meddlesome quantifiers and operators.<= /div>
2.  Yes, {le} makes purely denotative terms (God, how that phrase brings=20 back seminars and symposia of old).  It is pragmatically urged that th= e=20 predicate involved be somehow connected to the object in the view of the other participants than the speaker but that is not strictly required.&nbs= p; a le phrase points to a particular definite (or is it specific?) thing=20 (in the xorlo sense) and just that, so that thing must be in UD, but is=20 otherwise not restricted.
3.  As I have said, the main feature of {lo} is salience.  A lo phrase=20 refers to the things with the indicated property that currently are of=20 interest -- including bringing them to our attention as one possible=20 way.  What things is quite open to contextual determination: {lo broda= }=20 may, depending on context, refer to the physical mass of all brodas, or=20 the class of them or some subclass or or broda alone or various chunks=20 of one or several brodas taken separately or en masse.  There are=20 various auxiliary devices (not all well-developed) for disambiguating if context doesn't work.
4 Neither {le} nor {lo} correlate in any regular way to English "the" or=20 "a", though, because of salience, repeated {lo broda} comes to be "the" regularly. 
5.  But {lo} is always bad for "any" because sali= ence -- or any specifying factor -- is just what "any" does not have.

My suggestion is th= at we create a list of many many examples and each lojbanist is given oppor= tunity to translate them.
Otherwise this problem will never be solved. Probably people here don't=20 understand what all those terms like "specific" or  "salience" or othe= r=20 terms. vau zo'onai
Yes, seriously  i dont remember when i=20 started that thread on "any". Long ago. No solution that has been=20 approved by at least 90% of lojbanists.
The same questions and an= swers arise again and again.
We need a huge list of examples.
mu'o



From: la glek= i <gleki.is...@gmail.com>
To: loj...@googlegroups.com
Sen= t: Monday, January 28, 2013 8:04 AM
Subject: Re: [lojban] Re: Aesop's "The Wolf and the= Crane"



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=20 to "a" and "the", for back-referencing, is bad. I'm just not sure how=20 many of you will agree with the CLL. (Also, I can't be bothered to look=20 it up.)

{lo} *can* refer to things in context, and have definite=20 referents. It's the *generic* article in the sense that we *don't know*=20 if it's being definite or indefinite. The definite-indefinite=20 distinction seems to slowly be dying in IRC Lojban, which is -- I'd=20 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=20 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=20 plise} has the awful problem of having semi-definite referents=20 (quantifierless {lo} doesn't actually need to for strange xorlo=20 reasons). However, assuming xorlo strangeness doesn't happen, the formal definition says we can plug in {zo'e noi ke'a plise} (the formal=20 definition should change, IMVHO, to reflect the fact that {lo} can be=20 quite bullshit-y.) -> {.i mi sisku zo'e noi ke'a plise}. Here's the=20 proof that actual referents appear. {zo'e} has referents. Now, if any=20 apple will do, there *shouldn't* be referents. Now, maybe it's possible=20 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=20 that might suggest that using properties can most of the time / always=20 work. I think however that exploring this possibility is worthwhile,=20 unless we all get our facts straight about xorlo. (As it is, everyone=20 has their own interpretation. Please don't say otherwise. In fact, I=20 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=20 about xorlo, but I realise that I don't.)

.i mi'e la tsani mu'o

P.S.=20 if this is going to degenerate into a full-blown discussion about=20 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.

Other si= milar topics:

--
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.
 
 
---6906265-22077271-1359390219=:55415--