Re: [bpfk] Improvements to fragments in ilmentufa parser

[Jorge Llambías <jjllambias@gmail.com>]

On Wed, Apr 1, 2015 at 7:02 AM, Gleki Arxokuna <gleki.is.my.name@gmail.com> wrote:

It appears that those two strings:

bridi-tail-3 <- selbri? tail-terms / gek-sentence
tail-terms <- terms? VAU-clause? free* !ZOhU-clause

make isolate {pa} not parseable. Probably because if selbri = "" and tail-terms = "" then it goes wild.

Can you check if this is true?

Right, the rule fragment will never be reached, because the empty string will always satisfy statement:

  paragraph <- (statement / fragment) (I-clause !jek !joik !joik-jek free* (statement / fragment)?)*

"poi broda" and "be ko'a" should suffer the same fate as "pa".

You should reverse the order of fragment and statement to (fragment / statement), so that fragment is tested first, but also remove from fragment all the fragments that are now proper statements. So I think you'd only be left with:

  fragment <- ek free* / quantifier / relative-clauses / links / linkargs
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.