Received: from mail-la0-f59.google.com ([209.85.215.59]:34326) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1Ya8nF-0005E8-7A for lojban-list-archive@lojban.org; Mon, 23 Mar 2015 13:17:57 -0700 Received: by lams18 with SMTP id s18sf48112156lam.1 for ; Mon, 23 Mar 2015 13:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type: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; bh=RmbGK76c6yy7pog2SMUZ5bPr5TZT5FFf0BTSWgy1QKg=; b=FlDpOD8T9HcDmJzZtHStJiHDfn85Zac9AHKRqIBFjdYEg8Ufsj5xJxA4w4+kdia10v ApnjQ4ZuejPp3UD5lsWxZhzEAAmPJ489flQ25cnX+4jKh5PEUCo8IFdzOmK+o7gJdiwi sNbYuNNf1GHaFjGjkAegv6KWpN4Suz1Z+wMOgKr7BurPpsejRdcWtWGxFeZIJffBgnjT ciLC9nAfIwZ+joo1EI6DIKGPClJE311qJAljxNSC5bxvxuCGDPejNoCSJzh7dM+SYr9L 9p80OBhapPUH3OQhPjmk55p346q+t0pnR2HGkDBXwcy3GGYwnu7yki4HXh+BAq1yLDCe Utng== X-Received: by 10.180.8.229 with SMTP id u5mr67230wia.19.1427141862260; Mon, 23 Mar 2015 13:17:42 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.96.106 with SMTP id dr10ls865886wib.20.canary; Mon, 23 Mar 2015 13:17:41 -0700 (PDT) X-Received: by 10.181.12.74 with SMTP id eo10mr2394200wid.2.1427141861849; Mon, 23 Mar 2015 13:17:41 -0700 (PDT) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com. [2a00:1450:400c:c05::233]) by gmr-mx.google.com with ESMTPS id el6si551219wib.0.2015.03.23.13.17.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2015 13:17:41 -0700 (PDT) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c05::233 as permitted sender) client-ip=2a00:1450:400c:c05::233; Received: by mail-wi0-x233.google.com with SMTP id g7so57282644wib.1 for ; Mon, 23 Mar 2015 13:17:41 -0700 (PDT) X-Received: by 10.194.190.10 with SMTP id gm10mr1334901wjc.91.1427141861777; Mon, 23 Mar 2015 13:17:41 -0700 (PDT) Received: from [192.168.0.102] (95-210-212-178.ip.skylogicnet.com. [95.210.212.178]) by mx.google.com with ESMTPSA id w3sm12761186wiz.5.2015.03.23.13.17.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2015 13:17:41 -0700 (PDT) Message-ID: <551074C8.10306@gmail.com> Date: Mon, 23 Mar 2015 21:17:12 +0100 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] On the meanings of the causal gismu References: <550EC85E.7070206@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------030700010400060500080408" X-Original-Sender: ilmen.pokebip@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c05::233 as permitted sender) smtp.mail=ilmen.pokebip@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: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - This is a multi-part message in MIME format. --------------030700010400060500080408 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable On 23/03/2015 16:31, Jorge Llamb=C3=ADas wrote: > > On Sun, Mar 22, 2015 at 10:49 AM, Ilmen > wrote: > > > =E2=80=94 What is the semantic difference between {selja'e}, {rinka} = and > {bapli}? Does {selja'e} express a weaker relation than that > expressed by {rinka}? > > > Setting aside the "sumti raising" issue, I would say "rinka" and=20 > "selja'e" are pretty much equivalent. It's hard to think of cases=20 > where one works but not the other. > I've always though of {selja'e} as being a somewhat looser / less strict=20 relation than {rinka}, as if it was something like {x1 .a lo selpau be=20 x1 cu rinka x2}, so that one can say {lo nu carvi cu selja'e lo nu mi na=20 klama}, where the connection between the two events is not clearly=20 explained, and where it seems that "lo nu carvi" is not the only factor=20 that have determined the event {lo nu mi klama} not to occur (another=20 plausible factor could be "mi na djica lo nu mi se carvi"). But this impression that {selja'e} is looser than {rinka} is perhaps=20 subjective, and maybe {rinka} can be used just as vaguely. > "banzu" is not the same as "rinka". ro da zo'u da banzu da .i ku'i na=20 > ku ro da zo'u da rinka da .i la'a no da zo'u da rinka da .i ro da poi=20 > kacna'u zo'u lo du'u da pilji li vo lo kacna'u cu banzu lo du'u da=20 > pilji li re lo kacna'u .i ku'i pe'i lo du'u pilji li vo cu na rinka lo=20 > du'u pilji li re > But, isn't this second example (that with {kacna'u}) what {nibli} is=20 for? I thought that banzu-nu (the version of {banzu} that parallels=20 {sarcu}) was the event equivalent of {nibli}. mi'e la .ilmen. mu'o --=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/d/optout. --------------030700010400060500080408 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 23/03/2015 16:31, Jorge Llamb=C3=ADas wrote:

On Sun, Mar 22, 2015 at 10:49 AM, Ilmen <i= lmen.pokebip@gmail.com> wrote:

=E2=80=94 What is the semantic difference between {selja'e}= , {rinka} and {bapli}? Does {selja'e} express a weaker relation than that expressed by {rinka}?

Setting aside the "sumti raising" issue, I would say "rinka" and "selja'e" are pretty much equivalent. It's hard to think of cases where one works but not the other.

I've always though of {selja'e} as being a somewhat looser / less strict relation than {rinka}, as if it was something like {x1 .a lo selpau be x1 cu rinka x2}, so that one can say {lo nu carvi cu selja'e lo nu mi na klama}, where the connection between the two events is not clearly explained, and where it seems that "lo nu carvi" is not the only factor that have determined the event {lo nu mi klama} not to occur (another plausible factor could be "mi na djica lo nu mi se carvi").
But this impression that {selja'e} is looser than {rinka} is perhaps subjective, and maybe {rinka} can be used just as vaguely.

"banzu" is not the same as "rinka". ro da zo'u da banzu da .i ku'i na ku ro da zo'u da rinka da .i la'a no da zo'u da rinka da .i ro da poi kacna'u zo'u lo du'u da pilji li vo lo kacna'u cu banzu lo du'u da pilji li re lo kacna'u .i ku'i pe'i lo du'u pilji li vo cu na rinka lo du'u pilji li re

But, isn't this second example (that with {kacna'u}) what {nibli} is for? I thought that banzu-nu (the version of {banzu} that parallels {sarcu}) was the event equivalent of {nibli}.

mi'e la .ilmen. 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+unsub= scribe@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 http= s://groups.google.com/d/optout.
--------------030700010400060500080408--