Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c00::231 as permitted sender) client-ip=2a00:1450:400c:c00::231;
MIME-Version: 1.0
Date: Tue, 31 Mar 2015 20:45:04 -0300
Message-ID: <CAO7tK2dbJKdicdV9qWvn2Wn1gNiSNbQzqg01PBQCdUr0N_D+DQ@mail.gmail.com>
Subject: [bpfk] selma'o ZEhEI and PEG
From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= <jjllambias@gmail.com>
To: bpfk-list@googlegroups.com
Content-Type: multipart/alternative; boundary=047d7b8743f81bce5205129e3014
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
Sender: bpfk-list@googlegroups.com
X-Spam_score: -1.7
X-Spam_score_int: -16
X-Spam_bar: -

--047d7b8743f81bce5205129e3014
Content-Type: text/plain; charset=UTF-8

gleki asked about incorporating selma'o ZEhEI to PEG and I said it would
require modifying lots and lots of rules, basically all the selma'o rules.
But maybe not.

I was thinking of ZEhEI as being similar to ZEI, but that's probably not
the best way to think about it. ZEhEI is actually much more like BU. The
only difference is that instead of creating something like BY, it creates
something like BAhE. So we only need to do for ZEhEI wrt to BAhE what we do
for BU wrt to BY.

This is still not trivial, because BU interacts with ZEI in weird ways, and
now we'd be adding a third ingredient into the mix, which makes it all even
more messy. But the required modifications would probably look something
like this:

zehei-clause <- pre-clause zehei-clause-no-pre
zehei-clause-no-pre <- pre-zei-bu (zehei-tail? zei-tail / zehei-tail?
bu-tail)* zehei-tail post-clause

zei-clause-no-pre <- pre-zei-bu (zei-tail? bu-tail / zei-tail?
zehei-tail)* zei-tail post-clause

bu-clause-no-pre <- pre-zei-bu (bu-tail? zei-tail / bu-tail?
zehei-tail)* bu-tail post-clause

zehei-tail <- ZEhEI-clause+

pre-zei-bu <- (!ZEhEI-clause !BU-clause !ZEI-clause !SI-clause
!SA-clause !SU-clause !FAhO-clause any-word-SA-handling) si-clause?

;         turns any word into a BAhE modifier

ZEhEI-clause <- ZEhEI-pre ZEhEI-post
ZEhEI-pre <- pre-clause ZEhEI spaces?
ZEhEI-post <- spaces?

;         next word intensifier
BAhE-clause <- (BAhE-pre BAhE-post)+ / zehei-clause+
BAhE-pre <- BAhE spaces?
BAhE-post <- si-clause? !ZEI-clause !BU-clause !ZEhEI-clause

I haven't tested any of this, and it may require further tweaking, but
that's the general idea. It may also be necessary to add !ZEhEI-clause
wherever there's a !ZEI-clause !BU-clause, but I suspect many of those
are actually redundant.

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.

--047d7b8743f81bce5205129e3014
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div>gleki asked about incorporating selma&#39;o ZEhEI=
 to PEG and I said it would require modifying lots and lots of rules, basic=
ally all the selma&#39;o rules. But maybe not.</div><div><br></div><div>I w=
as thinking of ZEhEI as being similar to ZEI, but that&#39;s probably not t=
he best way to think about it. ZEhEI is actually much more like BU. The onl=
y difference is that instead of creating something like BY, it creates some=
thing like BAhE. So we only need to do for ZEhEI wrt to BAhE what we do for=
 BU wrt to BY.</div><div><br></div><div>This is still not trivial, because =
BU interacts with ZEI in weird ways, and now we&#39;d be adding a third ing=
redient into the mix, which makes it all even more messy. But the required =
modifications would probably look something like this:</div><div><br></div>=
<div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wr=
ap"><font face=3D"arial, helvetica, sans-serif">zehei-clause &lt;- pre-clau=
se zehei-clause-no-pre
zehei-clause-no-pre &lt;- pre-zei-bu (zehei-tail? zei-tail / zehei-tail? bu=
-tail)* zehei-tail post-clause</font></pre><pre style=3D"color:rgb(0,0,0);w=
ord-wrap:break-word;white-space:pre-wrap"><pre style=3D"word-wrap:break-wor=
d;white-space:pre-wrap"><font face=3D"arial, helvetica, sans-serif">zei-cla=
use-no-pre &lt;- pre-zei-bu (zei-tail? bu-tail / zei-tail? zehei-tail)* zei=
-tail post-clause

bu-clause-no-pre &lt;- pre-zei-bu (bu-tail? zei-tail / bu-tail? zehei-tail)=
* bu-tail post-clause</font></pre></pre></div><div><pre style=3D"color:rgb(=
0,0,0);word-wrap:break-word;white-space:pre-wrap"><span style=3D"font-famil=
y:arial,helvetica,sans-serif">zehei-tail &lt;- ZEhEI-clause+</span><br></pr=
e><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"=
><font face=3D"arial, helvetica, sans-serif">pre-zei-bu &lt;- (!ZEhEI-claus=
e !BU-clause !ZEI-clause !SI-clause !SA-clause !SU-clause !FAhO-clause any-=
word-SA-handling) si-clause?
</font></pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-spac=
e:pre-wrap"><span style=3D"font-family:arial,helvetica,sans-serif">;       =
  turns any word into a BAhE modifier </span><br></pre><pre style=3D"color:=
rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><pre style=3D"word-wr=
ap:break-word;white-space:pre-wrap"><font face=3D"arial, helvetica, sans-se=
rif">ZEhEI-clause &lt;- ZEhEI-pre ZEhEI-post
ZEhEI-pre &lt;- pre-clause ZEhEI spaces?
ZEhEI-post &lt;- spaces?</font></pre><pre style=3D"word-wrap:break-word;whi=
te-space:pre-wrap"><pre style=3D"word-wrap:break-word;white-space:pre-wrap"=
><font face=3D"arial, helvetica, sans-serif">;         next word intensifie=
r=20
BAhE-clause &lt;- (BAhE-pre BAhE-post)+ / zehei-clause+
BAhE-pre &lt;- BAhE spaces?
BAhE-post &lt;- si-clause? !ZEI-clause !BU-clause !ZEhEI-clause</font></pre=
></pre></pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-spac=
e:pre-wrap"><font face=3D"arial, helvetica, sans-serif">I haven&#39;t teste=
d any of this, and it may require further tweaking, but that&#39;s the gene=
ral idea. It may also be necessary to add !ZEhEI-clause wherever there&#39;=
s a !ZEI-clause !BU-clause, but I suspect many of those are actually redund=
ant.</font></pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-=
space:pre-wrap"><font face=3D"arial, helvetica, sans-serif">mu&#39;o mi&#39=
;e xorxes</font></pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;w=
hite-space:pre-wrap"><font face=3D"arial, helvetica, sans-serif"><br></font=
></pre></div></div>

<p></p>

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

--047d7b8743f81bce5205129e3014--