Received: from mail-da0-f57.google.com ([209.85.210.57]:38932) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Tzqpn-0004WB-KI; Mon, 28 Jan 2013 07:41:29 -0800 Received: by mail-da0-f57.google.com with SMTP id q27sf1669018daj.12 for ; Mon, 28 Jan 2013 07:41:17 -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=TL1dVEjZUx0vQRwHKOjuHW3Fb4l2DgQqh9k+n2WCMz8=; b=YYvh08at5qguxNzvvpz8tEeMOYwBCeU4DR9Sa8a8CY1qheREqaA8pP1cJAyiCPWAT7 ih5BYME2dlkWoEu2pfsJW9FhIurKODrpgUxf9KGedhi6AUi8jdpQUt3UV3TphpiPTJn1 I3DPPeLmhKwJ/y0GzyPMXOEjDSBuCllEJWxed1ufMC89XoR+RVE4hgf2v1gaMVymJEsg ayV8aw9LOS4FrSgmHPI9OUtTJDe72pC+PRf9ZPi/uF5XCZRSaNF9+JA50WWePuNtCSn8 XAqbnAaOEI1feJVy+ZPoL8LYFltSTRCKMdT1ICt9PmJaOu37uuiz7iEjle/Ip1NRvyM9 A93Q== 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=TL1dVEjZUx0vQRwHKOjuHW3Fb4l2DgQqh9k+n2WCMz8=; b=rdbEK23pKwlDlXaL91W1akGGhr7RfZpGYvp5XIjDQP7h5hkFE8velnh3yvhzgzLpIp 3tdxbI5EANyzXcIW/GL4vs5vMM2wF4VeaOsE4pDSyhXPcVQbLG/2LFyuk580p5t1da1g BJAU+uLrDWruoe9c2LsjGk9YJ9GOG6DERaIKHSqQjNAWOKqEL1oel9OPbcK2n9bwsPlg dmaXCrzLWp+las0P0i89ee9hFTiEgQbyXUthrnPw5xhYKKWDFzlm8LxWy1zlsYmoOIzC 0VoO2QgGxs9umL6nsBcQl3eIy28GlYc9mNxbzAtQmMrLbgjbMlYNdG9/AuZzU0z0d/Ak TFew== X-Received: by 10.182.118.70 with SMTP id kk6mr244950obb.10.1359387677068; Mon, 28 Jan 2013 07:41:17 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.182.51.103 with SMTP id j7ls219133obo.94.gmail; Mon, 28 Jan 2013 07:41:16 -0800 (PST) X-Received: by 10.182.231.34 with SMTP id td2mr26399obc.11.1359387675943; Mon, 28 Jan 2013 07:41:15 -0800 (PST) Date: Mon, 28 Jan 2013 07:41:15 -0800 (PST) From: la gleki To: lojban@googlegroups.com Cc: John E Clifford Message-Id: <90c8d399-cef0-41dc-9434-9c4b6111cbab@googlegroups.com> In-Reply-To: <1359386679.75094.YahooMailNeo@web184403.mail.bf1.yahoo.com> 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> <1359386679.75094.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_405_10585199.1359387675573" X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_405_10585199.1359387675573 Content-Type: text/plain; charset=ISO-8859-1 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 loj...@googlegroups.com > . > To unsubscribe from this group, send email to > lojban+un...@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. > > > > > -- 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_405_10585199.1359387675573 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Monday, January 28, 2013 7:24:39 PM UTC+4, clifford wrote:
To start.  1) "any" is fairly peculiar to English  (a= nd related languages) but it seems that all its logical roles are related t= o scope issues, whether the scope at variance with the quantifier's, condit= ional or imperative or intensional.  Lojban doesn't do the scopes othe= r than the propositional ones well (hardly at all), so we are left to conte= xt or jury-rigging: how do we indicate that the "an apple" is best scoped a= s within, rather than outside the command (and the underlying intensional b= it about what would happen were I to get an apple or were my request to be acted up= on positively)?  Tossing {tu'a}s around, while justifiable, seems inel= egant at best.
2.  Yes, {le} makes purely denotative terms = (God, how that phrase brings back seminars and symposia of old).  It i= s pragmatically urged that the predicate involved be somehow connected to t= he object in the view of the other participants than the speaker but that i= s 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 thin= g 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 t= o the things with the indicated property that currently are of interest -- = including bringing them to our attention as one possible way.  What th= ings is quite open to contextual determination: {lo broda} may, depending o= n context, refer to the physical mass of all brodas, or the class of them o= r some subclass or or broda alone or various chunks of one or several broda= s taken separately or en masse.  There are various auxiliary devices (= not all well-developed) for disambiguating if context doesn't work.<= /div>
4 Neither {le} nor {lo} correlate in any regular way to English "the" o= r "a", though, because of salience, repeated {lo broda} comes to be "the" r= egularly. 
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 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 sol= ution that has been approved by at least 90% of lojbanists.
The s= ame questions and answers arise again and again.
We need a huge l= ist 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 m= anner analogous to "a" and "the", for back-referencing, is bad. I'm just no= t 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

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@googl= egroups.com.
Visit this group at http://groups.google.com/group/lojban?hl=3Den= .
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 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_405_10585199.1359387675573--