From bpfk-list+bncCJ2UzZHuDRCOlvvqBBoEQU7jdA@googlegroups.com Fri Feb 18 11:40:43 2011 Received: from mail-ww0-f61.google.com ([74.125.82.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PqWBW-0003do-Ij; Fri, 18 Feb 2011 11:40:43 -0800 Received: by wwb34 with SMTP id 34sf3404770wwb.16 for ; Fri, 18 Feb 2011 11:40:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature: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; bh=BXTcImv6n+qlwrE+SSqeWmcKXE1LsI6X31Sr1JFRl1c=; b=KPtGRRTRsTK0vaQ/X9ST0g1Ed5gjisEpnHjMN1XulMk91KmCAvtJBYSmB8gLsYEfm6 cPPJDAS8/NaAsUS/SHdW6CUqiPcRU0CFyg5ErCpq5+hstXO2Rktm4aeWKbKIEBRIT1Vu Dlao5dq0AT+kPDycpFTTion2xxKgWh/7boId0= 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=KphzKxW3XR4YnrhtMwEVLnHA4T/PGaVGoDRDZ38VSXalT6Aaa9x1QKCyx1MNEx+hoz Rdx2FHKCa7xuSeVIIhBdmK50uwVC1mLlr4xs+QW1iNjn0lE2/mQXxQ9Pw6OEPAG369WB EHeC53DUkcwD/M58DDZXZsCytiLzoxzLiLunQ= Received: by 10.216.169.140 with SMTP id n12mr710977wel.24.1298057998238; Fri, 18 Feb 2011 11:39:58 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.216.162.73 with SMTP id x51ls1442227wek.3.p; Fri, 18 Feb 2011 11:39:57 -0800 (PST) Received: by 10.216.29.134 with SMTP id i6mr75124wea.9.1298057997331; Fri, 18 Feb 2011 11:39:57 -0800 (PST) Received: by 10.216.29.134 with SMTP id i6mr75123wea.9.1298057997318; Fri, 18 Feb 2011 11:39:57 -0800 (PST) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by gmr-mx.google.com with ESMTPS id q45si309803weh.0.2011.02.18.11.39.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Feb 2011 11:39:57 -0800 (PST) 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 wwi17 with SMTP id 17so978073wwi.3 for ; Fri, 18 Feb 2011 11:39:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.55.15 with SMTP id s15mr1026268wbg.164.1298057997161; Fri, 18 Feb 2011 11:39:57 -0800 (PST) Received: by 10.227.54.10 with HTTP; Fri, 18 Feb 2011 11:39:57 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Feb 2011 16:39:57 -0300 Message-ID: Subject: Re: [bpfk] dag-cll git updates for Fri Feb 18 14:21:07 EST 2011 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 I haven't been paying any attention to all these dag-cll messages we've been getting on the bpfk-list, because I thought they were about fixing formatting and typos, but Lindar's recent message says there is actual content change going on as well? If so, is there some way to detect the content changes lost among all the unreadable stuff? Going through this last one, I find this: > -- =A0 =A0 =A0 =A0la .apasionatas. poi se cusku la .artr. rubnstain.= cu se nelci mi > -+ =A0 =A0 =A0 =A0la .apasionatas. ku poi se cusku la .artr. rubnsta= in. cu se nelci mi which I assume means that a "ku" is being inserted. That makes it ungrammatical with the current grammar. I support making it grammatical, because it goes in the direction of merging CMEVLA with BRIVLA, but I haven't seen any discussion about a change in the grammar to allow "ku" there. 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.