Received: from mail-pv0-f189.google.com ([74.125.83.189]) by chain.digitalkingdom.org with esmtp (Exim 4.71) (envelope-from ) id 1OBtKB-0003AP-Tv; Tue, 11 May 2010 10:33:02 -0700 Received: by pvh1 with SMTP id 1sf179853pvh.16 for ; Tue, 11 May 2010 10:32:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:mime-version:received:received :in-reply-to:references:date:message-id:subject:from:to :x-original-authentication-results:x-original-sender:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=W8ZexeVeBNh9homcQkeP2MN6/BBBKLfBriUI4Z+lSm4=; b=V35+J0KTmyIwTo5gf85INx7EC4yWlFf6ODMH2TXViQfwwQwKYYyrQ5D4TvyE4n/6wp XPUbpbgj8eRU/Dh4PdRx5mrVRtqfAIzfuge2PgoXkZCByjja68GESjkGfgokRsOnEJAL c5RiUVp8E/LCx72mbdXbYjrzXB/CbE9f0DOIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from:to:x-original-authentication-results :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; b=WST4v7+KX6eg0t1CdjaL1IVMSCpxTJV076Z3FEfkTvPaU2nI6xF6ILgaGLEfMfKhrm 6vjsoPO0vf+T2Rz7MzdlAiu5xHt0a0vrKUfTPPs7TV+p9D36bblcQHqGr0AM+BvKCybf qBRc0teKH2nCwZ7Os4nG11VxOCrKVbUqiCt4c= Received: by 10.115.100.11 with SMTP id c11mr805778wam.23.1273599166956; Tue, 11 May 2010 10:32:46 -0700 (PDT) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.115.38.17 with SMTP id q17ls24524237waj.0.p; Tue, 11 May 2010 10:32:46 -0700 (PDT) Received: by 10.115.115.4 with SMTP id s4mr1421439wam.27.1273599164564; Tue, 11 May 2010 10:32:44 -0700 (PDT) Received: by 10.115.115.4 with SMTP id s4mr1421438wam.27.1273599164524; Tue, 11 May 2010 10:32:44 -0700 (PDT) Received: from mail-vw0-f43.google.com (mail-vw0-f43.google.com [209.85.212.43]) by gmr-mx.google.com with ESMTP id u10si6359390wak.2.2010.05.11.10.32.43; Tue, 11 May 2010 10:32:43 -0700 (PDT) Received-SPF: pass (google.com: domain of lukeabergen@gmail.com designates 209.85.212.43 as permitted sender) client-ip=209.85.212.43; Received: by vws15 with SMTP id 15so7344400vws.2 for ; Tue, 11 May 2010 10:32:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.63.78 with SMTP id a14mr4764129vci.4.1273599162656; Tue, 11 May 2010 10:32:42 -0700 (PDT) Received: by 10.220.94.77 with HTTP; Tue, 11 May 2010 10:32:42 -0700 (PDT) In-Reply-To: References: <4BE97DBB.4060404@perpetuum-immobile.de> Date: Tue, 11 May 2010 13:32:42 -0400 Message-ID: Subject: Re: [lojban-beginners] sei vs to From: Luke Bergen To: lojban-beginners@googlegroups.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lukeabergen@gmail.com designates 209.85.212.43 as permitted sender) smtp.mail=lukeabergen@gmail.com; dkim=pass (test mode) header.i=@gmail.com X-Original-Sender: lukeabergen@gmail.com Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: lojban-beginners@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=e0cb4e88751dad2f4b048654e92b Content-Length: 6923 --e0cb4e88751dad2f4b048654e92b Content-Type: text/plain; charset=ISO-8859-1 oops, sorry, I wanted my example to go: {la djan cu citka lo plise to mi ji'a nelci py}. In my first example {sei} would feel perfectly natural while not so much in the revised example. On Tue, May 11, 2010 at 1:30 PM, Luke Bergen wrote: > Also, I don't know if they're defined this way precisely, but when I see > {sei} I usually get the connotation that it's more closely related to the > text at hand. While to ... toi feels much more like it could be about > anything, e.g. {la djan cu citka le plise to mi ji'a nelci toi} while this > feels like it would be inappropriate for {sei}. > > That could just be a distinction from usage though and have nothing to do > with the actual grammar of either. > > > On Tue, May 11, 2010 at 1:25 PM, tijlan wrote: > >> On 11 May 2010 16:57, Luke Bergen wrote: >> >>> That brings up a question for me. In that sentence that you gave tijlan, >>> what about the text tells us that the {fi lo cukta...} applies to the >>> {prali} and not to the {pensi}? Does {sei} take a bridi, a selbri, or >>> something else? What terminates a {sei} or is the idea of terminating {sei} >>> as absurd as terminating {zo}? I've perused the CLL but {sei} isn't >>> documented very well there from what I have found. >> >> >> {sei}'s scope ends right after the end of the last selbri that it >> contains. So, no sumti or tag following that in-sei selbri becomes part of >> the sei scope, unless they are attached to it with {be}. >> >> One little advantage of {sei} is that its terminator {se'u} is elidable in >> more occasions than {to}'s {toi} is: >> >> ma prali sei la alis pensi [se'u] ti >> ma prali to la alis pensi toi ti >> >> But an easy change in the word order would offset that advantage: >> >> ma prali ti sei la alis pensi [se'u] >> ma prali ti to la alis pensi [toi] >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Lojban Beginners" group. >> To post to this group, send email to lojban-beginners@googlegroups.com. >> To unsubscribe from this group, send email to >> lojban-beginners+unsubscribe@googlegroups.com >> . >> For more options, visit this group at >> http://groups.google.com/group/lojban-beginners?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Lojban Beginners" group. To post to this group, send email to lojban-beginners@googlegroups.com. To unsubscribe from this group, send email to lojban-beginners+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban-beginners?hl=en. --e0cb4e88751dad2f4b048654e92b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable oops, sorry, I wanted my example to go: {la djan cu citka lo plise to mi ji= 'a nelci py}. =A0In my first example {sei} would feel perfectly natural= while not so much in the revised example.

On Tue, May 11, 2010 at 1:30 PM, Luke Bergen <lukeabergen@gmail.com> wrot= e:
Also, I don't know if they're defined this way precisely, but when = I see {sei} I usually get the connotation that it's more closely relate= d to the text at hand. =A0While to ... toi feels much more like it could be= about anything, e.g. {la djan cu citka le plise to mi ji'a nelci toi} = while this feels like it would be=A0inappropriate=A0for {sei}.

That could just be a distinction from usage though and have = nothing to do with the actual grammar of either.


On Tue, May 11, 2010 at 1:25 PM,= tijlan <jbotijlan@gmail.com> wrote:
On 11 May 20= 10 16:57, Luke Bergen <lukeabergen@gmail.com> wrote:
That brings up a question for me. =A0In that sentence that you gave tijlan,= what about the text tells us that the {fi lo cukta...} applies to the {pra= li} and not to the {pensi}? =A0Does {sei} take a bridi, a selbri, or someth= ing else? =A0What terminates a {sei} or is the idea of terminating {sei} as= absurd as terminating {zo}? =A0I've perused the CLL but {sei} isn'= t documented very well there from what I have found.

{sei}'s scope ends right after the end of the last selbr= i that it contains. So, no sumti or tag following that in-sei selbri become= s part of the sei scope, unless they are attached to it with {be}.

One little advantage of {sei} is that its terminator {se'u} is elid= able in more occasions than {to}'s {toi} is:

=A0ma prali sei la alis pensi [se'u] ti
=A0ma prali to la alis p= ensi toi ti

But an easy change in the word order would offset that a= dvantage:

=A0ma prali ti sei la alis pensi [se'u]
=A0ma prali= ti to la alis pensi [toi]

--
You received this message because you are subscribed to the Google Groups &= quot;Lojban Beginners" group.
To post to this group, send email to lojban-beginners@googlegroups.com.
To unsubscribe from this group, send email to lojban-beginners+un= subscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/g= roup/lojban-beginners?hl=3Den.


--
You received this message because you are subscribed to the Google Groups "= Lojban Beginners" group.
To post to this group, send email to lojban-beginners@googlegroups.com.
To unsubscribe from this group, send email to lojban-beginners+unsubscribe@= googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban= -beginners?hl=3Den.
--e0cb4e88751dad2f4b048654e92b--