Received: from mail-lb0-f184.google.com ([209.85.217.184]:48872) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Y26Ri-0002qI-97; Fri, 19 Dec 2014 14:54:56 -0800 Received: by mail-lb0-f184.google.com with SMTP id u14sf130095lbd.11; Fri, 19 Dec 2014 14:54:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type: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; bh=uGBiWb3smu2xjxIP+P0O5MvfbE1CbJU9FBQUmNpFB8U=; b=lipu1QP0oU5xJNGaXsPl6xqD+v1vpmyU3kZ6xHFHlUNM563FJGyd1wHlXTNWrsk08+ CslyVjqI8AB12sFZrlGAbjkSIUJgaYtmoVjF/xdJcea6acjOkZFTEQ+V4gc1GQtPYyza f2mag5J2tutZ3nUQ50JJiY7KSYGv55vOsckFDtWNtl9KpsgjwaJaIZcuHNoB/AY9p5Xf tNPGPTOHWIr4dup9e7dz7wiEwFA8wT/XtsaYKQe34wcKQXLcP3/9gJTHZbdTdcsHxw04 XnWCHPyaoATTZFLtHkt5GlpNqyQzXhXQIHxjwWSpj9BArkhFoS2zLj/MFPQgqpqrziZl t6rQ== X-Received: by 10.180.75.42 with SMTP id z10mr35957wiv.18.1419029687008; Fri, 19 Dec 2014 14:54:47 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.103.167 with SMTP id fx7ls236449wib.25.gmail; Fri, 19 Dec 2014 14:54:46 -0800 (PST) X-Received: by 10.194.133.39 with SMTP id oz7mr12547wjb.3.1419029686881; Fri, 19 Dec 2014 14:54:46 -0800 (PST) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com. [2a00:1450:4010:c03::235]) by gmr-mx.google.com with ESMTPS id mu9si412178lbc.0.2014.12.19.14.54.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Dec 2014 14:54:46 -0800 (PST) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c03::235 as permitted sender) client-ip=2a00:1450:4010:c03::235; Received: by mail-la0-f53.google.com with SMTP id gm9so1662565lab.12 for ; Fri, 19 Dec 2014 14:54:46 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.73.97 with SMTP id k1mr10298344lbv.78.1419029686752; Fri, 19 Dec 2014 14:54:46 -0800 (PST) Received: by 10.114.78.9 with HTTP; Fri, 19 Dec 2014 14:54:46 -0800 (PST) In-Reply-To: <453B2682CF664DECBA7B599F97BB9AF6@gmail.com> References: <548AC3CB.7090403@gmx.de> <580B9AB84B34485AB4139B921C46CF42@gmail.com> <3ED463A548E74A53BD8F2ECEF0C620F8@gmail.com> <14FDADF47D7841A39D612894E81CC89B@gmail.com> <20141214025736.GB19927@mercury.ccil.org> <20141214190350.GD29313@mercury.ccil.org> <5660b66f-68e1-4e9c-b4ce-1713a7bf1491@googlegroups.com> <86CF3AC1702C439EAC77F8EDC0AA0B9D@gmail.com> <453B2682CF664DECBA7B599F97BB9AF6@gmail.com> Date: Fri, 19 Dec 2014 19:54:46 -0300 Message-ID: Subject: Re: [bpfk] official cmavo form From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=001a11c3274c679a62050a9998d9 X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c03::235 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 2866 --001a11c3274c679a62050a9998d9 Content-Type: text/plain; charset=UTF-8 On Fri, Dec 19, 2014 at 7:48 PM, Alex Burka wrote: > > I'm not maikxlx, but I was asking whether you were making a distinction > between {ia} and {i,a} (because I thought that under camxes there was no > such distinction). > Oops, sorry about that; Indeed camxes completely ignores commas. I was addressing maikxlx's ideas. I don't understand what the rationale would be for allowing "ia" word-initially but not word-medially. Why is it more distinct word-initially than word-medially? mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an email to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --001a11c3274c679a62050a9998d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Dec 19, 2014 at 7:48 PM, Alex Burka <aburka@seas.upenn.edu= > wrote:
I'm not maikxlx, but I was asking whether you were = making a distinction between {ia} and {i,a} (because I thought that under c= amxes there was no such distinction).

Oops, sorry about that;

Indeed camxes completely = ignores commas. I was addressing maikxlx's ideas. I don't understan= d what the rationale would be for allowing "ia" word-initially bu= t not word-medially. Why is it more distinct word-initially than word-media= lly?

mu'o mi'e xorxes

=

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
--001a11c3274c679a62050a9998d9--