Received: from mail-ie0-f189.google.com ([209.85.223.189]:35560) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1TFp73-0007Po-Rk; Sun, 23 Sep 2012 09:33:09 -0700 Received: by iebc10 with SMTP id c10sf1218023ieb.16 for ; Sun, 23 Sep 2012 09:32:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :x-ymail-osg: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=atk8kQFg2GT3/x85NOY3SG+e19EA7PtN+IF4ws3ht24=; b=ZB+z729JsxnZQdqx4LeD1afXS09P/vJnks3l//yv1md9YFuGItXOgVwavPGo033sAh W117gikz2V4XnJY8HAlng0Ipyaq3GK2WKck5epMOd5pa9e/CiEz/XvO7UP5SwCk8kfrH +OuPDYOqwV89i1+KdOuZ3HYc6JOcOIRr0gGRi5aRAJ8Dka+2p//9MGIfuAoHQUI6xEca c7ajqCKE4NQFMz8mX3NTnPsBiX9ERqJRU2uMIqw91mTshUPhurGB5cmK3YRxqMqO/CkY nG5c0EJFgniamPco3KkbHyAgiSWuBnCL2Bg3barMpJAFJM07LgRIxG9xv/8NSDWiiMCz gfRg== Received: by 10.68.219.198 with SMTP id pq6mr2383868pbc.0.1348417971298; Sun, 23 Sep 2012 09:32:51 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.68.226.100 with SMTP id rr4ls1877744pbc.2.gmail; Sun, 23 Sep 2012 09:32:50 -0700 (PDT) Received: by 10.66.81.39 with SMTP id w7mr299081pax.1.1348417970524; Sun, 23 Sep 2012 09:32:50 -0700 (PDT) Received: by 10.66.81.39 with SMTP id w7mr299080pax.1.1348417970509; Sun, 23 Sep 2012 09:32:50 -0700 (PDT) Received: from nm15.bullet.mail.sp2.yahoo.com (nm15.bullet.mail.sp2.yahoo.com. [98.139.91.85]) by gmr-mx.google.com with SMTP id j3si2513195paz.2.2012.09.23.09.32.50; Sun, 23 Sep 2012 09:32:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.139.91.85 as permitted sender) client-ip=98.139.91.85; Received: from [98.139.91.69] by nm15.bullet.mail.sp2.yahoo.com with NNFMP; 23 Sep 2012 16:32:50 -0000 Received: from [66.94.237.103] by tm9.bullet.mail.sp2.yahoo.com with NNFMP; 23 Sep 2012 16:32:49 -0000 Received: from [127.0.0.1] by omp1008.access.mail.mud.yahoo.com with NNFMP; 23 Sep 2012 16:32:49 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 738819.34183.bm@omp1008.access.mail.mud.yahoo.com Received: (qmail 54224 invoked by uid 60001); 23 Sep 2012 16:32:49 -0000 X-YMail-OSG: qIGAR_YVM1lcPb9neWDRmg0vFLbeIiqJHqaSEwKm7oeUeIU XbauxOlYwquaFeeOr_DHHlHfSxBxnjOUNBREHsJMLiGgID1qeZzfAvOOZAjz _wn7lYmenbuhHOnpcxPSlnRtYrv13D5Whm5MW.vm9Tec5B6baks_s4ThAYq7 nwWa3WaMOaWh3WuItDQAOH7YZrVvDpgv2ZFFE5uPYtM.K.eBUrN1zqFGHY7x Zv86fq5.ChWj5pxTcYO6r7BMG6VdvFrZ.NULnCwl7mkjwkeNnfY7PBIs1fmw DGrVWHn0r3fLRloG7zxTzOAj3VapgyPZFYH3I.dMizDMDpfFXRmNeUjz6AhX CEP_PgXNDJBZ2Y9bJQniaRY5Yt6C67uWoQ.IOoEPOAss0O77L35wn9xSVFwU 98g4dp_l0E0G9A2T.v1HF86xc2Rn_QedmAv.Xf3CEBPQ.dmNMEB9qThJk_s. LV6Za6Kh8shIEGTOuBH2m8mgBZrFAECZv1VD0XMAiPOCdZYRwBO4CLZ4B.vf mcaZaQd687MbB9MvqEs2btGn1oWuDu9Pmsd7BxoiSGN8geJJRoCyDukwFHMl 0GiihFnyqsQ9iNykWNju1HqSfv614DrtCThSCFW2BE58P Received: from [99.92.108.194] by web184404.mail.bf1.yahoo.com via HTTP; Sun, 23 Sep 2012 09:32:49 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <4eae7ab1-572f-44cc-a260-a78b3bf93a9c@googlegroups.com> <4646abde-2d1e-4e97-a7e5-5e187d7ec59e@googlegroups.com> <08369d01-d329-494e-95e9-7e6375e390fd@googlegroups.com> Message-ID: <1348417969.42535.YahooMailNeo@web184404.mail.bf1.yahoo.com> Date: Sun, 23 Sep 2012 09:32:49 -0700 (PDT) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] Re: Cowan's summary: opacity and sumti-raising To: "lojban@googlegroups.com" In-Reply-To: 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 98.139.91.85 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) 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-1810159024-1348417969=:42535" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ---420974808-1810159024-1348417969=:42535 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I seem to have missed something here.=A0 Is the question whether different = sorts of things can be mentioned as objects of desires or portrayal or eval= uation?=A0 To a fairly large extent, the answer is obviously "Yes!".=A0 Mor= e readily in some cases than in others: desires and needs, for example,=A0 = are for things that fit into a causal narrative and so pretty much have to = be events; pictures pretty much range over all possible categories (in a br= oad sense of "picture" of course, as is usual in art), seeking is limited (= perhaps) to the concrete (although answers seem to be an exception).=A0=20 In any case, I doubt that this is the problem.=A0 What is usually the probl= em here is that sometimes the predicates of this sort take arguments that c= reate an intensional context and sometimes not.=A0 And the reason for that = is simply that sometimes the arguments involve reference to things in the e= xternal world and sometime not.=A0 A picture of USS Constitution battling H= MS Seraphis sets up different logical expectations from a picture of just t= wo frigates fighting, namely that there are, outside the world of the pictu= re, two ships who might be in this battle, whereas there is no such certain= ty in the second case.=A0 And, in a logical language, this needs to be refl= ected, somehow, in the presentation.=A0 The present system doesn't do this = very well (the inchoate Xorban seems to be a bit better, but it is still to= o illformed to be sure), but it at least warns one to be wary about the twi= n no-nos of quantifying in and interchange of identicals.=A0=20 ________________________________ From: Jacob Errington To: lojban@googlegroups.com=20 Sent: Sunday, September 23, 2012 11:07 AM Subject: Re: [lojban] Re: Cowan's summary: opacity and sumti-raising =20 I dislike multiple types in pretty much any place. I don't personally belie= ve that love can apply to events, but obviously, that's arguable. People ar= e going to use the language the way they want, because at this point there'= re no stone tablets with the rules really written onto them. I don't even t= hink that it's useful at this point to try convincing people of what's righ= t and wrong with the language. It's like a religious debate. .i mi'e la tsani mu'o On 23 September 2012 01:12, la gleki wrote: > >On Saturday, September 22, 2012 9:53:23 PM UTC+4, tsani wrote: >The thing about {cirko} is that it may or may not have to deal with posses= sion. It has a sort of possession focus, but if you're using it with proper= ties, then that just falls apart: {.i mi cirko lo ka pampe'o do} >>Really, it's just co'u, but when used on a concrete sumti, it has the imp= lication of losing possession. I'm not too fond of this duality. > > >Are you fond of lo selpa'i duality being both an object and an abstraction= ? May be we should say {mi prami tu'a do} all the time? > >> >>.i mi'e la tsani mu'o >> >> >>On 22 September 2012 12:53, Ian Johnson wrote: >> >>I consider {cirko} to have similar issues to {binxo}; if it's going to ha= ve anything to do with properties, it should always have to do with propert= ies, but since properties are just predicates in my usage, {binxo} is essen= tially redundant to {co'a}. {cirko} as only having to do with {co'u ponse} = would be fine, but if it has to do with a property then it is again redunda= nt to just {co'u}. >>> >>>The rest are straightforwardly fine, to me; things like {melbi} fall int= o a general category of "pre-jai'd" gismu, which are a bit odd but useful a= nd pe'i consistent. >>> >>>mu'o mi'e la latro'a >>> >>> >>> >>>On Sat, Sep 22, 2012 at 9:18 AM, la gleki wrote: >>> >>>I should make my point more clear. >>>> >>>> >>>>Look at the following. >>>> >>>> >>>>prami x1 loves/feels strong affectionate devotion towards x2 (object/st= ate). >>>> >>>>dirba x1 is dear/precious/darling to x2; x1 is emotionally valued by x2= ;=A0x1 may be a specific object, a commodity (mass), an event, or a propert= y >>>>pluka x1 (event/state) seems pleasant to/pleases x2 under conditions x3= . >>>>melbi=A0x1 is beautiful/pleasant to x2 in aspect x3 (ka) by aesthetic s= tandard x4. >>>> >>>> >>>>And last but not least >>>>cirko -cri-=A0x1 loses person/thing x2 at/near x3; x1 loses property/fe= ature x2 in conditions/situation x3;=A0x2 may be a specificobject, a commod= ity (mass), an event (rare for cirko), or a property. >>>> >>>> >>>>This last example shows something mutce lo ka cizra. >>>> >>>> >>>> >>>>If we can easily interchange objects and abstractions in {lo se prami, = lo dirba, lo se cirko} omitting {tu'a} then it would be reasonable to ask: >>>> >>>> >>>>"What the hell is {tu'a} for?" If lojban is not consistent in using it = at all, why not omit it all the time? >>>> >>>> >>>>Then we'll get those {mi sisku lo penbi} (in la selpa'i=A0's dialect) a= nd even {mi djica lo plise}. >>>> >>>> >>>>On Monday, August 20, 2012 12:46:15 PM UTC+4, la gleki wrote: >>>>Again Google Groups didn't let me resurrect this old discussion. So ple= ase follow the link to follow the whole discussion. >>>>> >>>>> >>>>>And now it's my turn to ask the community once again after 18 years of= disinterest. >>>>> >>>>> >>>>>{djica}, {nitcu} and {sisku}, for example, have all been >>>>>>dealt with differently: {djica} only accepts events, {nitcu} still ac= cepts >>>>>>objects, and the solution for {sisku} was the weirdest: the x2 place = was >>>>>>directly eliminated and replaced by only a property of some inaccesib= le >>>>>>entity, so that {le se sisku} is not the thing looked for, but a prop= erty >>>>>>of said thing. >>>>>>=A0 >>>>>> >>>>Why not treat them all the same? >>>>>> >>>>>> >>>>>>The transparent case: >>>>>> >>>>>> >>>>>>{mi djica lo tanxe} =3D "There is a box wanted by me" >>>>>>{mi nitcu lo tanxe} =3D "There is a box needed by me" >>>>>>{mi sisku lo tanxe} =3D "There is a box sought by me" >>>>> >>>>> >>>>>One more moment. Are there any other gismu that have the same "problem= "?=A0 >>>>> >>>>>On Tuesday, November 22, 1994 4:03:33 AM UTC+4, Jorge Llambias wrote: >>>>>la lojbab cusku di'e >>>>>>> Of course there is nothing strange about a brivla relating two obje= cts - a >>>>>>> seeker and the thing known-and-sought-after, and having a certain p= redicate >>>>>>> relating them. =A0The problem that I see is that there is more than= one such >>>>>>> predicate, and the choice is dependent on the specificity =A0(or is= that >>>>>>> definiteness %^) of x2 vs. its opacity, etc., and what the desire i= s of the >>>>>>> seeker for the final state after finding. >>>>>>The problem is transparency vs opacity. Transparent references can be >>>>>>specific or nonspecific, and that can be marked with the appropriate >>>>>>quantifiers, but we don't have any way to mark explicitly opaque refe= rences. >>>>>>The other properties that you mention, like desires of the seeker for= what >>>>>>to do after (or rather if) the sought after thing is found, are not r= eally >>>>>>to the point. If you want a place for them I guess you do need a lujv= o. >>>>>>Also, in English, the meaning of "seek an object" has been generalize= d >>>>>>to "seek knowledge", where by "finding it", we mean that we get to >>>>>>know the truth value of some utterance. (I suppose that's what you ca= ll the >>>>>>seeking of science.) I don't have a problem with letting this metapho= rical >>>>>>extension into Lojban, but in any case this is not part of the opaque= problem. >>>>>>An interesting property of sisku as it is defined now, is that the la= mbda >>>>>>variable of its property really never takes a value. Normally, the la= mbda >>>>>>variable of a property corresponds to one or more of the places of th= e >>>>>>selbri (for example for {zmadu}, it's the x1 and x2) but for sisku, t= here >>>>>>is no place for the thing being sought, so there is no place that fit= s the >>>>>>lambda variable. >>>>>>> WE have other cases in Lojban where the Lojban word covers a mislea= ding >>>>>>> subset of the English meanings of the keywords ("old" and "know" be= ing two >>>>>>> cases that come to mind). >>>>>>BTW, because of my mail problems a month or so ago I never found out = whether >>>>>>{citno} means "young", so that it only refers to living things, or wh= ether >>>>>>it is more general. Would an "old car" in lojban be a {tolcitno karce= } or >>>>>>a {tolcnino karce}? >>>>>>> In all such casesa we have learned to live with the >>>>>>> fact that the English word is tto broad and have come up with lujvo= for the >>>>>>> alternative meanings. =A0Such lujvo can always exist, and if this w= hole >>>>>>> issue of "lo" and "existence" blows away. the number of distinction= s we need >>>>>>=A0to >>>>>>> make may be reduced. =A0But I remain unconvinced of this - as pc sa= id a while >>>>>>> back in this discussion - there are some predicates that embody a h= idden >>>>>>> abstraction involving one of the sumti, and we have to live with th= is >>>>>>What do you mean by "some predicates"? English verbs, like "want", "n= eed", >>>>>>"look for", etc, or Lojban predicates like {djica}, {nitcu}, {sisku},= etc.? >>>>>>I totally agree that the English verbs can accept opaque references a= s direct >>>>>>objects, without any marking. They also, in other contexts, can take = transparent >>>>>>direct objects. >>>>>>Because of the logical aspect of Lojban, this can't work like that in= Lojban, >>>>>>and so the arguments are always transparent. >>>>>>But, the fact is that the opaque meaning is often very useful for the= se >>>>>>predicates, so what do we do? >>>>>>I propose to find one solution for all such predicates, rather than p= atches >>>>>>for each of them. {djica}, {nitcu} and {sisku}, for example, have all= been >>>>>>dealt with differently: {djica} only accepts events, {nitcu} still ac= cepts >>>>>>objects, and the solution for {sisku} was the weirdest: the x2 place = was >>>>>>directly eliminated and replaced by only a property of some inaccesib= le >>>>>>entity, so that {le se sisku} is not the thing looked for, but a prop= erty >>>>>>of said thing. >>>>>>Why not treat them all the same? >>>>>>The transparent case: >>>>>>{mi djica lo tanxe} =3D "There is a box wanted by me" >>>>>>{mi nitcu lo tanxe} =3D "There is a box needed by me" >>>>>>{mi sisku lo tanxe} =3D "There is a box sought by me" >>>>>>and the opaque case: >>>>>>{mi djica xe'e lo tanxe} =3D "I want a box (I don't care which)" >>>>>>{mi nitcu xe'e lo tanxe} =3D "I need a box (I don't care which)" >>>>>>{mi sisku xe'e lo tanxe} =3D "I seek a box (I don't care which)" >>>>>>(I don't mind using {lo'e} instead of {xe'e lo}, I think it makes sen= se >>>>>>as well.) >>>>>>As things stand now, for the transparent case I have to say: >>>>>>{da poi tanxe zo'u mi djica tu'a da} >>>>>>{mi nitcu lo tanxe} >>>>>>{da poi tanxe zo'u mi sisku le ka du da} >>>>>>Why so complicated? >>>>>>> =A0 =A0 =A0 =A0mi'e la lojbab noi sisku loka lo danfu be le me zo s= isku me'u nabmi >>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 cu mansa roda >>>>>>That doesn't make much sense to me. You probably mean {noi sisku lo k= a danfu >>>>>>le me zo sisku me'u nabmi gi'e mansa roda}, otherwise you are saying = that >>>>>>you are looking for something with property an answer satisfies every= one, >>>>>>but what is it that you look for? the answer, everyone? I think this = is an >>>>>>unnecessarily complicated way to deal with {sisku}. >>>>>>Jorge >>>> --=20 >>>>You received this message because you are subscribed to the Google Grou= ps "lojban" group. >>>> To view this discussion on the web visit https://groups.google.com/d/msg/lo= jban/-/aTfTDbKnrqUJ. >>>> >>>>To post to this group, send email to loj...@googlegroups.com. >>>>To unsubscribe from this group, send email to lojban+un...@googlegroups= .com. >>>> >>>>For more options, visit this group at http://groups.google.com/group/lo= jban?hl=3Den. >>>> >>> >>>--=20 >>>You received this message because you are subscribed to the Google Group= s "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. >>> >>>For more options, visit this group at http://groups.google.com/group/loj= ban?hl=3Den. >>> >> > --=20 >You received this message because you are subscribed to the Google Groups = "lojban" group. > To view this discussion on the web visit https://groups.google.com/d/msg/lo= jban/-/t_ef3I0HOREJ. > >To post to this group, send email to lojban@googlegroups.com. >To unsubscribe from this group, send email to lojban+unsubscribe@googlegro= ups.com. >For more options, visit this group at http://groups.google.com/group/lojba= n?hl=3Den. > --=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. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den. --=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. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den. ---420974808-1810159024-1348417969=:42535 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I seem to have missed= something here.  Is the question whether different sorts of things ca= n be mentioned as objects of desires or portrayal or evaluation?  To a= fairly large extent, the answer is obviously "Yes!".  More readily in= some cases than in others: desires and needs, for example,  are for t= hings that fit into a causal narrative and so pretty much have to be events= ; pictures pretty much range over all possible categories (in a broad sense= of "picture" of course, as is usual in art), seeking is limited (perhaps) = to the concrete (although answers seem to be an exception). 
In an= y case, I doubt that this is the problem.  What is usually the problem= here is that sometimes the predicates of this sort take arguments that cre= ate an intensional context and sometimes not.  And the reason for that is simply that sometimes the arguments involve reference to things in= the external world and sometime not.  A picture of USS Constitution b= attling HMS Seraphis sets up different logical expectations from a picture = of just two frigates fighting, namely that there are, outside the world of = the picture, two ships who might be in this battle, whereas there is no suc= h certainty in the second case.  And, in a logical language, this need= s to be reflected, somehow, in the presentation.  The present system d= oesn't do this very well (the inchoate Xorban seems to be a bit better, but= it is still too illformed to be sure), but it at least warns one to be war= y about the twin no-nos of quantifying in and interchange of identicals.&nb= sp;



= From: Jacob Errington <= ;nictytan@gmail.com>
To: lojban@googlegroups.com
Se= nt: Sunday, September 23, 2012 11:07 AM
Subject: Re: [lojban] Re: Cowan's summary: opa= city and sumti-raising

I dislike multiple types in pretty much any place.= I don't personally believe that love can apply to events, but obviously, t= hat's arguable. People are going to use the language the way they want, bec= ause at this point there're no stone tablets with the rules really written = onto them. I don't even think that it's useful at this point to try convinc= ing people of what's right and wrong with the language. It's like a religio= us debate.

.i mi'e la tsani mu'o

On 23 September 2012 01:12, la gleki <gleki.is.my.name@gmail.com> wrote:
<= br>
On Saturday, September 22, 2012 9:53:23 PM UTC+4, tsani wrote: The thing about {cirko} is that it may or may not have to deal with possess= ion. It has a sort of possession focus, but if you're using it with propert= ies, then that just falls apart: {.i mi cirko lo ka pampe'o do}
Really, it's just co'u, but when used on a concrete sumti, it has the impli= cation of losing possession. I'm not too fond of this duality.

Are you fond of lo selpa'i duality being bo= th an object and an abstraction? May be we should say {mi prami tu'a do} al= l the time?

.i mi'e la tsani mu'o

I consider {cirko} to have similar issues to {binxo}; if it's going to have= anything to do with properties, it should always have to do with propertie= s, but since properties are just predicates in my usage, {binxo} is essenti= ally redundant to {co'a}. {cirko} as only having to do with {co'u ponse} wo= uld be fine, but if it has to do with a property then it is again redundant= to just {co'u}.

The rest are straightforwardly fine, to me; things like {melbi} fall in= to a general category of "pre-jai'd" gismu, which are a bit odd but useful = and pe'i consistent.

mu'o mi'e la latro'a


On Sat, Sep 22, 2012 at 9:18 AM, la gleki <gleki.is...@gmail.com> wrote:
I should make my point more clear.

Look at the following= .

prami x1 loves/feels strong affectionate de= votion towards x2 (object/state).
dirba x1 is dear/precious/= darling to x2; x1 is emotionally valued by x2; x1 may be a specific object, a commodity (mass), an event, or a property
pluka x1 (event/state) seems pleasant to/pleases x2 under c= onditions x3.
melbi x1 is beautiful/pleasant to x2 in = aspect x3 (ka) by aesthetic standard x4.

And last = but not least
cirko -cri- x1 loses person/thing x2 at/near x3; x1 loses pr= operty/feature x2 in conditions/situation x3; x2 may be a specific = object, a commodity (mass), an event (rare for cirko), or a property= .

This last example shows something mutce lo ka = cizra.

If we can easily interchange object= s and abstractions in {lo se prami, lo dirba, lo se cirko} omitting {tu'a} = then it would be reasonable to ask:

"What the hell is {tu'a} for?" If lojban is not cons= istent in using it at all, why not omit it all the time?
<= br>
Then we'll get those {mi sisku lo penbi} (in la sel= pa'i 's dialect) and even {mi djica lo plise}.


On Monday, August 20, 2012 12:46:15 PM UTC+4, = la gleki wrote:
Ag= ain Google Groups didn't let me resurrect this old discussion. So please follow the link to follow the whole d= iscussion.

And now it's my turn to ask the community once again af= ter 18 years of disinterest.

{djica}, {nitcu} and {sis= ku}, for example, have all been
dealt with differently: {djica} only accepts events, {nitcu} still acc= epts
objects, and the solution for {sisku} was the weirdest: the = x2 place was
directly eliminated and replaced by only a property = of some inaccesible
entity, so that {le se sisku} is not the thing looked for, but a prope= rty
of said thing.
 
Why not treat them all the same?

The transparent case:

{mi djica lo tanxe} =3D "T= here is a box wanted by me"
{mi nitcu lo tanxe} =3D "There is a box needed by me"
{mi si= sku lo tanxe} =3D "There is a box sought by me"

=
One more moment. Are there any other gismu that have the same "p= roblem"? 

On Tuesday, November 22, 1994 4:03:33 AM UTC+4, Jorge Llambias wro= te:
la lojbab cusku di'e
> Of course there is nothing strange about a br= ivla relating two objects - a
> seeker and the thing known-and-sought= -after, and having a certain predicate
> relating them.  The pro= blem that I see is that there is more than one such
> predicate, and the choice is dependent on the specificity  (or is= that
> definiteness %^) of x2 vs. its opacity, etc., and what the de= sire is of the
> seeker for the final state after finding.
= The problem is transparency vs opacity. Transparent references can be
specific or nonspecific, and that can be marked with the appropriate
qua= ntifiers, but we don't have any way to mark explicitly opaque references.
The other properties that you mention, like desires of the seeker = for what
to do after (or rather if) the sought after thing is found, are not really<= br>to the point. If you want a place for them I guess you do need a lujvo.<= /div>
Also, in English, the meaning of "seek an object" has been genera= lized
to "seek knowledge", where by "finding it", we mean that we get to
know = the truth value of some utterance. (I suppose that's what you call the
s= eeking of science.) I don't have a problem with letting this metaphorical extension into Lojban, but in any case this is not part of the opaque probl= em.
An interesting property of sisku as it is defined now, is tha= t the lambda
variable of its property really never takes a value. Normal= ly, the lambda
variable of a property corresponds to one or more of the places of the
s= elbri (for example for {zmadu}, it's the x1 and x2) but for sisku, thereis no place for the thing being sought, so there is no place that fits the=
lambda variable.
> WE have other cases in Lojban where the Loj= ban word covers a misleading
> subset of the English meanings of the = keywords ("old" and "know" being two
> cases that come to mind).
BTW, because of my mail problems a month or so ago I never found out w= hether
{citno} means "young", so that it only refers to living things, o= r whether
it is more general. Would an "old car" in lojban be a {tolcitn= o karce} or
a {tolcnino karce}?
> In all such casesa we have learned to li= ve with the
> fact that the English word is tto broad and have come u= p with lujvo for the
> alternative meanings.  Such lujvo can alw= ays exist, and if this whole
> issue of "lo" and "existence" blows away. the number of distinctions w= e need
 to
> make may be reduced.  But I remain unconvin= ced of this - as pc said a while
> back in this discussion - there ar= e some predicates that embody a hidden
> abstraction involving one of the sumti, and we have to live with this<= /div>
What do you mean by "some predicates"? English verbs, like "want"= , "need",
"look for", etc, or Lojban predicates like {djica}, {nitcu}, {= sisku}, etc.?
I totally agree that the English verbs can accept opaque references as= direct
objects, without any marking. They also, in other contexts, can = take transparent
direct objects.
Because of the logical aspect= of Lojban, this can't work like that in Lojban,
and so the arguments are always transparent.
But, the fact is tha= t the opaque meaning is often very useful for these
predicates, so what = do we do?
I propose to find one solution for all such predicates,= rather than patches
for each of them. {djica}, {nitcu} and {sisku}, for example, have all been<= br>dealt with differently: {djica} only accepts events, {nitcu} still accep= ts
objects, and the solution for {sisku} was the weirdest: the x2 place = was
directly eliminated and replaced by only a property of some inaccesible
= entity, so that {le se sisku} is not the thing looked for, but a propertyof said thing.
Why not treat them all the same?
The t= ransparent case:
{mi djica lo tanxe} =3D "There is a box wanted by me"
{mi nitcu lo = tanxe} =3D "There is a box needed by me"
{mi sisku lo tanxe} =3D "There = is a box sought by me"
and the opaque case:
{mi djica xe'e lo tanxe} =3D "I want a box (I don't care which)"
{m= i nitcu xe'e lo tanxe} =3D "I need a box (I don't care which)"
{mi sisku= xe'e lo tanxe} =3D "I seek a box (I don't care which)"
(I don't mind using {lo'e} instead of {xe'e lo}, I think it makes sens= e
as well.)
As things stand now, for the transparent case I ha= ve to say:
{da poi tanxe zo'u mi djica tu'a da}
{mi nitcu lo tanxe}
{da poi tanxe zo'u mi sisku le ka du da}
W= hy so complicated?
>        mi'e la lojbab= noi sisku loka lo danfu be le me zo sisku me'u nabmi
>    =                     &nbs= p; cu mansa roda
That doesn't make much sense to me. You probably mean {noi sisku lo ka= danfu
le me zo sisku me'u nabmi gi'e mansa roda}, otherwise you are say= ing that
you are looking for something with property an answer satisfies= everyone,
but what is it that you look for? the answer, everyone? I think this is an<= br>unnecessarily complicated way to deal with {sisku}.
Jorge
--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://= groups.google.com/d/msg/lojban/-/aTfTDbKnrqUJ.
<= div>
=20 To post to this group, send email to loj...@g= ooglegroups.com.
To unsubscribe from this group, send email to lojban+un...@googlegroups.com.
For more options, visit this group at http://groups.googl= e.com/group/lojban?hl=3Den.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to loj...@g= ooglegroups.com.
To unsubscribe from this group, send email to lojban+un...@googlegroups.com.
For more options, visit this group at http://groups.googl= e.com/group/lojban?hl=3Den.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://= groups.google.com/d/msg/lojban/-/t_ef3I0HOREJ.

=20 To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegro= ups.com.
For more options, visit this group at http://groups.googl= e.com/group/lojban?hl=3Den.

--
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.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.


--
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.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
---420974808-1810159024-1348417969=:42535--