Received: from mail-ww0-f61.google.com ([74.125.82.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P53H5-0006Iw-HH; Sun, 10 Oct 2010 14:17:46 -0700 Received: by wwe15 with SMTP id 15sf663394wwe.16 for ; Sun, 10 Oct 2010 14:17:37 -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; bh=rde0oz/sVpDpitsvKBxocNHy8MnhXua46JelkJUYntw=; b=CVC6MNlz4fLCDfF5J8vQQClCskQc1TOJ2TU9wa4mP02sLi0nrxEQRoCR2kdHWfy5V7 CDLNl6oFU/9nSwLeuDymss/PtMcnbvAIHdPBEdJ1MmHyjZWJ/mOvotsu7W+Yb3sffvji X7sm8+V1bvaOnvQRzr+PZ4PRLwl8uKnL9BTgc= 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=l1+FZDCaU94vG+HbrsS2rwqgHFMD0gvfExxZdc2bNI81GUfkuR3aE+d8jQ/UAskK8W IEJ2dBczJm+XREpcoFSXTDK2Dc1R1efbbk6kA/JWto/yg+QoPohBQqHgkpIohNiie7jt +o2ilPfN62/B9vs3RlItMa1096x/snuo22nHM= Received: by 10.216.237.206 with SMTP id y56mr348226weq.12.1286745451338; Sun, 10 Oct 2010 14:17:31 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.216.238.19 with SMTP id z19ls83000weq.2.p; Sun, 10 Oct 2010 14:17:30 -0700 (PDT) Received: by 10.216.165.85 with SMTP id d63mr12531wel.10.1286745450645; Sun, 10 Oct 2010 14:17:30 -0700 (PDT) Received: by 10.216.165.85 with SMTP id d63mr12530wel.10.1286745450612; Sun, 10 Oct 2010 14:17:30 -0700 (PDT) Received: from mail-ww0-f48.google.com (mail-ww0-f48.google.com [74.125.82.48]) by gmr-mx.google.com with ESMTP id w33si786984wbd.6.2010.10.10.14.17.29; Sun, 10 Oct 2010 14:17:29 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 74.125.82.48 as permitted sender) client-ip=74.125.82.48; Received: by wwi14 with SMTP id 14so80647wwi.17 for ; Sun, 10 Oct 2010 14:17:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.135.75 with SMTP id m11mr4945360wbt.96.1286745449363; Sun, 10 Oct 2010 14:17:29 -0700 (PDT) Received: by 10.227.145.130 with HTTP; Sun, 10 Oct 2010 14:17:29 -0700 (PDT) In-Reply-To: References: <4CB0B239.50107@lojban.org> <4CB1F3EA.5000608@lojban.org> <4CB20ADF.6050500@lojban.org> Date: Sun, 10 Oct 2010 18:17:29 -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.48 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-Length: 2270 On Sun, Oct 10, 2010 at 5:44 PM, Jonathan Jones wrote: > > The disadvantage is that my human brain has to mentally insert the elided > {.i}. There's no such thing as an elided ".i"! ".i" is not an elidable word. > Not being a stupid machine, I am able to intuitively determine whether > a person is continuing another persons text or merely not bothering to start > with {.i} based on context and the content of the two or more persons' > speeches. Because the practice of eliding the intial {.i} is /ambiguous/, I > don't do it myself. There is no practice of eliding ".i". There is no required initial ".i". The separator ".i" is required between two sentences, it is not required at the beginning of a text. If you are proposing a change to the language, please make it clear that that is what you are doing. I make change proposals all the time, but I try to keep distinct what my proposal is from what the official rule is. Otherwise it gets confusing. Are you arguing for a change, or are you explaining how you understand the language is currently defined? There is no such thing as an elided ".i" in the current language, and there is no rule that every new speaker just keeps adding stuff to one single text in a conversation. > The advantage is, it is both easy and possible to continue another person's > jufra by the simple method of /not/ beginning your speech with {.i}. Except when you want to continue it with ".i", which may be rare but possible. But then speakers completing other speaker's sentences is also rare. And there are ways of doing it from your own text in any case, for example with "go'i" which can bring a sentence from someone else's text into your own and you can complete it there. So you are willing to give up the useful property of texts of having a speaker and an audience, for the rare occasions when someone wants to complete someone else's sentences? mu'o mi'e xorxes -- 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@googlegroups.com. For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.