Received: from mail-yx0-f189.google.com ([209.85.213.189]:42589)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCKOXn8wTELvJ-oAFGgToPlQ8@googlegroups.com>)
	id 1Sy43u-0004bc-I4; Sun, 05 Aug 2012 09:52:22 -0700
Received: by yenq11 with SMTP id q11sf822610yen.16
        for <multiple recipients>; Sun, 05 Aug 2012 09:52:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=beta;
        h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject
         :mime-version: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=36ROSi4T4qVqN1l1r6RXPa3yrMqNOopFU2dqQeNkY3E=;
        b=QX9Ns0maZ6KoF9HKZe78AJflJV7NCJFs+5BSpJ+AXYwCw391++3dO7UDIHDbPxVgW2
         HlJfMSzYSLDCxFGWWVzwoUqPH+vRtBYZz+aZyZ3APdaQ9v3bS7y2AGLzJ+0ZKq0ZufbW
         uSQl2kkjivbTxrOhC5XoVQqZgzMWdUR/C3XKs=
Received: by 10.52.34.8 with SMTP id v8mr732351vdi.5.1344185531870;
        Sun, 05 Aug 2012 09:52:11 -0700 (PDT)
X-BeenThere: lojban@googlegroups.com
Received: by 10.220.223.77 with SMTP id ij13ls4185829vcb.1.gmail; Sun, 05 Aug
 2012 09:52:10 -0700 (PDT)
Received: by 10.52.71.7 with SMTP id q7mr703861vdu.20.1344185530490;
        Sun, 05 Aug 2012 09:52:10 -0700 (PDT)
Date: Sun, 5 Aug 2012 09:52:09 -0700 (PDT)
From: Gleki Arxokuna <gleki.is.my.name@gmail.com>
To: lojban@googlegroups.com
Message-Id: <9b2f1ef7-d761-46ac-b963-fdad88ae0697@googlegroups.com>
In-Reply-To: <b009781f-3cae-4773-85cf-8730270d335e@googlegroups.com>
References: <d31f9fdd-bfa0-4f98-ba41-77ed87af37a6@googlegroups.com> <501CCD85.9090902@gmail.com> <CAEimHHArGqziabsHa-vi_dGeFhtnStyQf6GovS6Frk=xWr1Vdg@mail.gmail.com>
 <201208041530.45361.phma@phma.optus.nu>
 <8a72d9e6-4047-40ad-a1c2-ca19e97db2ed@googlegroups.com>
 <b009781f-3cae-4773-85cf-8730270d335e@googlegroups.com>
Subject: Re: [lojban] Ancient Greek, free word order and the same FA two times
  in a bridi
MIME-Version: 1.0
X-Original-Sender: gleki.is.my.name@gmail.com
X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of
 gleki.is.my.name@gmail.com designates internal as permitted sender)
 smtp.mail=gleki.is.my.name@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: <lojban.googlegroups.com>
X-Google-Group-Id: 1004133512417
List-Post: <http://groups.google.com/group/lojban/post?hl=en_US>, <mailto:lojban@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:lojban+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/lojban?hl=en_US>
Sender: lojban@googlegroups.com
List-Subscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:lojban+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:googlegroups-manage+1004133512417+unsubscribe@googlegroups.com>
Content-Type: multipart/alternative; 
	boundary="----=_Part_238_4040802.1344185529946"
X-Spam-Score: -0.7 (/)
X-Spam_score: -0.7
X-Spam_score_int: -6
X-Spam_bar: /

------=_Part_238_4040802.1344185529946
Content-Type: text/plain; charset=ISO-8859-1

doi djandus isn't it {ju'e} that pafcribe suggested?
If you agree with it we have three votes (including mine).

On Sunday, August 5, 2012 6:40:59 PM UTC+4, djandus wrote:
>
> On Sunday, August 5, 2012 4:38:29 AM UTC-5, iesk wrote:
>>
>> I tend to think that {broda fa ko'a fa ko'e} means more or less the same 
>> thing as {ko'a broda .i ko'e broda}, 
>
> This is also what I was imagining at first, but I didn't realize it until 
> you said it. It occurs to me that this would probably be the most easily 
> acceptable interpretation for dealing with the problems I brought up (i.e. 
> how it interrelates with {be} and GOhA usage) as it leaves it up to context 
> what relationship there is between the two statements, if any. In the case 
> of GOhA, it would generally be an overwrite of the previous, implying some 
> form of correction. In the case of {be} and double-FA, I think it's a 
> somewhat silly usage, but it could make sense. 
>
> Personally, I find the pure "erasure" sort of usage to be very useful, and 
> any other kind of... weak. I also think logical connective implications 
> would be explicitly wrong, as those feel completely against the GOhA 
> overwrite usage, and it would only be a very small shortcut to far more 
> confusing statements that are already expressible.
>
> mu'o mi'e djos
>

-- 
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/-/c7Wrov6u8vIJ.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.


------=_Part_238_4040802.1344185529946
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

doi djandus isn't it {ju'e} that pafcribe suggested?<div>If you agree with =
it we have three votes (including mine).<br><div><br>On Sunday, August 5, 2=
012 6:40:59 PM UTC+4, djandus wrote:<blockquote class=3D"gmail_quote" style=
=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: =
1ex;">On Sunday, August 5, 2012 4:38:29 AM UTC-5, iesk wrote:<blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #cc=
c solid;padding-left:1ex">I tend to think that {broda fa ko'a fa ko'e} mean=
s more or less the same thing as {ko'a broda .i ko'e broda},&nbsp;</blockqu=
ote><div>This is also what I was imagining at first, but I didn't realize i=
t until you said it. It occurs to me that this would probably be the most e=
asily acceptable interpretation for dealing with the problems I brought up =
(i.e. how it interrelates with {be} and GOhA usage) as it leaves it up to c=
ontext what relationship there is between the two statements, if any. In th=
e case of GOhA, it would generally be an overwrite of the previous, implyin=
g some form of correction. In the case of {be} and double-FA, I think it's =
a somewhat silly usage, but it could make sense.&nbsp;</div><div><br></div>=
<div>Personally, I find the pure "erasure" sort of usage to be very useful,=
 and any other kind of... weak. I also think logical connective implication=
s would be explicitly wrong, as those feel completely against the GOhA over=
write usage, and it would only be a very small shortcut to far more confusi=
ng statements that are already expressible.</div><div><br></div><div>mu'o m=
i'e djos</div></blockquote></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups "=
lojban" group.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/lojban/-/c7Wrov6u8vIJ">https://groups.google.com/d/msg/lojban/-/c7=
Wrov6u8vIJ</a>.<br />=20
To post to this group, send email to lojban@googlegroups.com.<br />
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou=
ps.com.<br />

For more options, visit this group at http://groups.google.com/group/lojban=
?hl=3Den.<br />



------=_Part_238_4040802.1344185529946--