From lojban+bncCOjSjrXVGBD-2q3oBBoEDXwxNg@googlegroups.com Fri Dec 17 06:02:59 2010 Received: from mail-gy0-f189.google.com ([209.85.160.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PTatV-0004aH-NU; Fri, 17 Dec 2010 06:02:58 -0800 Received: by gyb11 with SMTP id 11sf403338gyb.16 for ; Fri, 17 Dec 2010 06:02:43 -0800 (PST) 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-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=u+oXX0QRw27FJTsri6R9S3ONovoJVG6/C2iNFbxg6ck=; b=AY9+PVqdx8NXQ3h5Q1IcflIaJbiTykZBr+lKZkr7anZ3snu9Nj+pbN2pmO6XR4mY74 ZzMuqgOGnY1sPI7KyyA98XjrzYZM/Lddk1evi69yP02ed26YPho3CSKwFjsbc+r9QfM2 D3MAs9NS5O04CsIbL5S2fQxq4L/r3cko9v17Y= 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=s2r/0dzyOnaRCbk/TXC9zeu0k+HNyRK1dVDnxLbEa5G0TmlQw2aBAhb3IS2/Lge/Dm 7Fy1p1ejyCUWnERDVgfnq2J5cqWIIFmZI0v263F9RtOZv1luN6w+o27BmE0urU33VPnn bvXWucYYygDyfYJ8kbBdXF1aZeti+OjHEnz40= Received: by 10.90.4.21 with SMTP id 21mr51131agd.33.1292594558982; Fri, 17 Dec 2010 06:02:38 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.231.76.165 with SMTP id c37ls3550362ibk.3.p; Fri, 17 Dec 2010 06:02:37 -0800 (PST) Received: by 10.231.206.17 with SMTP id fs17mr340465ibb.8.1292594556977; Fri, 17 Dec 2010 06:02:36 -0800 (PST) Received: by 10.231.206.17 with SMTP id fs17mr340464ibb.8.1292594556937; Fri, 17 Dec 2010 06:02:36 -0800 (PST) Received: from mail-iy0-f178.google.com (mail-iy0-f178.google.com [209.85.210.178]) by gmr-mx.google.com with ESMTP id d9si55593ibq.7.2010.12.17.06.02.35; Fri, 17 Dec 2010 06:02:35 -0800 (PST) Received-SPF: pass (google.com: domain of lukeabergen@gmail.com designates 209.85.210.178 as permitted sender) client-ip=209.85.210.178; Received: by iyi42 with SMTP id 42so480027iyi.23 for ; Fri, 17 Dec 2010 06:02:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.35.131 with SMTP id p3mr785607ibd.87.1292594555732; Fri, 17 Dec 2010 06:02:35 -0800 (PST) Received: by 10.231.19.199 with HTTP; Fri, 17 Dec 2010 06:02:35 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Dec 2010 09:02:35 -0500 Message-ID: Subject: Re: [lojban] go'i as "yes" 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.210.178 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=00032557a2ba554c6f04979b9f31 --00032557a2ba554c6f04979b9f31 Content-Type: text/plain; charset=ISO-8859-1 > > > > If I were writing a program to parse lojban, how should my parser deal > with > > a piece of discourse that contained {go'i} if it wanted to expand > > everything? > > i.e. given the following bridi > > .i ti'e .u'i la .bob. noi lazni cu zvati to pe'i cinri toi ma > > How does {go'i} differ syntactically and semantically from {zo'e zvati > zo'e} > > Neither seems like a very helpful answer to a "ma" question. > > mu'o mi'e xorxes I know, I was just throwing as much interesting stuff into a predicate as I could think of at the time and then saying "go'i" as a way of asking "do {ma} get repeated in a go'i?" Based on the rest of your email, it sounds like a good rule of thumb is "read {go'i} like it's repeating only the main selbri of the previous bridi where it's places are filled with {zo'e} which usually means to assume the previous bridi's terbri(s)". -- 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. --00032557a2ba554c6f04979b9f31 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

> If I were writing a program to parse lojban, how should my parser deal= with
> a piece of discourse that contained {go'i} if it wanted to expand<= br> > everything?
> i.e. given the following bridi
> .i ti'e .u'i la .bob. noi lazni cu zvati to pe'i cinri toi= ma
> How does {go'i} differ syntactically and semantically from {zo'= ;e zvati zo'e}

Neither seems like a very helpful answer to a "ma" question= .

mu'o mi'e xorxes

I know, I was just= throwing as much interesting stuff into a predicate as I could think of at= the time and then saying "go'i" as a way of asking "do = {ma} get repeated in a go'i?"

Based on the rest of your email, it sounds like a good = rule of thumb is "read {go'i} like it's repeating only the mai= n selbri of the previous bridi where it's places are filled with {zo= 9;e} which usually means to assume the previous bridi's terbri(s)"= .

--
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.
--00032557a2ba554c6f04979b9f31--