Received: from mail-pb0-f59.google.com ([209.85.160.59]:51933) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TzrXk-0004oy-RL; Mon, 28 Jan 2013 08:26:54 -0800 Received: by mail-pb0-f59.google.com with SMTP id wz12sf426039pbc.4 for ; Mon, 28 Jan 2013 08:26: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:date:from:to:cc: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=udoWbuSJBNH9LqCRsLmDmSY9w0YY0NhEEVChd0MR+RA=; b=sK/nPr3N84qfiD/HmF8KiAG1t3BQYG3DN2BXdFHAU5+9NTFdfoRJ0LJWsNepCWjUXf jDzwgzIEn4mZbszbhbsTxhmBnrvM35U2zUo232T5o6AnefBR2wIvPiQ978RjfeHUenE9 gs1Zi1UJFajItJ3l7FaZVzeAJa2p4K12ZnHCpAQTrNpOiRBzeA/B1dZidB2FLe/XPV/t Q1oF5rR/4XzWaUQVrVUpVH+dOXTaCKCr7z2Cm23+jFXCfqK/ZHMSHf0cDZVfa0nhEtvn Bu8yqWBZk5uF2W4oxd0P0zfPxRIPVhDWH/AwpiSqyXsJCQUlJL/YM8VUUW7sZbnEo6C4 UgEg== 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:cc: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=udoWbuSJBNH9LqCRsLmDmSY9w0YY0NhEEVChd0MR+RA=; b=T0EsrI01Srv20C6WliBod2on+0xK/ly7fX0XZtFzJqZOYSf3vU+nCp7qKYNjl2IbxT ZyHFcFbazJn+VnOUR0GDqFuEz/bsdyxqiHYxPRf/uOOa+w/mLDuyylu/yuhlRQmUh0ut Z9eSqG1PIEYz1DoMuBaBMrIoDOpa26dFoBfYt8bllPPkQr0RKr8FnWk/vXKauhNl+3Wz Pvtuv6Y9uyB8FSrSw+1zHRldFh9GQ88rjG10oJcdRjYzMHOnLsdKP88yQguKUuuvtxcL /j4YifRA8diM7ApkLfYI7PXO0iT/k6Emvmfi3pijfi1Kdy3KEEQ7Ds2Lh6gC+TEahrqj 9woA== X-Received: by 10.49.24.14 with SMTP id q14mr2306201qef.17.1359390402468; Mon, 28 Jan 2013 08:26:42 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.24.37 with SMTP id r5ls1107240qef.85.gmail; Mon, 28 Jan 2013 08:26:41 -0800 (PST) X-Received: by 10.49.95.68 with SMTP id di4mr2396740qeb.0.1359390400785; Mon, 28 Jan 2013 08:26:40 -0800 (PST) Date: Mon, 28 Jan 2013 08:26:40 -0800 (PST) From: la gleki To: lojban@googlegroups.com Cc: John E Clifford Message-Id: In-Reply-To: <1359390219.55415.YahooMailNeo@web184403.mail.bf1.yahoo.com> References: <1359390219.55415.YahooMailNeo@web184403.mail.bf1.yahoo.com> Subject: [lojban] Re: lo and le and ro and any and ol' unca Tom Cobbley 'n' all. (was something about Aesop) 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_152_14097010.1359390400480" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_152_14097010.1359390400480 Content-Type: text/plain; charset=ISO-8859-1 On Monday, January 28, 2013 8:23:39 PM UTC+4, clifford wrote: > > Well, I think what we seriously need is some logic lessons. > How do you imagine children born by parents speaking Lojban taking logic lessons? Give examples from real life and you are done. > I don't think that all the problems have been solved (and for some I don't > see how to solve them in Lojban) > Do you know how to solve them somewhere? In xorban/tokipona/Navaho/language of penguins? > , but things are not nearly as muddled as some people persist in > claiming. that being said, a number of examples would be helpful to make > the points already established clear and 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 > connection was?) and stick to meddlesome quantifiers and operators. > To start. 1) "any" is fairly peculiar to English (and related languages) > but it seems that all its logical roles are related to scope issues, > whether the scope at variance with the quantifier's, conditional or > imperative or intensional. Lojban doesn't do the scopes other than the > propositional ones well (hardly at all), so we are left to context or > jury-rigging: how do we indicate that the "an apple" is best scoped as > within, rather than outside the command (and the underlying intensional bit > about what would happen were I to get an apple or were my request to be > acted upon positively)? Tossing {tu'a}s around, while justifiable, seems > inelegant at best. > 2. Yes, {le} makes purely denotative terms (God, how that phrase brings > back seminars and symposia of old). It is pragmatically urged that the > predicate involved be somehow connected to the object in the view of the > other participants than the speaker but that is not strictly required. a > le phrase points to a particular definite (or is it specific?) thing (in > the xorlo sense) and just that, so that thing must be in UD, but is > otherwise not restricted. > 3. As I have said, the main feature of {lo} is salience. A lo phrase > refers to the things with the indicated property that currently are of > interest -- including bringing them to our attention as one possible way. > What things is quite open to contextual determination: {lo broda} may, > depending on context, refer to the physical mass of all brodas, or the > class of them or some subclass or or broda alone or various chunks of one > or several brodas taken separately or en masse. There are 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 > "a", though, because of salience, repeated {lo broda} comes to be "the" > regularly. > 5. But {lo} is always bad for "any" because salience -- or any specifying > factor -- is just what "any" does not have. > > > My suggestion is that we create a list of many many examples and each > lojbanist is given opportunity to translate them. > Otherwise this problem will never be solved. Probably people here don't > understand what all those terms like "specific" or "salience" or other > terms. vau zo'onai > Yes, seriously i dont remember when i started that thread on "any". Long > ago. No solution that has been 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 > *Sent:* 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 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_152_14097010.1359390400480 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Monday, January 28, 2013 8:23:39 PM UTC+4, clifford wrote:
Well, I think what we seriously need is some logic lessons. = ;

How do you imagine chi= ldren born by parents speaking Lojban taking logic lessons?
Give = examples from real life and you are done.

 
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)

<= div>Do you know how to solve them somewhere? In xorban/tokipona/Navaho/lang= uage of penguins?

 
, b= ut 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>
To start.  1) "any" is fairly peculiar to English  (and related lan= guages) 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.  Lojban doesn't do the scopes other than th= e=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 happen were I to get an apple or were my request to be acted upon positively)?  Tossing {tu'a}s around, while justifiable, seems= =20 inelegant at best.
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 salience= -- or any specifying factor -- is just what "any" does not have.

My suggestion is that w= e create a list of many many examples and each lojbanist is given opportuni= ty 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



<= br>

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?


Other si= milar topics:
= Quantifier exactness&nb= sp;https://groups. google.com/forum/#!topi= c/ lojban/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_152_14097010.1359390400480--