Received: from mail-ww0-f61.google.com ([74.125.82.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P4YlS-0006Yy-0w; Sat, 09 Oct 2010 05:43:05 -0700 Received: by wwe15 with SMTP id 15sf452992wwe.16 for ; Sat, 09 Oct 2010 05:42:55 -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=ecAAYN4ZMWaSkvGV1gZ9Qdj+aAqIEgG/C3OliUxao4M=; b=3SidueRIe2gbkLUnL2zuvyZwWI1vhK1perNL4bYAohUs1o3CPndLmPoz8ySTbMVw/K EKVbxaZo/d5T8g6A9Tod6aB+PBn41LT8syBD1sjz0GGoNGPeV6jsnvDO8eG2SLsolqpQ gF5tYy82oLJnXhCOXSTETAlo6zI9BFRdUbhGE= 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=FR2HqafRRNMeBRAzWfPEyDn7mJkB7LmzMupGWmzOQ5JDADkAmCLch8EqcxCC9Y4agC OCU+XlBjfi8eeiE1lHOCWKnq7+lS272k7wDyQGlZ1yH26d+tc+7fyDqOukS0QcMXhPe+ gD1qs5jfoHS1n8XjAe1zahPV0bbUjupIgVUE4= Received: by 10.216.237.206 with SMTP id y56mr206456weq.12.1286628168978; Sat, 09 Oct 2010 05:42:48 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.216.237.134 with SMTP id y6ls805462weq.2.p; Sat, 09 Oct 2010 05:42:48 -0700 (PDT) Received: by 10.216.177.205 with SMTP id d55mr88013wem.9.1286628168043; Sat, 09 Oct 2010 05:42:48 -0700 (PDT) Received: by 10.216.177.205 with SMTP id d55mr88012wem.9.1286628168024; Sat, 09 Oct 2010 05:42:48 -0700 (PDT) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by gmr-mx.google.com with ESMTP id o41si1501833weq.4.2010.10.09.05.42.46; Sat, 09 Oct 2010 05:42:47 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 74.125.82.42 as permitted sender) client-ip=74.125.82.42; Received: by mail-ww0-f42.google.com with SMTP id 31so946829wwb.3 for ; Sat, 09 Oct 2010 05:42:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.43.11 with SMTP id u11mr3424654wbe.200.1286628166839; Sat, 09 Oct 2010 05:42:46 -0700 (PDT) Received: by 10.227.145.130 with HTTP; Sat, 9 Oct 2010 05:42:46 -0700 (PDT) In-Reply-To: References: <20100903032539.GY5990@digitalkingdom.org> Date: Sat, 9 Oct 2010 09:42:46 -0300 Message-ID: Subject: Re: [bpfk] BPFK work 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 74.125.82.42 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: 4800 On Sat, Oct 9, 2010 at 5:50 AM, Stela Selckiku wrote: > 2010/10/8 Jorge Llamb=EDas : >> >> Starting an utterance with ".i" is no guarantee that your utterance >> won't be garbled if it's taken as continuation of what someone else is >> saying. As a trivial example, if the other speaker ended with "zo", it >> would just quote your ".i". But there are plenty of other cases that >> could absorb your ".i" too. > > That's how I think of it as working. =A0I don't see how that's a > problem. =A0That could even make sense: > > A: .i .u'u mi djisku zo > (confused pause) > B: .i > > A wasn't sure what word they meant to say that they meant to say, so B > helpfully inserted that it was ".i". Of course that's one possible reading. It is you, the listener, who decides which chunk of sound input you are going to treat as the text to be parsed. You obviously can't take the whole history of sound produced in the universe and treat that as a single piece of Lojban text. And even if you restrict yourself to one room where you can hear two simultaneous conversations, are you going to treat them both as a single text mixing words from each conversation as they come to you? No, you treat one chunk as one text and the other chunk as another text. It's the same with two speakers participating in one conversation. Sometimes they may complete each other's sentences, but for the most part each produces their own text (which of course has the other person's text as part of its context). The problem is not that sometimes someone can complete someone else's sentence. That's perfectly fine. The problem is if you take the absolutist position that everything you say is necessarily a continuation of what someone else has said before as part of the same text. That just won't work. > It's my opinion and preference that a switch to a new speaker should > never automatically imply the beginning of a new text. I agree. There's nothing automatic about it. It is often the case, but you can't count on it being always the case. >=A0I would like > to think of all of the speakers in a conversation as collaborating on > a single text, with only rare exceptions (such as perhaps "ta'a"). "ta'a" is a free modifier, so it can be inserted pretty much anywhere without breaking anything. > I'm not even exactly sure what this idea of switching to a "new > speaker" means, in a Lojbanic context. =A0Two different people don't > have to be two separate speakers in Lojban, do they? =A0They can be > speaking jointly, as one referent of "mi". =A0Surely we must allow two > people to collaboratively speak a single text. =A0We shouldn't attempt > to grammatically enforce concepts of personal identity. And I don't think anyone is suggesting that we do. What we shouldn't do either is pretend that most conversations are not between two (or more) different people. "mi" and "do" in most common cases have well defined and distinct referents. A: .i mi gleki B: .i go'i ra'o Obviously that's two texts, not one text ".i mi gleki .i go'i ra'o" with the second part being a redundant repetition of the first. Anyway, as usual we've been completely derailed from the original issue, which was to find a suitable example for NAI. To sum up: (1) I think using "ienai broda" as an example of NAI is not such a good idea, because there are likely to be two different opinions on how "ienai" affects that bridi. In fact the example I have for "ienai" is pretty much inconsistent with the example given here for "nai". It's controversial because of "ie", not because of "nai", so let's just not use it as an example of "nai". (2) I suggested to replace it with what I thought would be an uncontroversial case: "ienai .i broda" (3) It turns out I was wrong, people now want to make even that second case controversial too. I really cannot believe that people would interpret "ienai .i broda" as anything other than the speaker disagreeing with what was said before and offering some contrary opinion on whatever that was. (4) Since what we want is an example of "nai", not an example of "ie" here, I now suggest we simply drop "ie" as the example and choose something else: "fi'i nai", ".oi nai", ".o'a nai", "uu nai", "la'a nai" there are lots of hopefully non controversial options, but I'm going to let the shepherd pick the actual example so they don't feel the need to find it objectionable in some way. 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.