Received: from mail-pd0-f190.google.com ([209.85.192.190]:64434) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VzbKG-0007yg-4P for lojban-list-archive@lojban.org; Sat, 04 Jan 2014 16:12:31 -0800 Received: by mail-pd0-f190.google.com with SMTP id g10sf3969620pdj.27 for ; Sat, 04 Jan 2014 16:12:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=A0LLCrWcMMHcVarNINIFe/hhXiidukfOl7zKaim7ZYI=; b=ggYGbMJEXYYER4H62a9rx2Lb4Zh6PmuQKIwzaazuRAuPD9+grjga5V2jDtMxzLcHjX mgqjpNhV9+ScB+rlED2gPUFFUvGk3JucMK375NSuMLZ15cFeGu3l316A7bHgd7lGnsgC VXew6/2K9PyQoMjd7kt6eiXMM326rH5HYnl8XvhxZEZNxbYjERLKUdSzcx3pBygQN0iB ZPFWJiaRmLIhmyge0hwuYPbgjTWkm2WZnujeBTU31TJmXDuRWLIhpTomc24Am4DJ9pJm Zn8HVCskJ7Hl5cBn88kScZ6HOqjPyAefOFVZsVX0XDAj0MK8e8jurX8DB7A0ZpKXUzpn QZVg== X-Received: by 10.49.49.232 with SMTP id x8mr63998qen.13.1388880733776; Sat, 04 Jan 2014 16:12:13 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.49.40.194 with SMTP id z2ls5314523qek.23.gmail; Sat, 04 Jan 2014 16:12:13 -0800 (PST) X-Received: by 10.52.159.99 with SMTP id xb3mr34723258vdb.4.1388880733230; Sat, 04 Jan 2014 16:12:13 -0800 (PST) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [2607:f8b0:4001:c05::232]) by gmr-mx.google.com with ESMTPS id k45si2356675yhn.4.2014.01.04.16.12.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Jan 2014 16:12:13 -0800 (PST) Received-SPF: pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c05::232 as permitted sender) client-ip=2607:f8b0:4001:c05::232; Received: by mail-ig0-x232.google.com with SMTP id ut6so4163447igb.5 for ; Sat, 04 Jan 2014 16:12:13 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.50.70 with SMTP id a6mr10882329igo.1.1388880732937; Sat, 04 Jan 2014 16:12:12 -0800 (PST) Received: by 10.64.223.166 with HTTP; Sat, 4 Jan 2014 16:12:12 -0800 (PST) In-Reply-To: <52C880CB.9030601@gmx.de> References: <52C880CB.9030601@gmx.de> Date: Sat, 4 Jan 2014 22:12:12 -0200 Message-ID: Subject: Re: [lojban] {to'e ri'a} From: =?ISO-8859-1?Q?Felipe_Gon=E7alves_Assis?= To: lojban@googlegroups.com X-Original-Sender: felipeg.assis@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c05::232 as permitted sender) smtp.mail=felipeg.assis@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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=089e010d9d40b8e31d04ef2dfe47 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: ki'e sai selpa'i That is very clear! Maybe it should be posted somewhere? mu'o mi'e .asiz. [...] 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 (felipeg.assis[at]gmail.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 --089e010d9d40b8e31d04ef2dfe47 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable ki'e sai selpa'i That is very clear! Maybe it should be posted somewhere? mu'o mi'e .asiz. On 4 January 2014 18:44, selpa'i wrote: > la'o me. Felipe Gon=E7alves Assis .me cusku di'e > > I am confused. If the referent of the tagged sumti prevents the event >> described by the bridi, which event is there for the main brid to refer >> to? >> >> The page doesn't give examples. What would them be, if any? >> > > Since this is a topic that should be of interest to almost anyone, I will > try to give a brief summary not only of {NAhE + BAI}, but also of how all > the causation sumtcita work, and how they interact with NAhE and NAI, sin= ce > all this should be common knowledge (afterall it's needed on a daily basi= s). > > The idea is that each of the {to'e + causation sumtcita} give a different > shade of {fanta}, "to prevent". > > For example, {to'e ri'a} means the same as {to'e rinka}, just in sumtcita > form, and adding {nai} to a sumtcita creates a contradictory negation (i.= e. > {ri'a nai} -> {na rinka}). > > To begin with, using a causation sumtcita puts the tagged sumti into the > x1, and the main bridi into the x2. Here is an example: > > (1a) mi lebna ki'u lo nu mi xagji mutce > "I took it because I was so hungry." > > (1a) can be refactored as (1b). > > (1b) lo nu mi xagji mutce cu krinu lo nu [da'i nai] mi lebna > "My being very hungry was the reason I took it." > > (you need to make sure that the events are still getting asserted, which = I > will ignore here for the sake of simplicity) > > This transformation is very basic, but it helps us to undestand the > meaning of more complex sumtcita and their relationship to the main bridi= . > It's possible to attach NAhE as well as NAI, as in (2a) and (3a). > > (2a) mi klama mu'i nai lo nu lo speni cu zvati > "I didn't go because my wife was there." (but presumably for anothe= r > reason)" > > {mu'i nai} does not mean "despite" (anymore). (2b) shows why (2a) means > what it means now, using the same transformation as before: > > (2b) lo nu lo speni cu zvati cu na mukti lo nu mi klama > "My wife being there was not the motivation for my going there." > > Next, (3a) shows an example of {to'e}+causative. > > (3a) ? mi farlu to'e ri'a lo nu do jgari lo mi xance > "I fell, prevented by your holding my hand." > > Refactoring, we get (3b). > > (3b) lo nu do jgari lo mi xance cu to'e rinka lo nu mi farlu > "You holding my hand prevented my from falling." > > In (3a), we have the slightly strange case of a sumtcita removing the > assertion from the main bridi without any contradictory negation, which i= s > probably exactly what confused you. The strangeness disappears in (3b), > because rinka2 is no longer asserted by default. > > We can either conclude that (3a) is not a well-formed statement, or that > there exist certain sumtcita that can change the assertive force of the > main bridi on their own. The former would make {to'e ri'a} rather useless= , > as you noticed; the latter would be slightly unusual (not completely > unusual, cf. CAhA). > > In any case, while {to'e ri'a} itself might be of limited use, {to'e se > ri'a} is still perfectly usable, as for example in (3c): > > (3c) do jgari lo mi xance to'e se ri'a lo nu mi farlu > "You held my hand, thereby preventing me from falling." > > And once we add a {nai} to {to'e ri'a}, all is in order again, as shown b= y > (4a-b). > > (4a) mi dunda fi do to'e mu'i nai lo nu do ta'e darxi > "I will give it to you despite you always hitting me." > > And again, we can rewrite as (4b) to see how that meaning comes about. > > (4b) lo nu do ta'e darxi cu na to'e mukti lo nu mi dunda fi do > "You always hitting me does not demotivate me from giving it to you= ." > > All the above works in exactly the same way with the other BAI that can > integrate the main bridi as an argument of their base predicate, like {ta= i} > and {du'i}, so it's very important to learn this well. Plus, it's a > recurring theme in tense semantics, too. > > mi'e la selpa'i 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. > 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. For more options, visit https://groups.google.com/groups/opt_out. --089e010d9d40b8e31d04ef2dfe47 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
ki'e sai selpa'i

That is ve= ry clear! Maybe it should be posted somewhere?

mu'o
mi&= #39;e .asiz.


On 4 January 2014 18:44, selpa'i <seladwa@gmx.de> wrote:
la'o me. Felipe Gon=E7alves Assis .me cusku di'e
<= br>
I am confused. If the referent of the tagged sumti prevents the event
described by the bridi, which event is there for the main brid to refer to?=

The page doesn't give examples. What would them be, if any?

Since this is a topic that should be of interest to almost anyone, I will t= ry to give a brief summary not only of {NAhE + BAI}, but also of how all th= e causation sumtcita work, and how they interact with NAhE and NAI, since a= ll this should be common knowledge (afterall it's needed on a daily bas= is).

The idea is that each of the {to'e + causation sumtcita} give a differe= nt shade of {fanta}, "to prevent".

For example, {to'e ri'a} means the same as {to'e rinka}, just i= n sumtcita form, and adding {nai} to a sumtcita creates a contradictory neg= ation (i.e. {ri'a nai} -> {na rinka}).

To begin with, using a causation sumtcita puts the tagged sumti into the x1= , and the main bridi into the x2. Here is an example:

=A0(1a) mi lebna ki'u lo nu mi xagji mutce
=A0 =A0 =A0 "I took it because I was so hungry."

(1a) can be refactored as (1b).

=A0(1b) lo nu mi xagji mutce cu krinu lo nu [da'i nai] mi lebna
=A0 =A0 =A0 "My being very hungry was the reason I took it."

(you need to make sure that the events are still getting asserted, which I = will ignore here for the sake of simplicity)

This transformation is very basic, but it helps us to undestand the meaning= of more complex sumtcita and their relationship to the main bridi. It'= s possible to attach NAhE as well as NAI, as in (2a) and (3a).

=A0(2a) mi klama mu'i nai lo nu lo speni cu zvati
=A0 =A0 =A0 "I didn't go because my wife was there." (but pre= sumably for another reason)"

{mu'i nai} does not mean "despite" (anymore). (2b) shows why = (2a) means what it means now, using the same transformation as before:

=A0(2b) lo nu lo speni cu zvati cu na mukti lo nu mi klama
=A0 =A0 =A0 "My wife being there was not the motivation for my going t= here."

Next, (3a) shows an example of {to'e}+causative.

=A0(3a) ? mi farlu to'e ri'a lo nu do jgari lo mi xance
=A0 =A0 =A0 =A0 "I fell, prevented by your holding my hand."

Refactoring, we get (3b).

=A0(3b) lo nu do jgari lo mi xance cu to'e rinka lo nu mi farlu
=A0 =A0 =A0 "You holding my hand prevented my from falling."

In (3a), we have the slightly strange case of a sumtcita removing the asser= tion from the main bridi without any contradictory negation, which is proba= bly exactly what confused you. The strangeness disappears in (3b), because = rinka2 is no longer asserted by default.

We can either conclude that (3a) is not a well-formed statement, or that th= ere exist certain sumtcita that can change the assertive force of the main = bridi on their own. The former would make {to'e ri'a} rather useles= s, as you noticed; the latter would be slightly unusual (not completely unu= sual, cf. CAhA).

In any case, while {to'e ri'a} itself might be of limited use, {to&= #39;e se ri'a} is still perfectly usable, as for example in (3c):

=A0(3c) do jgari lo mi xance to'e se ri'a lo nu mi farlu
=A0 =A0 =A0 "You held my hand, thereby preventing me from falling.&quo= t;

And once we add a {nai} to {to'e ri'a}, all is in order again, as s= hown by (4a-b).

=A0(4a) mi dunda fi do to'e mu'i nai lo nu do ta'e darxi
=A0 =A0 =A0 "I will give it to you despite you always hitting me."= ;

And again, we can rewrite as (4b) to see how that meaning comes about.

=A0(4b) lo nu do ta'e darxi cu na to'e mukti lo nu mi dunda fi do =A0 =A0 =A0 "You always hitting me does not demotivate me from giving = it to you."

All the above works in exactly the same way with the other BAI that can int= egrate the main bridi as an argument of their base predicate, like {tai} an= d {du'i}, so it's very important to learn this well. Plus, it's= a recurring theme in tense semantics, too.

mi'e la selpa'i 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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--089e010d9d40b8e31d04ef2dfe47--