Received: from mail-gh0-f188.google.com ([209.85.160.188]:46287) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1U38Kf-00021Z-8B; Wed, 06 Feb 2013 08:59:12 -0800 Received: by mail-gh0-f188.google.com with SMTP id z12sf560785ghb.25 for ; Wed, 06 Feb 2013 08:58:42 -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: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=iMiQP+r+LTqyOX7Tv8TnpWvme7X0wFsVzwjk0VGtV5E=; b=PJD+n0XDf5zzm3YXAmZpOIa4LW1nntmwpzStIIv6zgUukzWeEU8AsRuoQxHt15L5I7 fauDmqNdTMpqea2QiPh+oqA0wZ6TIxdwL+qogF9mJhsl0eqlQBoZ03lJCJAA3nv4/1Hi +/r1mklnWzS4hjOD1eqGDqpTkYq3gr+aILhd2pJj6aTjgKiGEaVF4v3TErk5cnuWxWVr EX/9k0MIWjUGUOpk3ngP+Yziy6Ra8+C8H1JnVdlquhNIE8IfHK8/UrDwhFFQCjXCj2Qh zswH9TTqEkxEsBtNovl0IdrkC/uG3OnIRKnhwogBwOZMG068UGCem1NeGJZ/Y+pOWMAt S1OA== X-Received: by 10.49.62.2 with SMTP id u2mr2507104qer.38.1360169922365; Wed, 06 Feb 2013 08:58:42 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.127.142 with SMTP id ng14ls413472qeb.61.gmail; Wed, 06 Feb 2013 08:58:41 -0800 (PST) X-Received: by 10.224.110.68 with SMTP id m4mr15499125qap.2.1360169921700; Wed, 06 Feb 2013 08:58:41 -0800 (PST) X-Received: by 10.224.110.68 with SMTP id m4mr15499122qap.2.1360169921673; Wed, 06 Feb 2013 08:58:41 -0800 (PST) Received: from nm18-vm0.access.bullet.mail.mud.yahoo.com (nm18-vm0.access.bullet.mail.mud.yahoo.com. [66.94.236.23]) by gmr-mx.google.com with ESMTPS id ef22si557994qcb.0.2013.02.06.08.58.41 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Feb 2013 08:58:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 66.94.236.23 as permitted sender) client-ip=66.94.236.23; Received: from [66.94.237.127] by nm18.access.bullet.mail.mud.yahoo.com with NNFMP; 06 Feb 2013 16:58:40 -0000 Received: from [66.94.237.112] by tm2.access.bullet.mail.mud.yahoo.com with NNFMP; 06 Feb 2013 16:58:40 -0000 Received: from [127.0.0.1] by omp1017.access.mail.mud.yahoo.com with NNFMP; 06 Feb 2013 16:58:40 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 945008.18658.bm@omp1017.access.mail.mud.yahoo.com Received: (qmail 96202 invoked by uid 60001); 6 Feb 2013 16:58:40 -0000 X-YMail-OSG: 7Ig8NhQVM1kKIIMzs8Q2tE9dtDuhei4c0A7WoKVH2rrOpna 1o5X0jM9by8cnHkAZCmjsT6NafyxEGLdvJOt0on98fpEDS4135n6TS.zSw0k PHivdqbcraz90FzWHIk.oItBRF0ceRztv7vq6HH35KRA5eDziw1FzoQu34ry jB3nEySk3Q0ZwKXLJkrGP9sTiep1J0MUB3SaNRM.TvMO9klGRGMEucaL2fV0 Uw7fTbsD4xCI3OusEQeZXCxvBy29TjxKbvaZFt24cB63cO9OgnsgTf3ybTYL Zig39USLtSW7huSMN1w7881mGkWTZjeK1r_FUJA4TOnyhnLDin.z8VMTzorA 9HNHLsdd4dh8CBSNsg2J3YBJ7sLpjx4xM8Qt5bIQcm0emslhiDvnU7KP8D9V hGV7TojlNZPKoUfJu6t5tpNXrlB2YATLCrio_j0vB7R1OtGol3l1cL5JRx9v JAMbxuyqzGLoFjZ4pGfM69wwXJie77zkAf7kW3MmzUuivTLfRxxP3uBJRWc4 Yyjg4hdWCo954wkpHNOyFtt10xv4xxVFSKKXEkShMtxUtzWhnO6zKkFgK_Vt hJCTICctQErVkLhkHiw7LNSyAkymJR7JS8tiCiBi1VQZJo45n_gpNI2l2fBl zX82fSCOPUdxPLQNS6rNc9n86HG1C0.pXy6sIBvqjXQfCJA4jq6V5o24SzDz 0kJYkiq36cLK2VHe5u241y4gVQKyn7bR7FtR1.hhULVeC1avZF_oRh4mLhmA ESMlwUvmuxQYZyi1cujqfv._0T1iFwOMtLx4bsvpxwe9Jr2BLNy_7.MAifkI uEgcWK49BlaD6UlJPtvZUAwr.Gaf0sfJc7WCZrzjvTW_ds6yuZjvSPeHJaoX M0Ryhpi1mWRvHfgmByAJSmaFtuAv_VW_kAK6CHGxb1.07KQ8qlvKb Received: from [99.92.108.194] by web184402.mail.bf1.yahoo.com via HTTP; Wed, 06 Feb 2013 08:58:40 PST X-Rocket-MIMEInfo: 001.001,R29vZC4KQnV0IGl0IHdvdWxkIGJlIG5pY2UgdG8gZm9ybXVsYXRlIGEgZ2VuZXJhbCBwcmluY2lwbGUgYWJvdXQgdGhlaXIgdXNlIHRoYXQgY291bGQgYXBwbHkgYWNyb3NzIHRoZSBib2FyZC7CoCBJIGRvbid0IHBhcnRpY3VsYXJseSBzZWUgYW55IHJlYXNvbiB0byBjb25maW5lIHRoZSB1c2FnZSB0byB7ZHUndX0gKGV4Y2VwdCBmb3IgdGhlICJpbmRpcmVjdCBxdWVzdGlvbiIgbGFiZWwpIG9yIHRvIHtrYX06IHdoYXQgaGUgc2FpZCBpcyBwcmVzdW1hYmx5IGEgcHJvcG9zaXRpb24gKG9yIGEgc2xldyBvZiABMAEBAQE- X-Mailer: YahooMailWebService/0.8.132.503 References: Message-ID: <1360169920.78314.YahooMailNeo@web184402.mail.bf1.yahoo.com> Date: Wed, 6 Feb 2013 08:58:40 -0800 (PST) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] {makau} {mokau} 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 66.94.236.23 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="-334495122-266461450-1360169920=:78314" X-Spam-Score: 0.1 (/) X-Spam_score: 0.1 X-Spam_score_int: 1 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Good. But it would be nice to formulate a general principle about their use that could apply across the board. I don't particularly see any reason to confine the usage to {du'u} (except for the "indirect question" label) or to {ka}: what he said is presumably a proposition (or a slew of them) but what he saw is probably an event or a sensation and what a pair have in common might be just about anything: a property, a piece of property, a kinship, a genetic mutation, and so on forever. Of course, that would suggest the same sort of extension for the lambda term (including making it more useful), which ain't gonna happen. [...] Content analysis details: (0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kali9putra[at]yahoo.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid ---334495122-266461450-1360169920=:78314 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Good. But it would be nice to formulate a general principle about their use that = could apply across the board.=A0 I don't particularly see any reason to con= fine the usage to {du'u} (except for the "indirect question" label) or to {= ka}: what he said is presumably a proposition (or a slew of them) but what = he saw is probably an event or a sensation and what a pair have in common m= ight be just about anything: a property, a piece of property, a kinship, a = genetic mutation, and so on forever.=A0 Of course, that would suggest the s= ame sort of extension for the lambda term (including making it more useful)= , which ain't gonna happen. ________________________________ From: Remo Dentato To: lojban =20 Sent: Wednesday, February 6, 2013 10:16 AM Subject: Re: [lojban] {makau} {mokau} =20 To those still staying with the original {makau} & {mokau} question. Thanks! I'm not quite sure I'll be able to use them properly but I started = see what they are intended for. mu'o mi'e la .remod. On Wed, Feb 6, 2013 at 4:15 PM, la gleki wrote= : > >On Tuesday, February 5, 2013 8:15:10 PM UTC+4, Latro wrote: >{djuno} bothers me, because there's two different useful things it should = mean. There's a djuno-ka definition, where the speaker knows the du'u that = is created by applying djuno2 to djuno3, and there's a djuno-du'u definitio= n, where the speaker knows djuno2, which pertains to djuno3 in some way. Th= e former is in some sense "incomplete"; {lo se djuno} is not a complete bri= di syntactically but is not a "fact" semantically either. The latter is red= undant, and could just as easily be done with srana. (That is, {mi djuno lo= du'u broda noi srana ko'a} =3D=3D {mi djuno lo du'u broda kei ko'a} and {m= i djuno lo srana be ko'a} =3D=3D {mi djuno fi ko'a}). >> >>That said, simply disregarding djuno3 and leaving djuno2 lets you use jai= hackery to obtain the ka version and srana hackery to obtain the gimste ve= rsion. Of course all of this is just tinkering that won't be implemented an= yways. >> > > >Could you please provide real examples of =A0djuno with {ka}-meaning and d= juno with {srana} meaning. > > >Another question. What about morji, jimpe? Do they also show the same dual= ism? > > > >>mi'e la latro'a mu'o >> >> >>On Sat, Feb 2, 2013 at 11:06 AM, Jorge Llamb=EDas wr= ote: >> >>On Sat, Feb 2, 2013 at 12:46 PM, Jacob Errington wrot= e: >>>> >>>> {djuno2} is actually a ka, but we pretend that it isn't because the gi= mste >>>> made its definition clumsy to use that way. Indeed, the djuno2 is a pr= operty >>>> of the djuno3. >>> >>>We could say that "djuno" is a sumti raising predicate, in the >>>linguistic sense of "raising" >>>http://en.wikipedia.org/wiki/Raising_(linguistics) since its x3 is the >>>semantic argument of an embedded predicate. The same can be said of >>>almost all predicates that take a ka-argument. (There are a couple of >>>oddball predicates that the gi'uste says should take ka but are not in >>>this category.) >>> >>> >>>mu'o mi'e xorxes >>> >>> >>>-- >>>You received this message because you are subscribed to the Google Group= s "lojban" group. >>> To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+un...@googlegroups.com. >>>To post to this group, send email to loj...@googlegroups.com. >>> >>>Visit this group at http://groups.google.com/group/lojban?hl=3Den. >>>For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> > --=20 >You received this message because you are subscribed to the Google Groups = "lojban" group. >To unsubscribe from this group and stop receiving emails from it, send an = email to lojban+unsubscribe@googlegroups.com. >To post to this group, send email to lojban@googlegroups.com. >Visit this group at http://groups.google.com/group/lojban?hl=3Den. >For more options, visit https://groups.google.com/groups/opt_out. >=A0 >=A0 > --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban?hl=3Den. For more options, visit https://groups.google.com/groups/opt_out. --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban?hl=3Den. For more options, visit https://groups.google.com/groups/opt_out. ---334495122-266461450-1360169920=:78314 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Good.
But it would= be nice to formulate a general principle about their use that could apply = across the board.  I don't particularly see any reason to confine the = usage to {du'u} (except for the "indirect question" label) or to {ka}: what= he said is presumably a proposition (or a slew of them) but what he saw is= probably an event or a sensation and what a pair have in common might be j= ust about anything: a property, a piece of property, a kinship, a genetic m= utation, and so on forever.  Of course, that would suggest the same so= rt of extension for the lambda term (including making it more useful), whic= h ain't gonna happen.



From: Remo Den= tato <rdentato@gmail.com>
T= o: lojban <lojban@googlegroups.com>
Sent: Wednesday, February 6, 2013 10:16 AM<= br> Subject: Re: [lojban] = {makau} {mokau}

To those still staying = with the original {makau} & {mokau} question.

Thanks! I'm = not quite sure I'll be able to use them properly but I started see what the= y are intended for.

mu'o mi'e la .remod.


On Wed, Feb 6, 2013 at 4= :15 PM, la gleki <gleki.is.my.name@gmail.com> wrote:
<= br>
On Tuesday, February 5, 2013 8:15:10 PM UTC+4, Latro wrote: {djuno} bothers me, because there's two different useful things it should m= ean. There's a djuno-ka definition, where the speaker knows the du'u that i= s created by applying djuno2 to djuno3, and there's a djuno-du'u definition= , where the speaker knows djuno2, which pertains to djuno3 in some way. The= former is in some sense "incomplete"; {lo se djuno} is not a complete brid= i syntactically but is not a "fact" semantically either. The latter is redu= ndant, and could just as easily be done with srana. (That is, {mi djuno lo = du'u broda noi srana ko'a} =3D=3D {mi djuno lo du'u broda kei ko'a} and {mi= djuno lo srana be ko'a} =3D=3D {mi djuno fi ko'a}).

That said, simply disregarding djuno3 and leaving djuno2 lets you use j= ai hackery to obtain the ka version and srana hackery to obtain the gimste = version. Of course all of this is just tinkering that won't be implemented = anyways.

Could you please provide real exampl= es of  djuno with {ka}-meaning and djuno with {srana} meaning.

Another question. What about morji, jimpe? Do they also s= how the same dualism?


mi'e la latro'a mu'o

On Sat, Feb 2, 2013 at 11:06 AM, Jorge Llamb=EDas <<= a href=3D"" rel=3D"nofollow">jjlla...@gmail.com> wrote:
<= div>On Sat, Feb 2, 2013 at 12:46 PM, Jacob Errington <nict...@gmail.com> wrote:
>
> {djuno2} is actually a ka, but we pretend that it isn't because the gi= mste
> made its definition clumsy to use that way. Indeed, the djuno2 is a pr= operty
> of the djuno3.

We could say that "djuno" is a sumti raising predicate, in the
linguistic sense of "raising"
http://en.wikipedia.org/wiki/Raising_(linguistics) since its x3 is the
semantic argument of an embedded predicate. The same can be said of
almost all predicates that take a ka-argument. (There are a couple of
oddball predicates that the gi'uste says should take ka but are not in
this category.)

mu'o mi'e xorxes

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+un...@googlegroups.com<= /a>.
To post to this group, send email to
loj...@g= ooglegroups.com.

Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/group= s/opt_out.



--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_o= ut.
 
 

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_o= ut.
 
 


--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban?hl=3Den.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
---334495122-266461450-1360169920=:78314--