From bpfk-list+bncCNCCoMTMDhDWt8TlBBoEHBXVIQ@googlegroups.com Sat Oct 09 18:50:30 2010 Received: from mail-ww0-f61.google.com ([74.125.82.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P4l3T-0007pe-KW; Sat, 09 Oct 2010 18:50:30 -0700 Received: by wwe15 with SMTP id 15sf540205wwe.16 for ; Sat, 09 Oct 2010 18:50:21 -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:received:mime-version:received :in-reply-to:references:from:date:message-id:subject: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=0fHbp1/n/ldJl6QOobda/a0XAK3b9DBg55WWW2oH1gs=; b=dMRooV+MqTVYXdiJBSPPDPAel2x8Ehu07P+T5UER+rFdBFRPL9SyOuorRog656l1EY KgtlGnD4rnkYOq+UOcLCwaZ9qNHcREYD1eUyH4IrkagBq1q9WcloGoVRT6x7kKwjBFqD GTBeqiWWPLIHaHTcA1P5FEU76tzwnVC+0wmSc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:from :date:message-id:subject: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=uhwpaFJ9aZ/Rh+xC1OZKRMdVhLje7Wqi24iAAWFDhN4NIPQttaDBLKvMnxfcp/wNmc fMKsrhen/3YPZ8Ha94g464SlyYvMqTT2oN5vsC8bTxhtwQodFCJnpoLLsAc1ChvpHrON QkIa85OplLBM5ETvdb66wuWVrBDSZhfmrnf6c= Received: by 10.216.145.90 with SMTP id o68mr746590wej.23.1286675414597; Sat, 09 Oct 2010 18:50:14 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.216.237.134 with SMTP id y6ls959953weq.2.p; Sat, 09 Oct 2010 18:50:13 -0700 (PDT) Received: by 10.216.181.80 with SMTP id k58mr211439wem.9.1286675413825; Sat, 09 Oct 2010 18:50:13 -0700 (PDT) Received: by 10.216.181.80 with SMTP id k58mr211438wem.9.1286675413795; Sat, 09 Oct 2010 18:50:13 -0700 (PDT) Received: from mail-ww0-f41.google.com (mail-ww0-f41.google.com [74.125.82.41]) by gmr-mx.google.com with ESMTP id v4si1729194weq.1.2010.10.09.18.50.12; Sat, 09 Oct 2010 18:50:12 -0700 (PDT) Received-SPF: pass (google.com: domain of selckiku@gmail.com designates 74.125.82.41 as permitted sender) client-ip=74.125.82.41; Received: by wwd20 with SMTP id 20so1146362wwd.2 for ; Sat, 09 Oct 2010 18:50:12 -0700 (PDT) Received: by 10.227.6.215 with SMTP id a23mr4159166wba.46.1286675412586; Sat, 09 Oct 2010 18:50:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.138.81 with HTTP; Sat, 9 Oct 2010 18:49:42 -0700 (PDT) In-Reply-To: <4CB0B239.50107@lojban.org> References: <4CB0B239.50107@lojban.org> From: Stela Selckiku Date: Sat, 9 Oct 2010 21:49:42 -0400 Message-ID: Subject: Re: [bpfk] BPFK work To: bpfk-list@googlegroups.com X-Original-Sender: selckiku@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of selckiku@gmail.com designates 74.125.82.41 as permitted sender) smtp.mail=selckiku@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 On Sat, Oct 9, 2010 at 2:19 PM, Robert LeChevalier wrot= e: > > But in case it is relevant, I have not seen any mention of fa'o, the > reserved cmavo that explicitly indicates the end of a piece of text (in t= he > sense of the largest parsible unit), but which I believe is found in no > formal grammar and is almost never used. =A0It was specifically conceived= for > situations where one knows that what one is saying cannot parse as a > continuation of what has gone previously, but has been superfluous in Loj= ban > parsers which were designed to inherently assume a single text. Oh right, {fa'o}! I guess we already have that direction, then, and we just need its opposite perhaps. Incidentally, {fa'o} is rather often used these days! Some of us have started using it on Twitter and other microblogging sites, to separate the Lojban text from any mentions or tags that follow it, like: "mi tavla fo lo melbi fa'o #lojban #conlang @lojbab" mi'e .telselkik. mu'o --=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.