Received: from mail-yx0-f189.google.com ([209.85.213.189]:50181) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T3RaN-0003xG-Ug; Mon, 20 Aug 2012 06:00:14 -0700 Received: by yenq11 with SMTP id q11sf6296163yen.16 for ; Mon, 20 Aug 2012 05:59:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:sender:in-reply-to:references :from:date:message-id:subject:to:cc: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=cS+w0F1d8KsjwNOaZ3ApRywgKroMDG/OI4J40XmbbYg=; b=iAxy+utXlF5vqTJm/jJwDSFIOfDrk+rDzBO6iYlNU7NfJ1BeXT61Vs79fbmbcmV5o5 0QFzmMC3I9j8pwkP/RqCOU1HFHg7djdPpvpg/y/LhJuk2pW5oP8dA2HZIbrl1zHrQpMi lmTV32fWGjo5iqSAEH2cmoHynRZDOoLWpfXig= Received: by 10.236.170.7 with SMTP id o7mr14990yhl.3.1345467594335; Mon, 20 Aug 2012 05:59:54 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.236.141.208 with SMTP id g56ls1887833yhj.5.gmail; Mon, 20 Aug 2012 05:59:53 -0700 (PDT) Received: by 10.236.165.98 with SMTP id d62mr8624670yhl.40.1345467593481; Mon, 20 Aug 2012 05:59:53 -0700 (PDT) Received: by 10.236.165.98 with SMTP id d62mr8624665yhl.40.1345467593337; Mon, 20 Aug 2012 05:59:53 -0700 (PDT) Received: from mail-yx0-f178.google.com (mail-yx0-f178.google.com [209.85.213.178]) by gmr-mx.google.com with ESMTPS id y43si4350909yhi.2.2012.08.20.05.59.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2012 05:59:53 -0700 (PDT) Received-SPF: pass (google.com: domain of rpglover64@gmail.com designates 209.85.213.178 as permitted sender) client-ip=209.85.213.178; Received: by yenm2 with SMTP id m2so6024742yen.23 for ; Mon, 20 Aug 2012 05:59:53 -0700 (PDT) Received: by 10.60.30.195 with SMTP id u3mr10051240oeh.80.1345467593156; Mon, 20 Aug 2012 05:59:53 -0700 (PDT) MIME-Version: 1.0 Sender: lojban@googlegroups.com Received: by 10.76.132.2 with HTTP; Mon, 20 Aug 2012 05:59:32 -0700 (PDT) In-Reply-To: <16cb34d3-9617-4ec8-80aa-b59bb003051c@googlegroups.com> References: <23861931-0238-4ac4-a76e-60a8ea1b4d75@googlegroups.com> <502E37FF.5000500@gmx.de> <3c8e9a9a-2f9b-4c00-8052-ebe2605507c8@googlegroups.com> <4e4d586e-9b38-4367-9bc8-6ac533896be3@googlegroups.com> <683d860a-1d75-4f50-995e-0d14af26fe81@googlegroups.com> <16cb34d3-9617-4ec8-80aa-b59bb003051c@googlegroups.com> From: ".arpis." Date: Mon, 20 Aug 2012 08:59:32 -0400 Message-ID: Subject: Re: [lojban] {ko}, {xa'e}, {.e'u}, {e'o} To: la gleki Cc: lojban@googlegroups.com 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.213.178 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=e89a8ff1c038f2678404c7b21594 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --e89a8ff1c038f2678404c7b21594 Content-Type: text/plain; charset=ISO-8859-1 {.e'o do broda} is not an imperative. The request is not necessarily directed at the listener, nor is the statement explicit about who is expected to enact change, and it relies on the understanding that certain attitudinals can make a statement counterfactual (which is not universally accepted, IIRC); {.e'o ko broda} has only the first of these problems, and not much of that one. {doi mi ko sipna} makes perfect sense; there's no reason why the speaker and the listener need be different. I disagree with that translation on several levels: first of all, {ko} does not indicate obligation; second of all, the second statement is much vaguer than the first; third of all, I think {ko} is primitive enough in the language that a translation of it is not practical. On Mon, Aug 20, 2012 at 4:39 AM, la gleki wrote: > So nobody gave me examples of differences between {.e'o do broda} and > {.e'o ko broda}. > {ko} is officially translated as "imperative you, listener". Therefore, > {doi mi ko sipna} is na smudra. > > So for now I propose the following translation: > {ko broda} = {doi do do'u .e'i do broda}. > If so then {ko} is a nice abbreviation. > > > btw here is an extract from an old post by Jorge. > > On Tuesday, October 25, 1994 3:23:34 AM UTC+4, (unknown) wrote: >> >> >> I just realized that it is strange that we have a special word for >> the "command mode", but not for other similar things like the >> "intentional mode", or the "volitional mode", etc, which are handled >> with UIs, but could equally well have been something like {ko}. >> >> For example, say {xi'u} was the "intentional {mi}", then we'd have >> >> xi'u klama lo zarci ~ ai mi klama lo zarci >> >> just like >> >> ko klama lo zarci ~ e'o do klama lo zarci >> >> I don't see why the imperative is somehow more fundamental than the >> intentional, volitional, and all the others. >> >> It would be interesting to make a list of the attitudinals that change >> the sentence to opaque mode, like {ai} and {e'o}. >> >> This is assuming I'm right that {ai mi klama lo zarci} means >> "I intend that there be a store such that I go to it" and not >> "there is a store such that I intend to go to it". >> >> Jorge >> > > On Sunday, August 19, 2012 8:51:50 AM UTC+4, .arpis. wrote: > >> >> Wait a minute. arpis's example of a request using imperatives was in >>> English. In Lojban, the imperative meaning is always and only that of >>> giving an order/command, i.e., telling someone to do something (, which in >>> English also carries the expectation that the command will be obeyed), or >>> as hinted by someone, to cause the sentence to be true. >>> >> >> My point is that "telling someone to do something" is a much broader >> category of utterances than "order/command". >> >>> >>> stevo >>> >>>> >>>> One more question, whats the difference between {pe'u do}, {pe'u ko} >>>> and {ko .e'o}? >>>> >>>>> >>>>>>>>>> Hunh? An imperative *is *necessarily an order. That's the >>>>>>>>>> definition of imperative. >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sat, Aug 18, 2012 at 11:32 AM, la gleki < >>>>>>>>>>> gleki.is...@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> {.e'u} and {ko} largely differ in the fact that after >>>>>>>>>>>> insubmission after {ko} you might be executed by your commander whereas >>>>>>>>>>>> after {.e'u} you would probably survive. zo'o >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> "Insubmission" is a new and useful word for me. Thanks for using >>>>>>>>>> it! >>>>>>>>>> >>>>>>>>>> stevo >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Friday, August 17, 2012 4:24:31 PM UTC+4, selpa'i wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Am 17.08.2012 13:47, schrieb Paul Predkiewicz: >>>>>>>>>>>>> > but {xa'e} is a rafsi of {xance}, how would you use it to >>>>>>>>>>>>> say such >>>>>>>>>>>>> > things as "let's go"? >>>>>>>>>>>>> >>>>>>>>>>>>> -xa'e- is the rafsi, but xa'e as a cmavo is a LAhE (even >>>>>>>>>>>>> though I wish >>>>>>>>>>>>> it was UI) that makes it so that the sumti it's used on is >>>>>>>>>>>>> treated as if >>>>>>>>>>>>> it was ko, i.e. a third-person command. >>>>>>>>>>>>> >>>>>>>>>>>>> xa'e lo gerku cu cliva >>>>>>>>>>>>> "The dogs shall leave!" >>>>>>>>>>>>> "May the dogs leave!" >>>>>>>>>>>>> "I want the dogs to leave." >>>>>>>>>>>>> >>>>>>>>>>>>> Whether it's very useful is another question. {.e'u} will >>>>>>>>>>>>> usually be >>>>>>>>>>>>> enough for cohortatives at least. >>>>>>>>>>>>> >>>>>>>>>>>>> mu'o mi'e la selpa'i >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo >>>>>>>>>>>>> lejbo >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>> 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/**ms******g/lojban/-/uwcGoYr3b0UJ >>>>>>>>>>>> . >>>>>>>>>>>> >>>>>>>>>>>> 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******/lojban?hl=en >>>>>>>>>>>> . >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> mu'o mi'e .arpis. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>> Google Groups "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******/lojban?hl=en >>>>>>>>>>> . >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>> Google Groups "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******/lojban?hl=en >>>>>>>>>> . >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> mu'o mi'e .arpis. >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> mu'o mi'e .arpis. >>>>>>> >>>>>>> >>>>> >>>>> >>>>> -- >>>>> mu'o mi'e .arpis. >>>>> >>>>> -- >>>> 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/-/uEHyocerN1kJ >>>> . >>>> >>>> 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/lojban?hl=en . >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "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/lojban?hl=en . >>> >> >> >> >> -- >> mu'o mi'e .arpis. >> >> -- mu'o mi'e .arpis. -- 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@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --e89a8ff1c038f2678404c7b21594 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable {.e'o do broda} is not an imperative. The request is not necessarily di= rected at the listener, nor is the statement explicit about who is expected= to enact change, and it relies on the understanding that certain attitudin= als can make a statement counterfactual (which is not universally accepted,= IIRC); {.e'o ko broda} has only the first of these problems, and not m= uch of that one.

{doi mi ko sipna} makes perfect sense; there's no reason why the sp= eaker and the listener need be different.

I disagree with that trans= lation on several levels: first of all, {ko} does not indicate obligation; = second of all, the second statement is much vaguer than the first; third of= all, I think {ko} is primitive enough in the language that a translation o= f it is not practical.

On Mon, Aug 20, 2012 at 4:39 AM, la gleki <gleki.is.my.name@gmail.com> wrote:
So nobody gave me examples of differences between {.e'o do broda} and {= .e'o ko broda}.
{ko} is officially translated as "imperative y= ou, listener". Therefore, {doi mi ko sipna} is na smudra.

So for now I propose the following translation:
{k= o broda} =3D {doi do do'u .e'i do broda}.
If so then {ko}= is a nice abbreviation.


btw here i= s an extract from an old post by Jorge.

On Tuesday, October 25, 1994 3:23:34 AM UTC+4, (unknown= ) wrote:

I just realized that it is strange that we have a special word forthe "command mode", but not for other similar things like the"intentional mode", or the "volitional mode", etc, wh= ich are handled
with UIs, but could equally well have been something like {ko}.

For e= xample, say {xi'u} was the "intentional {mi}", then we'd = have

=A0 =A0 =A0 =A0 xi'u klama lo zarci =A0~ =A0 ai mi klama lo = zarci

just like

=A0 =A0 =A0 =A0 ko klama lo zarci =A0 =A0~ =A0 e'o d= o klama lo zarci

I don't see why the imperative is somehow more f= undamental than the
intentional, volitional, and all the others.

I= t would be interesting to make a list of the attitudinals that change
the sentence to opaque mode, like {ai} and {e'o}.

This is assumin= g I'm right that {ai mi klama lo zarci} means
"I intend that th= ere be a store such that I go to it" and not
"there is a store= such that I intend to go to it".

Jorge


On Sunday, August 19, 2012 8= :51:50 AM UTC+4, .arpis. wrote:

Wait a minute. arpis's example of a request using im= peratives was in English. In Lojban, the imperative meaning is always and o= nly that of giving an order/command, i.e., telling someone to do something = (, which in English also carries the expectation that the command will be o= beyed), or as hinted by someone, to cause the sentence to be true. =A0

My point is that "telling someone to do so= mething" is a much broader category of utterances than "order/com= mand".

stevo

One more question, whats the difference between {pe'u = do}, {pe'u ko} and {ko .e'o}?

Hunh? An imp= erative is necessarily an order. That's the definition of impera= tive.=A0

On Sat, Aug 18, 2012 at 11:32 AM, la gleki <gleki.is...@gmail.com> wrote:
{.e'u} and {ko} largely differ in the fa= ct that after insubmission after {ko} you might be executed by your command= er whereas after {.e'u} you would probably survive. zo'o

"Insubmission= " is a new and useful word for me. Thanks for using it!

=
stevo=A0


On Friday, August 17, 2012 4:24:31 PM UTC+4, selpa'i wrote:Am 17.08.2012 13:47, schrieb Paul Predk= iewicz:
> but {xa'e} is a rafsi of {xance}, how would you use it to say = such=20
> things as "let's go"?

-xa'e- is the rafsi, but xa'e as a cmavo is a LAhE (even though= I wish=20
it was UI) that makes it so that the sumti it's used on is treated = as if=20
it was ko, i.e. a third-person command.

=A0 =A0 =A0xa'e lo gerku cu cliva
=A0 =A0 =A0"The dogs shall leave!"
=A0 =A0 =A0"May the dogs leave!"
=A0 =A0 =A0"I want the dogs to leave."

Whether it's very useful is another question. {.e'u} will usual= ly be=20
enough for cohortatives at least.

mu'o mi'e la selpa'i

--=20
pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo

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

=20 To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

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



=
--
mu'o mi'e .arpis.
<= /span>


--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

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

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

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



--
= mu'o mi'e .arpis.




--
mu&#= 39;o mi'e .arpis.




-- mu'o mi'e .arpis.

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

=20 To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

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

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@google= groups.com.

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



--
mu'o mi= 'e .arpis.




--
mu'o mi'e .arpis.

--
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.
--e89a8ff1c038f2678404c7b21594--