Received: from mail-qw0-f61.google.com ([209.85.216.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P4iyd-0008In-Pw; Sat, 09 Oct 2010 16:37:22 -0700 Received: by qwk4 with SMTP id 4sf369087qwk.16 for ; Sat, 09 Oct 2010 16:37:14 -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:received-spf:received:received:references:from :in-reply-to:mime-version: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=tQoh9NLWKEMeadpkkhlxMF9ekHYnAz+m4cp6qv5MDQI=; b=X4eNIqSDiwXbIaWHLDFjk1mCSHug8aIBr9KhhFlvqAOp3wtM2FZkiaNbHKlqSrc/Br vnWNryPgewjLAPEaTaXdyqu7517cVgei8TRHrBHKULfspW15K8kYbxtX/vQimScVzu4G PREAB+zcVhijrc2IQ8z+3ruNzEG9iMtw4SY5E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:references:from:in-reply-to:mime-version :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=E4pj2Abl1coLOCRBdE0jdr16ViOjSFkz/hyJCitKXCJKvhfaxQ4yMreRQtIQ+ycI4G IOS26et2v6QQifgCFkmCKc6TKg7psupupUkbBjMB1Wt+a8lqkqJn8MSJCF6aNZAFfsaB ISJ1JnMRWhG1J7PyD1jXXuMBPflHmghVU9TcQ= Received: by 10.224.206.137 with SMTP id fu9mr108127qab.51.1286667427700; Sat, 09 Oct 2010 16:37:07 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.224.87.217 with SMTP id x25ls420781qal.0.p; Sat, 09 Oct 2010 16:37:07 -0700 (PDT) Received: by 10.224.206.137 with SMTP id fu9mr678093qab.28.1286667427272; Sat, 09 Oct 2010 16:37:07 -0700 (PDT) Received: by 10.220.175.141 with SMTP id ba13mr863801vcb.13.1286662852182; Sat, 09 Oct 2010 15:20:52 -0700 (PDT) Received: by 10.220.175.141 with SMTP id ba13mr863800vcb.13.1286662852158; Sat, 09 Oct 2010 15:20:52 -0700 (PDT) Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by gmr-mx.google.com with ESMTP id a10si834825vci.13.2010.10.09.15.20.51; Sat, 09 Oct 2010 15:20:51 -0700 (PDT) Received-SPF: pass (google.com: domain of dbrockman@gmail.com designates 209.85.216.179 as permitted sender) client-ip=209.85.216.179; Received: by mail-qy0-f179.google.com with SMTP id 7so2154666qyk.10 for ; Sat, 09 Oct 2010 15:20:51 -0700 (PDT) Received: by 10.229.231.4 with SMTP id jo4mr3564889qcb.22.1286662850738; Sat, 09 Oct 2010 15:20:50 -0700 (PDT) References: <20100903032539.GY5990@digitalkingdom.org> <8136604407292225759@unknownmsgid> From: Daniel Brockman In-Reply-To: Mime-Version: 1.0 (iPhone Mail 8A293) Date: Sun, 10 Oct 2010 00:21:56 +0200 Message-ID: <6632159152572093565@unknownmsgid> Subject: Re: [bpfk] BPFK work To: "bpfk-list@googlegroups.com" X-Original-Sender: dbrockman@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dbrockman@gmail.com designates 209.85.216.179 as permitted sender) smtp.mail=dbrockman@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: 1378 > If it's an existing selma'o, then either UI or BAhE are the best choices,= I think. Even they will fail if the first speaker ends with ZO or ZEI thou= gh, because you wouldn't be able to complete with what you really want to c= omplete. You would need to use some additional trick with SI. I honestly don't understand what you are talking about here. > But we can't really add that to the formal grammar, so I say leave it to = pragmatics what chunk of input should be treated as the full text to parse,= whether it involves a single voice (as usual) or more than one voice (as c= an happen sometimes). Well, having an explicit cmavo means not having to rely on pragmatics (which in Lojbanistan are often low-bandwidth: IRC and e-mail are the lion's share). This can still be useful even if the formal parser will not be helped by the cmavo. But I see what you mean and I agree. Being able to be explicit about this is not an urgent expressive need at this time. Thank you for what has so far been an interesting conversation. --=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.