Received: from mail-gx0-f189.google.com ([209.85.161.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P4kGs-0004tZ-AF; Sat, 09 Oct 2010 18:00:17 -0700 Received: by gxk9 with SMTP id 9sf2436906gxk.16 for ; Sat, 09 Oct 2010 18:00:08 -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=/mQrLSmyDeeK6/UgcvYbF2Z8rZOOl2ttBi+jW6WKzTc=; b=yxVyQYO4MMIelIpPmq8LeMDpf9JS3j0ZKB4XCjZ+evjca9/YGrhvLELIzq6XfBOj1c JrrxJbycbzoioaiq4/XeaECJJS9dFMPKSOX5DuGS7hR7W4MBdmOqlCgt1HXWVWPbWdjl K0RCit3RCBix5PiB1rhdvmTDoped4JNddGwak= 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=GI2MJ14PLhwJpMNHZZZbuisBAdR35jE9iDu14LSWUnNHe2Zqlne98Ogx7sDoSRG2jo TPCked2fR0x+sXfnyejbf+/0Zws4epaNd5eDHRXYiP1H8YHIGKEVFyfJy05Ue21l6c73 VXgfwPUWRYUyeGP9k/4pA33rApS+w/y+cszp0= Received: by 10.91.9.1 with SMTP id m1mr335368agi.48.1286672401874; Sat, 09 Oct 2010 18:00:01 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.231.180.73 with SMTP id bt9ls1024456ibb.0.p; Sat, 09 Oct 2010 18:00:01 -0700 (PDT) Received: by 10.231.58.206 with SMTP id i14mr1218361ibh.0.1286672401563; Sat, 09 Oct 2010 18:00:01 -0700 (PDT) Received: by 10.231.58.206 with SMTP id i14mr1218359ibh.0.1286672401502; Sat, 09 Oct 2010 18:00:01 -0700 (PDT) Received: from mail-iw0-f170.google.com (mail-iw0-f170.google.com [209.85.214.170]) by gmr-mx.google.com with ESMTP id e4si3285911ibc.4.2010.10.09.18.00.00; Sat, 09 Oct 2010 18:00:00 -0700 (PDT) Received-SPF: pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.170 as permitted sender) client-ip=209.85.214.170; Received: by iwn37 with SMTP id 37so563270iwn.15 for ; Sat, 09 Oct 2010 18:00:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.216.131 with SMTP id hi3mr939468icb.322.1286672399820; Sat, 09 Oct 2010 17:59:59 -0700 (PDT) Received: by 10.231.206.68 with HTTP; Sat, 9 Oct 2010 17:59:59 -0700 (PDT) In-Reply-To: References: <20100903032539.GY5990@digitalkingdom.org> <8136604407292225759@unknownmsgid> <6632159152572093565@unknownmsgid> Date: Sat, 9 Oct 2010 18:59:59 -0600 Message-ID: Subject: Re: [bpfk] BPFK work From: Jonathan Jones To: bpfk-list@googlegroups.com X-Original-Sender: eyeonus@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.170 as permitted sender) smtp.mail=eyeonus@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: multipart/alternative; boundary=20cf301cbd345566fa049238c346 Content-Length: 3744 --20cf301cbd345566fa049238c346 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2010/10/9 Jorge Llamb=EDas > On Sat, Oct 9, 2010 at 9:48 PM, Jonathan Jones wrote: > > On Sat, Oct 9, 2010 at 6:44 PM, Jonathan Jones > wrote: > >> > >> Okay, that idea doesn't really work. The only other idea I can think o= f > is > >> "li'o .ie" - "di'ai si .ienai li'o" > > > > That does mean that di'ai has to remain invisible to si, of course. > > Either way it will be unintuitive sometimes. That's the problem of > using words for metalinguistic purposes. > > mu'o mi'e xorxes > I'd say that's a good enough solution for the problem of explicitly stating whether one is continuing another's jufra or not. Considering how often a person would want to be explicit - which I would guess is mutce rirci - the few cases in which it would be unintuitive are, to misuse a phrase, statistically irrelevant. --=20 mu'o mi'e .aionys. .i.a'o.e'e ko cmima le bende pe lo pilno be denpa bu .i doi luk. mi patfu d= o zo'o (Come to the Dot Side! Luke, I am your father. :D ) --=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. --20cf301cbd345566fa049238c346 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
2010/10/9 Jorge Llamb=EDas <= ;jjllambias@gmail.com>
On Sat, Oct 9, 2010 at 9:48 PM, Jonathan Jones <eyeonus@gmail.com> wrote:
> On Sat, Oct 9, 2010 at 6:44 PM, Jonathan Jones <eyeonus@gmail.com> wrote:
>>
>> Okay, that idea doesn't really work. T= he only other idea I can think of is
>> "li'o .ie" - "di'ai si .ienai li'o"= ;
>
> That does mean that di'ai has to remain invisible to si, of course= .

Either way it will be unintuitive sometimes. That's the problem o= f
using words for metalinguistic purposes.

mu'o mi'e xorxes

I'd say that's a good enough solution= for the problem of explicitly stating whether one is continuing another= 9;s jufra or not. Considering how often a person would want to be explicit = - which I would guess is mutce rirci - the few cases in which it would be u= nintuitive are, to misuse a phrase, statistically irrelevant.

--
mu'o mi'e .aionys.

.i.a'o.e'e ko cmima le= bende pe lo pilno be denpa bu .i doi luk. mi patfu do zo'o
(Come to= the Dot Side! Luke, I am your father. :D )

--
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.
--20cf301cbd345566fa049238c346--