Received: from mail-wy0-f189.google.com ([74.125.82.189]:35433) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1REYKQ-0001ke-UJ; Thu, 13 Oct 2011 20:21:07 -0700 Received: by wyh11 with SMTP id 11sf4028980wyh.16 for ; Thu, 13 Oct 2011 20:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf: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:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=hpqSLo1p9EBQ+W+q05TAx5ndwdepgFkBqPX3x2rYJhs=; b=bb7+J1CpjQeD3m3M4T9085HDKm3s3qZa6bZz+wiLdB6dS3IysFXnr0eU7OuWQtGt/f 1vdiCmmGdNXjS7rqOBYYWDBAiYUhq8X1bdumeF66V+yer2/T5Jy/kHM/d1nSTnasekWn 4uzZvbMmUUcLGOzHTeAaJEGGtOU/liFeMrZ9s= Received: by 10.216.170.12 with SMTP id o12mr906586wel.9.1318562448677; Thu, 13 Oct 2011 20:20:48 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.227.94.67 with SMTP id y3ls1955070wbm.1.gmail; Thu, 13 Oct 2011 20:20:47 -0700 (PDT) Received: by 10.216.156.135 with SMTP id m7mr41119wek.11.1318562447369; Thu, 13 Oct 2011 20:20:47 -0700 (PDT) Received: by 10.216.156.135 with SMTP id m7mr41118wek.11.1318562447346; Thu, 13 Oct 2011 20:20:47 -0700 (PDT) Received: from mail-ww0-f48.google.com (mail-ww0-f48.google.com [74.125.82.48]) by gmr-mx.google.com with ESMTPS id d7si3972467wbp.2.2011.10.13.20.20.47 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Oct 2011 20:20:47 -0700 (PDT) Received-SPF: pass (google.com: domain of eyeonus@gmail.com designates 74.125.82.48 as permitted sender) client-ip=74.125.82.48; Received: by wwe32 with SMTP id 32so1813498wwe.5 for ; Thu, 13 Oct 2011 20:20:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.5.135 with SMTP id 7mr572788wbv.86.1318562447189; Thu, 13 Oct 2011 20:20:47 -0700 (PDT) Received: by 10.227.5.138 with HTTP; Thu, 13 Oct 2011 20:20:47 -0700 (PDT) In-Reply-To: <1318557021.1886.10.camel@fagricipni-desktop> References: <0bee931d21bbb12d49b2029731cfac07.squirrel@QuestMail.FutureQuest.net> <1318557021.1886.10.camel@fagricipni-desktop> Date: Thu, 13 Oct 2011 21:20:47 -0600 Message-ID: Subject: Re: [lojban] fagricipni's Translations #1 From: Jonathan Jones To: lojban@googlegroups.com X-Original-Sender: eyeonus@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of eyeonus@gmail.com designates 74.125.82.48 as permitted sender) smtp.mail=eyeonus@gmail.com; dkim=pass (test mode) 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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=00248c0eeb484767c704af39bef0 X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --00248c0eeb484767c704af39bef0 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Oct 13, 2011 at 7:50 PM, H. Felton wrote: > I've re-read http://dag.github.com/cll/5/7/ > > On Tue, 2011-10-11 at 11:13 -0600, Jonathan Jones wrote: > > You don't need the be'o. > > This bit is accurate; though. > > > It's only required when linking multiple sumti, or in other words, > it's only needed when using bei. > > But, according to the discussion after > this example(http://dag.github.com/cll/5/7/#e10 ), your rule is > not entirely accurate; there are other cases where the "be'o" > cannot be elided. Since this is the case, I will include > "be'o" in at least some places where it could be elided until I > fully understand the rules for its elision. > Ah, I hadn't thought of the {lo broda be lo brode brodi} case, in which be'o is needed to distinguish between {lo brode brodi} and {lo brode ku brodi}. I wasn't aware of the NOI case at all. -- mu'o mi'e .aionys. .i.e'ucai ko cmima lo pilno be denpa bu .i doi.luk. mi patfu do zo'o (Come to the Dot Side! Luke, I am your father. :D ) -- 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. --00248c0eeb484767c704af39bef0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Oct 13, 2011 at 7:50 PM, H. Felton <lojban707@fagr= icipni.com> wrote:
I've re-read http://dag.github.com/cll/5/7/

On Tue, 2011-10-11 at 11:13 -0600, Jonathan Jones wrote:
> You don't need the be'o.

This bit is accurate; though.

> It's only required when linking multiple sumti, or in other words,=
it's only needed when using bei.

But, according to the discussion after
this example(http://dag.github.com/cll/5/7/#e10 ), your rule is
not entirely accurate; there are other cases where the "be'o"=
cannot be elided. =A0Since this is the case, I will include
"be'o" in at least some places where it could be elided until= I
fully understand the rules for its elision.

Ah, I= hadn't thought of the {lo broda be lo brode brodi} case, in which be&#= 39;o is needed to distinguish between {lo brode brodi} and {lo brode ku bro= di}.

I wasn't aware of the NOI case at all.

--
mu'o mi= 9;e .aionys.

.i.e'ucai ko cmima lo pilno be denpa bu .i doi.luk.= mi patfu do zo'o
(Come to the Dot Side! Luke, I am your father. :D = )

--
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.
--00248c0eeb484767c704af39bef0--