Received: from mail-yh0-f63.google.com ([209.85.213.63]:47926) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1UPAJJ-0005jW-8O for lojban-list-archive@lojban.org; Mon, 08 Apr 2013 04:32:53 -0700 Received: by mail-yh0-f63.google.com with SMTP id f64sf684694yha.8 for ; Mon, 08 Apr 2013 04:32:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:received-spf:mime-version :x-received:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results: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=AzNB82O+C+bZSLPVNqnPt5bwkTJgoxB+li0+/PCxnqA=; b=TRmGiWRiBfgcgLsfa7FDxvwA0WtDV/P0tqFvMz+uREMY2SVoEOvKfcouKRV64g5dzy bWAgq9vCXJxIIvWGTW6GOgBrhgDGhVrrh3dt1HgUMdjhsjoInVULDi6Nd81kpmyNQ+PC gceJxHMaWeUw9B63DK5WrR2YVAN9wBo1hLOrJymKDymArrclGL3o6c9NvNgY9fwJeNuf RQTpP79wLC1KH6i1fz3jsSenz5iRtnugaEzVA3k/xptzJ5Mk0umfOmdFLemYjH5aN/cQ 4kQDSX/0ZPFX+TMkO8DNI3RlrolfWnItWqQyGKkxv5ysQPI8QayXzaQIzU4pEssH3Ntk Yx5w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:received-spf:mime-version :x-received:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results: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=AzNB82O+C+bZSLPVNqnPt5bwkTJgoxB+li0+/PCxnqA=; b=owlWTy0r4UeDOYL7uwrQnSiPSg5oxIB4VvGX6851ciBa8DxL0SGCDUyhS6XCbb4OAp csert96GbI9Yop4/6QHVZSSZn6vczIm41w0x6Aq3oG13tqtqk2hKozN7VCtLOo7G9sNq e5vF47rZAdS/z3MGGSgPO0JScdWhePlGY1AWxyDLOlFxxXuALQ5oc7w0Lg3EDEndlDGn ro684FvXn3WaeWj0yXO2ZLd34T2gkOg7d01elJqjn4SG2NxmDUZHToj3aIBC/ElqzDYu 1P/FY1UTrS8jRq7lfDiGmE06WMquqztyya5Mz55JXtw8+vP6Qwtti4/8lLm4tkni32p4 yDCQ== X-Received: by 10.50.101.101 with SMTP id ff5mr815118igb.11.1365420742794; Mon, 08 Apr 2013 04:32:22 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.151.135 with SMTP id uq7ls2005921igb.24.canary; Mon, 08 Apr 2013 04:32:22 -0700 (PDT) X-Received: by 10.43.113.131 with SMTP id ew3mr16152255icc.24.1365420741989; Mon, 08 Apr 2013 04:32:21 -0700 (PDT) Received: from mail-ia0-x229.google.com (mail-ia0-x229.google.com [2607:f8b0:4001:c02::229]) by gmr-mx.google.com with ESMTPS id dl10si2147192igb.0.2013.04.08.04.32.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Apr 2013 04:32:21 -0700 (PDT) Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:4001:c02::229 as permitted sender) client-ip=2607:f8b0:4001:c02::229; Received: by mail-ia0-x229.google.com with SMTP id y26so991989iab.28 for ; Mon, 08 Apr 2013 04:32:21 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.20.135 with SMTP id n7mr6300106ige.31.1365420741857; Mon, 08 Apr 2013 04:32:21 -0700 (PDT) Received: by 10.231.237.84 with HTTP; Mon, 8 Apr 2013 04:32:21 -0700 (PDT) In-Reply-To: <2114901.tOamEWu4Il@caracal> References: <44e6fb5c-91f3-47ba-817c-8560c9c6ca14@googlegroups.com> <7a655b75-18fe-47ea-8a34-aec3ba934fbf@googlegroups.com> <2114901.tOamEWu4Il@caracal> Date: Mon, 8 Apr 2013 07:32:21 -0400 Message-ID: Subject: Re: [lojban] Re: "Any" and {ro} From: Ian Johnson To: lojban@googlegroups.com X-Original-Sender: blindbravado@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:4001:c02::229 as permitted sender) smtp.mail=blindbravado@gmail.com; dkim=pass header.i=@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=047d7bd7669249960004d9d7ca51 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --047d7bd7669249960004d9d7ca51 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Apr 7, 2013 at 11:06 PM, Pierre Abbat wrote: a. da fonta'a .i ko smadi lo du'u da mokau > b. mi tirna da .iku'i na ga'ezga da makau > c. do troci tu'a lo drata .ei selzva > d. xu da jungau do de tu? > e. ganai da'i do viska da gizibo ko jungau mi (this doesn't parse, and I'm > not > sure where to put "zibo") > g. la .djan. na viska da > h. mi jinvi lodu'u noda djuno le danfu > i. roda zo'u le banxa cu rivbi lo nu jdice da > j. roda zo'u curmi lo nu do cinba da > l. lo'e gerku cu se tuple voda While I won't protest in general about stretching the CLL's extremely vague rule about how {da} scope behaves with {.i} in the absence of an ijek, there's some other problems with this: a. da fonta'a .i ko smadi lo du'u da mokau Since ordinarily this would bind da in the du'u-scope, I'm skeptical as to whether you can stretch the rule without an ijek here. I'm also not sure what ijek would fix the job, and not sure whether {lo go'i} is actually sensible when the previous x1 is {da}. h. mi jinvi lodu'u noda djuno le danfu Depending on context this could be a problem, but that's really just having to do with {le danfu} (this one's not that bad really). This also makes sense, with somewhat different semantics, with {na jinvi lo du'u da ...}, and is arguably closer to the original that way. i. roda zo'u le banxa cu rivbi lo nu jdice da This is just wrong, even under unrestrictive models of {da}. {le banxa} is certainly in {ro da} in this context. That is, the most lax model of {da} I know of that actually makes sense includes everything that is actually in the current context in {ro da}. This gives you {le banxa cu rivbi lo nu jdice vo'a} which is absurd. I'm not sure what a legitimately good fix for this is, because you need some kind of a restriction on the {da}. {ro da poi co'e} seems like a copout, {ro da poi ka'e se jdice} seems clumsy if not sketchy for other reasons j. roda zo'u curmi lo nu do cinba da Same as the previous, though the justification feels significantly more pedantic in this case. l. lo'e gerku cu se tuple voda sei mi na pante This one's actually better than the original, because the original is of course false; in fact I would have trouble interpreting the original as generic. mi'e la latro'a mu'o -- 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=en. For more options, visit https://groups.google.com/groups/opt_out. --047d7bd7669249960004d9d7ca51 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sun, Apr 7, 2013 at 11:06 PM, Pierre Abbat=A0<phm= a@bezitopo.org>=A0wrote:

a. da fonta'a .i ko smadi lo du'u da mokau
b. mi tirna da .iku&#= 39;i na ga'ezga da makau
c. do troci tu'a lo drata .ei selzvad. xu da jungau do de tu?
e. ganai da'i do viska da gizibo ko junga= u mi (this doesn't parse, and I'm not
sure where to put "zibo")
g. la .djan. na viska da
h. mi ji= nvi lodu'u noda djuno le danfu
i. roda zo'u le banxa cu rivbi lo= nu jdice da
j. roda zo'u curmi lo nu do cinba da
l. lo'e ger= ku cu se tuple voda

While I won't protest in general about stretching the CL= L's extremely vague rule about how {da} scope behaves with {.i} in the = absence of an ijek, there's some other problems with this:

a. da fonta'a .i ko smadi lo du'u da mokau
Since ordinarily this wou= ld bind da in the du'u-scope, I'm skeptical as to whether you can s= tretch the rule without an ijek here. I'm also not sure what ijek would= fix the job, and not sure whether {lo go'i} is actually sensible when = the previous x1 is {da}.

h. mi jinvi lodu'u noda djuno le danfu
Depending= on context this could be a problem, but that's really just having to d= o with {le danfu} (this one's not that bad really). This also makes sen= se, with somewhat different semantics, with {na jinvi lo du'u da ...}, = and is arguably closer to the original that way.

i. roda zo'u le banxa cu rivbi lo= nu jdice da
This is just wrong, even under unrestrictive models of {da}. {le= banxa} is certainly in {ro da} in this context. That is, the most lax mode= l of {da} I know of that actually makes sense includes everything that is a= ctually in the current context in {ro da}. This gives you {le banxa cu rivb= i lo nu jdice vo'a} which is absurd. I'm not sure what a legitimate= ly good fix for this is, because you need some kind of a restriction on the= {da}. {ro da poi co'e} seems like a copout, {ro da poi ka'e se jdi= ce} seems clumsy if not sketchy for other reasons

=A0j. roda zo'u curmi lo nu do ci= nba da
Same as the previous, though the justification feels significant= ly more pedantic in this case.

=A0l. lo'e gerku cu se tuple voda
sei mi na pant= e This one's actually better than the original, because the original is= of course false; in fact I would have trouble interpreting the original as= generic.

=A0
mi'e la latro'a mu'o

--
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.
 
 
--047d7bd7669249960004d9d7ca51--