Received: from mail-ie0-f189.google.com ([209.85.223.189]:34291) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YdQY9-0005W2-LS; Wed, 01 Apr 2015 14:51:57 -0700 Received: by iebtr6 with SMTP id tr6sf23928091ieb.1; Wed, 01 Apr 2015 14:51:43 -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:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=6z/509Fz0XL7QC85z5B/QuRRBc8MQXqix3od1dYViio=; b=b3valC+6cyY2NJ1yuSWEz28AmoR0OE2P3cu0l8r3TLwOS4v/0rCVkQ62ogRX1nDDeP +xEUqwMHj0Dsp0YP72RRHF0VFNvMq8tL556JHRaEr30YkGFLGGic++9pt4KLFvVYakBw RTZuliDPd7O7KEbFhwoOTwFgrfwji06NDGDUQCJMrjhtYCfd5gUGqJKvq8APM8OPV6jZ uZBK6sxRKBx+1W7TScqdqPNpTY2NieoOoIjxdMsoiKVyl4LNM+spwwsP/PT7mMD3R0fj xYg4VSSHf7bfEfLf54BUCBty1iCpNqNWklqDuuCeGTe+rJbMs/qV2h8V3b0sgq8A7JO0 jEMA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=6z/509Fz0XL7QC85z5B/QuRRBc8MQXqix3od1dYViio=; b=VsveUu6ucqJYJRh2LCD+MaFEJd++4RInq9QgG9zX67kh7tt2ozbgW/DHshNm82pd7c NZLwTLeoBQYbtSE7c9jz6PLRVzyVwAyoxjntL4y7AVk0L3n4cNipgDwdwBUNGvxWY+Lz 9Zb9du1GU1DvT6oPjBYNFhxPbCuhjzIR1PXXtbfOuWg+uMiZBVYuCJfRvHr4g0mcLYNC V41i4Tq0vLlmdfCB9qrX036NvW+PddCJ0uNxW3V2obMggMijxDpsYh9YE5yea0pX02fZ AJyh30GhpJZwy+uP7GrCKZFZ1R5Heulcr5j1sh/zksCcCSDZXAZ+QCPhKpk9YB7G5wbi Du2Q== X-Received: by 10.50.148.98 with SMTP id tr2mr274153igb.3.1427925103162; Wed, 01 Apr 2015 14:51:43 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.50.44.4 with SMTP id a4ls1849970igm.36.canary; Wed, 01 Apr 2015 14:51:42 -0700 (PDT) X-Received: by 10.50.164.228 with SMTP id yt4mr271678igb.2.1427925102910; Wed, 01 Apr 2015 14:51:42 -0700 (PDT) Date: Wed, 1 Apr 2015 14:51:41 -0700 (PDT) From: guskant To: bpfk-list@googlegroups.com Message-Id: In-Reply-To: <1542A73D520E49BDB44789AB54497FDC@gmail.com> References: <1542A73D520E49BDB44789AB54497FDC@gmail.com> Subject: Re: [bpfk] selma'o ZEhEI and PEG MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3837_1864760099.1427925101405" X-Original-Sender: gusni.kantu@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.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - ------=_Part_3837_1864760099.1427925101405 Content-Type: multipart/alternative; boundary="----=_Part_3838_646639575.1427925101405" ------=_Part_3838_646639575.1427925101405 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Le jeudi 2 avril 2015 04:27:48 UTC+9, la durka a =C3=A9crit : > > Hmm, I don't know about this. I definitely see the motivation to avoid= =20 > modifying a bunch of parser rules (though what xorxes wrote really isn't= =20 > that many), but I'm not sure that MAI matches. A ((number / lerfu-string)= =20 > MAI-clause) is just an indicator, which binds to the previous word. So if= =20 > you write {zo'e bu ze'ei pa} with ze'ei in MAI, then it parses as {((zo'e= =20 > bu) ze'ei) pa}, with the zo'ebuze'ei attached to whatever precedes, rathe= r=20 > than the {pa}. Then to match the semantics to the grammar you'd want to= =20 > swap the order of {ze'ei} and make it {pa zo'e bu ze'ei}. Thoughts?=20 > > - mu'o mi'e durkavore=20 > =20 You are right, though the span of semantics does not have to be the same as= =20 the span of syntax. If you don't mind changing the order of words around=20 {ze'ei}, we could modify the definition of {ze'ei} of MAI so that the usage= =20 should be "X Y bu ze'ei". So the definition of {xo'e} will be as you said:= =20 pa zo'e bu ze'ei mu'o --=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. ------=_Part_3838_646639575.1427925101405 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Le jeudi 2 avril 2015 04:27:48 UTC+9, la durka a = =C3=A9crit :
Hmm, I don't know about this. I definitely see the moti= vation to avoid modifying a bunch of parser rules (though what xorxes wrote= really isn't that many), but I'm not sure that MAI matches. A ((number / l= erfu-string) MAI-clause) is just an indicator, which binds to the previous = word. So if you write {zo'e bu ze'ei pa} with ze'ei in MAI, then it parses = as {((zo'e bu) ze'ei) pa}, with the zo'ebuze'ei attached to whatever preced= es, rather than the {pa}. Then to match the semantics to the grammar you'd = want to swap the order of {ze'ei} and make it {pa zo'e bu ze'ei}. Thoughts?

- mu'o mi'e durkavore

 
You are right, though the span of semantics does not have to be= the same as the span of syntax. If you don't mind changing the order of wo= rds around {ze'ei}, we could modify the definition of {ze'ei} of MAI so tha= t the usage should be "X Y bu ze'ei". So the definition of {xo'e} will be a= s you said: 

pa zo'e bu ze'ei

<= /div>
mu'o

--
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.
------=_Part_3838_646639575.1427925101405-- ------=_Part_3837_1864760099.1427925101405--