Received: from mail-la0-f62.google.com ([209.85.215.62]:33012) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.85) (envelope-from ) id 1ZHoOU-0004pK-Fj; Wed, 22 Jul 2015 00:24:56 -0700 Received: by lagw2 with SMTP id w2sf84516934lag.0; Wed, 22 Jul 2015 00:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-spam-checked-in-group :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=4o6QdukjzU2gDYmseJcs5I4/qIW2055OL3jx12bwrOs=; b=Jh2eQRIMzO5vU6BS0SD90YIWuZqeO4J3YvMvJ9VQV/8GD/zV2dzRHaO8zRfTgNtYzp OnAotuS8dbyTyAsWI28rApdB02lvLFk46Qr/9Jb5VrgRmApiGX8UUr+dk7nrmyRq42NX TqYoScUjarjwQUXh3LjTVrGelphfI63KJuUj36p05lqmid7HgX3FUFccb2raIEt6orwx gdgnj+QtxM6LKhMKJwT2b7AxJMN2d4V0f+H2jVG0NHp05vH7CGOc8oj9BPY8jdmBoYE5 vMfp7NSA5BKTaHxivnA2sGGJkTG2fj3Mnf9pQvtnIw8qe10CtwFtXq7xfSOyf2POxC9R 0P+g== X-Received: by 10.180.208.47 with SMTP id mb15mr128675wic.19.1437549879301; Wed, 22 Jul 2015 00:24:39 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.94.10 with SMTP id cy10ls89031wib.25.gmail; Wed, 22 Jul 2015 00:24:39 -0700 (PDT) X-Received: by 10.180.90.106 with SMTP id bv10mr1011583wib.6.1437549879031; Wed, 22 Jul 2015 00:24:39 -0700 (PDT) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com. [2a00:1450:400c:c05::235]) by gmr-mx.google.com with ESMTPS id c3si654681wiz.2.2015.07.22.00.24.39 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jul 2015 00:24:39 -0700 (PDT) Received-SPF: pass (google.com: domain of durka42@gmail.com designates 2a00:1450:400c:c05::235 as permitted sender) client-ip=2a00:1450:400c:c05::235; Received: by mail-wi0-x235.google.com with SMTP id xm9so87676322wib.1 for ; Wed, 22 Jul 2015 00:24:39 -0700 (PDT) X-Received: by 10.194.52.105 with SMTP id s9mr2155358wjo.53.1437549878916; Wed, 22 Jul 2015 00:24:38 -0700 (PDT) Received: from Alexs-MacBook-Air-2.local ([192.124.26.172]) by smtp.gmail.com with ESMTPSA id eu2sm1901356wic.8.2015.07.22.00.24.37 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jul 2015 00:24:38 -0700 (PDT) Date: Wed, 22 Jul 2015 09:24:41 +0200 From: Alex Burka To: bpfk-list@googlegroups.com Message-ID: In-Reply-To: References: Subject: Re: [bpfk] Re: Internal grammar of UI, NAI and CAI X-Mailer: Airmail Beta (309) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="55af4539_4da3510e_64d6" X-Original-Sender: durka42@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of durka42@gmail.com designates 2a00:1450:400c:c05::235 as permitted sender) smtp.mail=durka42@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-Spam-Checked-In-Group: bpfk-list@googlegroups.com X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - --55af4539_4da3510e_64d6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline This is nice. I wonder if we could do a little study of UI-strings in the c= orpus to see if this breaks any widely used patterns. Also, I would be happ= y if we added toi'e/toi'o or a similar mechanism. On July 22, 2015 at 8:10:43 AM, Gleki Arxokuna (gleki.is.my.name@gmail.com)= wrote: 2015-07-20 19:18 GMT+03:00 Gleki Arxokuna : It means that {ro'a} series modify UI1 particles but not modify each other = (like if they were connected using {je}). After that {dai} follow (again as= if connected using {je} between themselves). Clarification. Obviously, {dai} do modify each other but as mentioned in th= e next sentence they must do that from right to the left which is currently= unavailable hence this ugly representation. =C2=A0 The problem is that a string of DAI should be parsed from right to left: -- 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 e= mail 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. --=20 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 e= mail 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. --55af4539_4da3510e_64d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =
This is nice. I wonder if we could do a little stu= dy of UI-strings in the corpus to see if this breaks any widely used patter= ns. Also, I would be happy if we added toi'e/toi'o or a similar mechanism.<= /div>
=

On July 22, 2015 a= t 8:10:43 AM, Gleki Arxokuna (gleki.is.my.name@gmail.com) wrote:


2015-07-20 19:18 GMT+03:00 Gleki Arxokuna <gleki.is.my.name@gmail.com>:
It means that {ro'a} series modify UI1 particles but not modify each other (like if they were connected using {je}). After that {dai} follow (again as if connected using {je} between themselves).

Clarification. Obviously, {dai} do modify each other but as mentioned in the next sentence they must do that from right to the left which is currently unavailable hence this ugly representation.

 
The problem is that a string of DAI should be parsed from right to left:


--
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 ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.

--
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.
--55af4539_4da3510e_64d6--