Received: from mail-qc0-f187.google.com ([209.85.216.187]:52710) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1UZLlM-0003Wv-Gw for lojban-list-archive@lojban.org; Mon, 06 May 2013 06:47:44 -0700 Received: by mail-qc0-f187.google.com with SMTP id a6sf1252446qch.4 for ; Mon, 06 May 2013 06:47:26 -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:x-received :mime-version:sender:in-reply-to:references:from:date:message-id :subject: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:list-subscribe:list-unsubscribe :content-type; bh=xuFWvj6XB7Hb5E5fVcPh7dnctNpMF386p3A1KTix7nM=; b=QcYcuMfyhMV0jnkgfVT3taI7gQ57qYHYN/g5IFB1dG9wWqCv+I5AztAr/FfHAy8ZOG 4SZl1FrWrSzub6gTLJmxXwoYV4l0TPGJbv8djUFPSjTmbfmYuu/PwZXKj51B70FTdaoZ K6fT+mbdpfCqP6q0jvNnT00goFAhU0WaE6TX6VQl2yD+8pqHBwHxU1Pc6HId7WZox3m+ BE1nIlVcFbyHXLgzppXq5yyobxAwotowanZ5EfsmjmRxr4Yf7PVOakCZHQAy55jX4KI4 LoviTe7mQAzF4Mp9SPvz7eq0xUIYLnPl+0O95MAzNMQ1Tw1z91FigWdHJ8yYirdI4dcC Y58A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:received-spf:x-received :mime-version:sender:in-reply-to:references:from:date:message-id :subject: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:list-subscribe:list-unsubscribe :content-type; bh=xuFWvj6XB7Hb5E5fVcPh7dnctNpMF386p3A1KTix7nM=; b=F3IalPjM0juNRNveHYgttM9kC763XOn9GNqybkwBPsjT7mlGAqbuXfaqFUPIRRgAbk A0LGMQPRe8sWIBNh3Mw0TSbFTumyB3j2iyYimiub8JCMiKLZ7yfnnIt0CavVnKW1APOn y32WI5rmU5mxWh/HcryXwRICPW42aszRHuWJYs8HF/2HFzm4s3BpwBU+ynztK/nx/4Xf ZHwqWG/PKTu7pUk1rN6OEIAczIR0/D6nJO66AZapVXygGVxnrMZ7hNTqKOUdHzjVeHBp x8bzLRLPl/wDbAWAe7+IzvzgG/661umvKWABtRDichaoHlH3FKGGHLF5we5elWPmrK7n BJcw== X-Received: by 10.49.6.201 with SMTP id d9mr201636qea.12.1367848046175; Mon, 06 May 2013 06:47:26 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.49.119.129 with SMTP id ku1ls2956722qeb.49.gmail; Mon, 06 May 2013 06:47:24 -0700 (PDT) X-Received: by 10.58.120.68 with SMTP id la4mr12809240veb.39.1367848044745; Mon, 06 May 2013 06:47:24 -0700 (PDT) Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by gmr-mx.google.com with ESMTPS id xu10si1223394vdb.0.2013.05.06.06.47.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 May 2013 06:47:24 -0700 (PDT) Received-SPF: pass (google.com: domain of rpglover64@gmail.com designates 209.85.220.177 as permitted sender) client-ip=209.85.220.177; Received: by mail-vc0-f177.google.com with SMTP id ha12so3023810vcb.22 for ; Mon, 06 May 2013 06:47:24 -0700 (PDT) X-Received: by 10.52.122.18 with SMTP id lo18mr5780411vdb.32.1367848044658; Mon, 06 May 2013 06:47:24 -0700 (PDT) MIME-Version: 1.0 Sender: lojban@googlegroups.com Received: by 10.220.118.79 with HTTP; Mon, 6 May 2013 06:47:04 -0700 (PDT) In-Reply-To: References: <20130504201243.GE20411@stodi.digitalkingdom.org> <51856E57.2010808@gmx.de> <20130504202515.GG20411@stodi.digitalkingdom.org> <55921D19-DB32-4D41-B6E9-1552B5BC9AB3@yahoo.com> <3A8DBDCA-994A-4A20-9BAD-A3A4F3561B49@yahoo.com> <5F42DC95-D2C4-4B0D-B018-A4BC82AAFB06@yahoo.com> From: ".arpis." Date: Mon, 6 May 2013 09:47:04 -0400 Message-ID: Subject: Re: [lojban] Robin retry: commands. To: Lojban X-Original-Sender: rpglover64@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of rpglover64@gmail.com designates 209.85.220.177 as permitted sender) smtp.mail=rpglover64@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: List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=089e013a0e16cf098904dc0cf0ce X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --089e013a0e16cf098904dc0cf0ce Content-Type: text/plain; charset=ISO-8859-1 If I understand {ga'i} correctly, it marks the referent to be of lower > rank. I don't think this is appropriate to mark it as a command. > {ga'i} marks the speaker to be higher rank; {ga'i nai} marks the speaker to be lower rank. > > {le'o}, according to jbovlaste is aggressiveness. If the commander > feels the need to be aggressive when giving commands, that hints to > some kind of inner shortcoming, so that he feels he needs to give the > command some additional force to compensate; and that makes it, in my > opinion, not a universal way to mark a "ko-bridi" as a command. > I agree. > > {e'i} is "feeling constraint" according to jbovlaste. According to the > Merrian-Webster dictionary (sorry, I'm not an English-native), > "constraint" is: > > [...] > > This seems to be the way the one receiving the command should feel, > not the commander's. > Yes, but the discussion is about whether to redefine (or at least to use dialectically) {e'i} to be more in line with {e'o}, {e'u}, and {e'a}. > > According to jbovlaste, {e'o} means "attitudinal: request - negative > request.". This doesn't look like a feeling, more like an intention; > the speaker's intention to make a request. There might be a plethora > of different feelings attached to this intention depending on the one > making the request. This is what we need to mark a "ko-bridi" as a > command. We need to clearly state the "ko-bridi" is a command. > > I'm no expert here, so I may be wrong, but my understanding on "ko > broda" is it means "make {ko broda} true", either as a request, or as > a command. The CLL makes a request explicit with "e'o ko broda". > > What about "e'onai ko broda"? {e'onai} means "negative request" > according to jbovlaste. So what is a negative request? My naive > interpretation: > > e'onai ko broda > negative request, make "ko broda" true > this is not a request, make "ko broda" true > this is an order, make "ko broda" true > > The experts here can explain why I am wrong.... > "negative request" seems to have been interpreted as "please don't" in the few uses I read of the few uses I found (here: http://www.lojban.org/corpus/ ) The BPFK proposed revision is to make {e'o nai} an offer. The problem with your logic for making {e'o nai} a command is that an analogous argument can be made for {e'u nai}. -- mu'o mi'e .arpis. -- 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. --089e013a0e16cf098904dc0cf0ce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


If I understand {ga'i} correctly, it marks the referent to be of lower<= br> rank. I don't think this is appropriate to mark it as a command.

{ga'i} marks the speaker to be higher ran= k; {ga'i nai} marks the speaker to be lower rank.
=A0

{le'o}, according to jbovlaste is aggressiveness. If the commander
feels the need to be aggressive when giving commands, that hints to
some kind of inner shortcoming, so that he feels he needs to give the
command some additional force to compensate; and that makes it, in my
opinion, not a universal way to mark a "ko-bridi" as a command.

I agree.

{e'i} is "feeling constraint" according to jbovlaste. Accordi= ng to the
Merrian-Webster dictionary (sorry, I'm not an English-native),
"constraint" is:

[...]

This seems to be the way the one receiving the command should feel,
not the commander's.

Yes, but the d= iscussion is about whether to redefine (or at least to use dialectically) {= e'i} to be more in line with {e'o}, {e'u}, and {e'a}.

According to jbovlaste, {e'o} means "attitudinal: request - negati= ve
request.". This doesn't look like a feeling, more like an intentio= n;
the speaker's intention to make a request. There might be a plethora of different feelings attached to this intention depending on the one
making the request. This is what we need to mark a "ko-bridi" as = a
command. We need to clearly state the "ko-bridi" is a command.
I'm no expert here, so I may be wrong, but my understanding on "ko=
broda" is it means "make {ko broda} true", either as a reque= st, or as
a command. The CLL makes a request explicit with "e'o ko broda&quo= t;.

What about "e'onai ko broda"? {e'onai} means "negati= ve request"
according to jbovlaste. So what is a negative request? My naive
interpretation:

e'onai ko broda
negative request, make "ko broda" true
this is not a request, make "ko broda" true
this is an order, make "ko broda" true

The experts here can explain why I am wrong....
<= br>
"negative request" seems to have been interpreted a= s "please don't" in the few uses I read of the few uses I fou= nd (here: http://www.lojban.org/c= orpus/)
The BPFK proposed revision is to make {e'o nai} an offer.
The problem with your logic for making {e'o nai} a command is th= at an analogous argument can be made for {e'u nai}.



--
mu'o mi'e .arpis.

--
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.
 
 
--089e013a0e16cf098904dc0cf0ce--