Re: [bpfk] extended rafsi and a tosmabru/slinku'i boondoggle

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

On Sun, Nov 9, 2014 at 6:26 PM, Alex Burka <durka42@gmail.com> wrote:

These didn't quite fix it. I think the problem has to do with stress, because I stumbled onto a change that is a half-fix (but I have no idea what else it breaks).

OK, more changes. The problem is that when checking "sporte'y" for slinku'i, it doesn't recognize "porte'y" as a rafsi-string because "por" gets absorbed as a y-less-rafsi, when it shouldn't, so it never absorbs "porte'y" as it should. Then "porte'y" is not deemed to be a rafsi string, "sporte'y" is not deemed to be a slinku'i and "sporte'yske" goes through.

So I'm adding these two new rules:

hy-rafsi = (long-rafsi vowel / CCV-rafsi / CVV-rafsi) h y h?

stressed-hy-rafsi = (long-rafsi stressed-vowel / stressed-CCV-rafsi / stressed-CVV-rafsi) h y h?

And changing these other two:

y-less-rafsi <- !y-rafsi !stressed-y-rafsi !hy-rafsi !stressed-hy-rafsi (CVC-rafsi / CCV-rafsi / CVV-rafsi) !h !any-extended-rafsi

rafsi-string <- y-less-rafsi* (gismu / CVV-final-rafsi / stressed-y-less-rafsi short-final-rafsi / y-rafsi / stressed-y-rafsi / stressed-y-less-rafsi? initial-pair y / hy-rafsi / stressed-hy-rafsi)

I found this nice page where I can check a PEG myself without having to write a parser: http://pegjs.majda.cz/online and these changes do seem to finally fix the problem.

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.