Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c00::234 as permitted sender) client-ip=2a00:1450:400c:c00::234;
MIME-Version: 1.0
From: Gleki Arxokuna <gleki.is.my.name@gmail.com>
Date: Wed, 25 Mar 2015 12:35:53 +0300
Message-ID: <CAO7bV+je-d2vPHm-7AzaQgmgb2K91_Ye2V4ODPEv4oMGmUZAXQ@mail.gmail.com>
Subject: [bpfk] Improvements to fragments in ilmentufa parser
To: bpfk-list@googlegroups.com
Content-Type: multipart/alternative; boundary=047d7b5d561059ed84051219a10d
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: -
Content-Length: 5926

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

The following problems were addressed while analyzing ilmentufa parser
based on camxes.js by Masato Hagiwara based on the original camxes:

1. {ca ma} parses as "fragment"
2. {mi zo'u ca ma} doesn't parse.
3. {mi djica lo nu lo plise} doesn't parse.
4. {mi ije ma} doesn't parse
5. {mi poi ca ma vau mo} doesn't parse.

So I made 2. parse as a "fragment" and made {lo plise} in 3. parse as a
"fragment".
Besides I added in fragment elidible GOhA_elidible which returns a node
labelled "COhE":
4. and 5. are now sentences falling back to fragments with COhE
autorestored.

([mi zo'u] [ca ma] COhE VAU)

(mi [CU {djica <lo (=C2=B9nu [{lo plise KU} COhE VAU] KEI=C2=B9) KU> VAU}])

([CU {mo VAU}] [i je {ma COhE VAU}]

([mi COhE VAU] [i je {ma COhE VAU}])

Notice that this grammar is somewhat experimental, e.g. it treats {cu} as
bridi tail starter.

Justification:
2. why not being able to parse it? Why force people to use {co'e} as the
selbri while we are allowed to omit {zo'e}?
3. {tu'a} in most cases can be replaced with {lonu} now without adding more
syllables but without learning tricky additional words like {tu'a}.

You can test raw output here:
http://vrici.lojban.org/~gleki/mediawiki-1.19.2/extensions/ilmentufa/camxes=
-exp.html

The exact changes implementing this are here:
https://github.com/Ilmen-vodhr/ilmentufa/compare/05a7193368eaeb9198f77533ae=
6f4ab3391fa4ad...8d5d4c3fea2201eba868eb9aa678b46a3dbfaae5

(ignore javascript litter in strings, it's unavoidable)

As you can see "fragment" now restores COhE in certain cases, "sentence"
falls back to this renewed "fragment".

Objections?

E.g. I suppose COhE_elidible should be inserted to more constructs. but I
haven't looked at where it can be done. What else apart from what has been
done can be autocorrected to bridi status?

--=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.

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

<div dir=3D"ltr"><div><div>The following problems were addressed while anal=
yzing ilmentufa parser based on camxes.js by Masato Hagiwara based on the o=
riginal camxes:</div><div><br></div><div>1. {ca ma} parses as &quot;fragmen=
t&quot;</div><div>2. {mi zo&#39;u ca ma} doesn&#39;t parse.</div><div>3. {m=
i djica lo nu lo plise} doesn&#39;t parse.</div><div>4. {mi ije ma} doesn&#=
39;t parse</div><div>5. {mi poi ca ma vau mo} doesn&#39;t parse.</div><div>=
<br></div><div>So I made 2. parse as a &quot;fragment&quot; and made {lo pl=
ise} in 3. parse as a &quot;fragment&quot;.</div><div>Besides I added in fr=
agment elidible GOhA_elidible which returns a node labelled &quot;COhE&quot=
;:<br></div><div><div>4. and 5. are now sentences falling back to fragments=
 with COhE autorestored.</div></div><div><br></div><div>([mi zo&#39;u] [ca =
ma] COhE VAU)=C2=A0<br></div><div><br></div><div>(mi [CU {djica &lt;lo (=C2=
=B9nu [{lo plise KU} COhE VAU] KEI=C2=B9) KU&gt; VAU}])=C2=A0</div><div><br=
></div><div>([CU {mo VAU}] [i je {ma COhE VAU}]<br><br>([mi COhE VAU] [i je=
 {ma COhE VAU}])=C2=A0<br><br>Notice that this grammar is somewhat experime=
ntal, e.g. it treats {cu} as bridi tail starter.</div><div><br></div><div>J=
ustification:=C2=A0<br></div><div>2. why not being able to parse it? Why fo=
rce people to use {co&#39;e} as the selbri while we are allowed to omit {zo=
&#39;e}?</div><div>3. {tu&#39;a} in most cases can be replaced with {lonu} =
now without adding more syllables but without learning tricky additional wo=
rds like {tu&#39;a}.</div><div><br></div><div>You can test raw output here:=
=C2=A0<a href=3D"http://vrici.lojban.org/~gleki/mediawiki-1.19.2/extensions=
/ilmentufa/camxes-exp.html" target=3D"_blank">http://vrici.lojban.org/~glek=
i/mediawiki-1.19.2/extensions/ilmentufa/camxes-exp.html</a></div><div><br><=
/div><div>The exact changes implementing this are here:</div><div><a href=
=3D"https://github.com/Ilmen-vodhr/ilmentufa/compare/05a7193368eaeb9198f775=
33ae6f4ab3391fa4ad...8d5d4c3fea2201eba868eb9aa678b46a3dbfaae5">https://gith=
ub.com/Ilmen-vodhr/ilmentufa/compare/05a7193368eaeb9198f77533ae6f4ab3391fa4=
ad...8d5d4c3fea2201eba868eb9aa678b46a3dbfaae5</a><br></div></div><div><br><=
/div><div>(ignore javascript litter in strings, it&#39;s unavoidable)</div>=
<div><br></div><div>As you can see &quot;fragment&quot; now restores COhE i=
n certain cases, &quot;sentence&quot; falls back to this renewed &quot;frag=
ment&quot;.</div><div><br></div><div>Objections?<br></div><div><br></div><d=
iv>E.g.=C2=A0I suppose COhE_elidible should be inserted to more constructs.=
 but I haven&#39;t looked at where it can be done. What else apart from wha=
t has been done can be autocorrected to bridi status?</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 />

--047d7b5d561059ed84051219a10d--