Received: from mail-fx0-f61.google.com ([209.85.161.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P657A-0006ie-Ez; Wed, 13 Oct 2010 10:27:48 -0700 Received: by fxm16 with SMTP id 16sf645276fxm.16 for ; Wed, 13 Oct 2010 10:27:36 -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-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 :content-transfer-encoding; bh=C0jae/k7gWhzKKq54nXct3GoiaL8ZGecYzCJhNSFt+g=; b=6qXz9FNPw64ABy+luBHjVQz/2+b9bU5fr7TG8FziwebnI3TtwVmtwz3JHE9kTJBMcP xV1xstbgA9bC9/Z3J7MVpEckljRv+KMO7tYV9unQSxBBAykj4xfLD8OlJ84xDE8mizui ET423Y+YXnUUWbIewnLez3gr0TVOXteNL6opg= 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:content-transfer-encoding; b=b/v4EzHhTRZTai0YMW5M2H6f0ABaBi+qyx20WzsV8B2VEriF2Op8YmeUHJ85/xxHLn 3pWORgl8Y1NuzibzEC6553wKwE3X5LvCRKVjU0cqIBnuXh4xMHNDOReqDHSfBBTKayd7 Rp0wJdD4xjz1YRHMWV9JnZVr9EmdoIfa56MvQ= Received: by 10.223.54.70 with SMTP id p6mr222158fag.6.1286990850950; Wed, 13 Oct 2010 10:27:30 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.204.137.193 with SMTP id x1ls609126bkt.0.p; Wed, 13 Oct 2010 10:27:30 -0700 (PDT) Received: by 10.204.22.204 with SMTP id o12mr477308bkb.2.1286990850205; Wed, 13 Oct 2010 10:27:30 -0700 (PDT) Received: by 10.204.22.204 with SMTP id o12mr477307bkb.2.1286990850103; Wed, 13 Oct 2010 10:27:30 -0700 (PDT) Received: from mail-fx0-f45.google.com (mail-fx0-f45.google.com [209.85.161.45]) by gmr-mx.google.com with ESMTP id p18si6202493bkb.0.2010.10.13.10.27.29; Wed, 13 Oct 2010 10:27:29 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.161.45 as permitted sender) client-ip=209.85.161.45; Received: by mail-fx0-f45.google.com with SMTP id 9so1719871fxm.32 for ; Wed, 13 Oct 2010 10:27:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.150.202 with SMTP id o10mr639807hbb.75.1286990848813; Wed, 13 Oct 2010 10:27:28 -0700 (PDT) Received: by 10.239.162.66 with HTTP; Wed, 13 Oct 2010 10:27:28 -0700 (PDT) In-Reply-To: References: <3443a11a-dc47-4efe-8501-4bdd78333ccf@y32g2000prc.googlegroups.com> Date: Wed, 13 Oct 2010 14:27:28 -0300 Message-ID: Subject: Re: [bpfk] Re: {.i} and {ni'o}, continuation or new jufra From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: bpfk-list@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 209.85.161.45 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Length: 1838 On Wed, Oct 13, 2010 at 12:37 PM, Daniel Brockman wrot= e: > > Here's how I see it: > > =A0{fa'ai}: Explicitly opens a new text. > =A0{fa'ei}: Explicitly opens an existing text for appending. > =A0{fa'o}: Explicitly closes the current text. The problem is that the grammar has no access to anything like "existing texts" that can be "opened", unless you are talking of a completely different paradigm than the YACC/BNF/PEG formal grammars. All texts that have been absorbed by the "text" rule are done and dealt with, there is no reopening of them. > The parameter to {fa'ei} should be a sumti whose referent > points the reader (whether human or machine) to the text > being appended to. =A0I expect that the sumti would usually > refer to the previous speaker. =A0The parameter is either > optional or you have to use {zo'e} if you want to be vague. The grammar has no access to the referents of sumti, so you seem to be talking about a human interpreter here. > The word stream following {fa'ei} is not a text in itself and > thus cannot be parsed on its own. =A0You have to find the > existing text first, append to that, and then reparse. Will the "existing text" not allowed to be a "project of a text" then? Is it not possible to append to the non-text "mi klama lo"? > I don't know what happens to pronouns like {mi} and {do} > when one speaker appends to another speaker's text. I would say that's the least of our problems, at this stage. mu'o mi'e xorxes --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To post to this group, send email to bpfk-list@googlegroups.com. To unsubscribe from this group, send email to bpfk-list+unsubscribe@googleg= roups.com. For more options, visit this group at http://groups.google.com/group/bpfk-l= ist?hl=3Den.