From lojban+bncCOjSjrXVGBD_7cjpBBoEUiGRYQ@googlegroups.com Sat Jan 15 16:08:48 2011 Received: from mail-gw0-f61.google.com ([74.125.83.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PeGAl-0005M3-DI; Sat, 15 Jan 2011 16:08:48 -0800 Received: by gwj17 with SMTP id 17sf2900475gwj.16 for ; Sat, 15 Jan 2011 16:08:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature: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:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=v+NnSekJGjF1FwkSvKNVpUf1IOcooCyxu0qtCe6Ro60=; b=iZ6nubWpDofKbOKJlFQUcVi9TiGkcbescOzJOmR2hwpNLfcqy0ofZhjxIcjJRTk6pD TbWkGiM4Pa2Cm9WzmAKB10cxO5OGNOVOMU2gDMfZAfSDnxGlrzAJH4CRzdmrai70T8Bj HfoYe36zVMFaY0zQsQlD/2xCsynRnb1b983Vc= 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-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; b=LKncJyzYtcnWJCP7iasvOPjl5J5vvWxFrHTJ4AARmIfIs9bRS2VpUi9DwSAdIhR4YP 416WFpH1vNpBkqAezUN3iPvSJEZu5fiJMObb/slO5wo9pXbeIBf2EEP6NzyYHTDv3G8Y 46M7zWGSLNKIWdJgbmaaLfq8k0YB81h1Xh4GA= Received: by 10.101.152.28 with SMTP id e28mr69520ano.14.1295136511635; Sat, 15 Jan 2011 16:08:31 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.231.76.165 with SMTP id c37ls3854736ibk.3.p; Sat, 15 Jan 2011 16:08:30 -0800 (PST) Received: by 10.231.14.67 with SMTP id f3mr678762iba.15.1295136510932; Sat, 15 Jan 2011 16:08:30 -0800 (PST) Received: by 10.231.14.67 with SMTP id f3mr678761iba.15.1295136510904; Sat, 15 Jan 2011 16:08:30 -0800 (PST) Received: from mail-iw0-f179.google.com (mail-iw0-f179.google.com [209.85.214.179]) by gmr-mx.google.com with ESMTPS id cu19si715268ibb.1.2011.01.15.16.08.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 15 Jan 2011 16:08:29 -0800 (PST) Received-SPF: pass (google.com: domain of lukeabergen@gmail.com designates 209.85.214.179 as permitted sender) client-ip=209.85.214.179; Received: by mail-iw0-f179.google.com with SMTP id 12so3786127iwb.10 for ; Sat, 15 Jan 2011 16:08:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.36.198 with SMTP id u6mr2420917ibd.100.1295136509662; Sat, 15 Jan 2011 16:08:29 -0800 (PST) Received: by 10.231.200.148 with HTTP; Sat, 15 Jan 2011 16:08:29 -0800 (PST) In-Reply-To: References: Date: Sat, 15 Jan 2011 19:08:29 -0500 Message-ID: Subject: Re: [lojban] question about ku From: Luke Bergen To: lojban@googlegroups.com X-Original-Sender: lukeabergen@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lukeabergen@gmail.com designates 209.85.214.179 as permitted sender) smtp.mail=lukeabergen@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: List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=0021cc0223829816b20499eb7785 --0021cc0223829816b20499eb7785 Content-Type: text/plain; charset=ISO-8859-1 This is the meat of my question. My initial guess was that {ba} expects a sumti as is the case with {mi citka lo plise ba lo nu mi xagji} and that putting it before the selbri or terminating it with {ku} is just a way of saying "forget that sumti, it's zo'e or something". But the only way of getting that is for there to be an implicit {lo} OR {ku} is special in that it terminates tags like LE, BAI, BA, (and FA?). But that doesn't seem right because then why wouldn't the ku be necessary in the case of {mi ba [ku] citka lo plise}? I wish I understood PEG better. On Sat, Jan 15, 2011 at 6:53 PM, Ian Johnson wrote: > Still no idea why ku can terminate two completely unrelated selma'o, > though. > > mu'o mi'e .latros. > > On Sat, Jan 15, 2011 at 6:11 PM, Luke Bergen wrote: > >> I don't know why it just occurred to me but... what exactly is "ku" >> terminatiging in "baku mi citka"? Is there an implicit "lo" so that parsers >> see this as /really/ being something like "baloku mi citka"? Or is ku just >> able to terminate "ba"? I didn't know that BA had a terminator... either >> way something feels strange. >> >> -- >> 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. >> > > -- > 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. > -- 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. --0021cc0223829816b20499eb7785 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This is the meat of my question. =A0My initial guess was that {ba} expects = a sumti as is the case with {mi citka lo plise ba lo nu mi xagji} and that = putting it before the selbri or terminating it with {ku} is just a way of s= aying "forget that sumti, it's zo'e or something". =A0But= the only way of getting that is for there to be an implicit {lo} OR {ku} i= s special in that it terminates tags like LE, BAI, BA, (and FA?). =A0But th= at doesn't seem right because then why wouldn't the ku be necessary= in the case of {mi ba [ku] citka lo plise}? =A0

I wish I understood PEG better.

On Sat, Jan 15, 2011 at 6:53 PM, Ian Johnson <blindbravado@gmail.com> wrote:
Still no idea why ku can terminate two comp= letely unrelated selma'o, though.

mu'o mi'e .latros.

On Sat, Jan 15, 2011 at 6:= 11 PM, Luke Bergen <lukeabergen@gmail.com> wrote:

I don't know why it just occurred=A0 to me but... what exactly is &= quot;ku" terminatiging in "baku mi citka"?=A0 Is there an im= plicit "lo" so that parsers see this as /really/ being something = like "baloku mi citka"?=A0 Or is ku just able to terminate "= ba"?=A0 I didn't know that BA had a terminator... either way somet= hing feels strange.

--
You received this message because you are subscribed to the Google Groups &= quot;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/lojba= n?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 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/lojba= n?hl=3Den.

--
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.
--0021cc0223829816b20499eb7785--