Received: from mail-lb0-f191.google.com ([209.85.217.191]:51298) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Xpe8U-0007xR-QW; Sat, 15 Nov 2014 06:15:37 -0800 Received: by mail-lb0-f191.google.com with SMTP id u10sf682030lbd.8 for ; Sat, 15 Nov 2014 06:15:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type; bh=JBwsjI1xFwiQsfzjy37xEXTAfPacGpxGaRszHPzOfRg=; b=OxWtv0Tc6yv6ys5agbDJsf8UR6Jp7AAdXoqyUiqKQJ8Nov73TfNbnsi935G404t60d +M8DxpLUh2U+Vu6X6I7ylnFXHtE2Hd4sSzXuBbO9qAHWIyD+aDyD2IrOUU2kG8K46bpr w298kkDER0RsJsYKQK870zVewlAtoxcjY4MjXDeWNylXi8G4pyrYyRoZLygwhocxM6ng AzBb0xxmGnHQIRyZez5vdACK9czq1GS0MjEUhZrBBf9Fg1oXIbA+VzcJpniuQhbNG6i+ WSSXqx5i2hoewhUE0mHu3cQrw4yZ5PuJtR+oEG2qIPe2EePtfpI37rGtEHmCQErV3ozX erXA== X-Received: by 10.152.7.100 with SMTP id i4mr956220laa.1.1416060927358; Sat, 15 Nov 2014 06:15:27 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.26.228 with SMTP id o4ls928690lag.66.gmail; Sat, 15 Nov 2014 06:15:26 -0800 (PST) X-Received: by 10.112.162.6 with SMTP id xw6mr11623614lbb.4.1416060926853; Sat, 15 Nov 2014 06:15:26 -0800 (PST) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com. [2a00:1450:4010:c04::22b]) by gmr-mx.google.com with ESMTPS id sg7si1514370lbb.1.2014.11.15.06.15.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Nov 2014 06:15:26 -0800 (PST) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c04::22b as permitted sender) client-ip=2a00:1450:4010:c04::22b; Received: by mail-lb0-f171.google.com with SMTP id b6so14003277lbj.2 for ; Sat, 15 Nov 2014 06:15:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.173.100 with SMTP id bj4mr2147024lbc.78.1416060926683; Sat, 15 Nov 2014 06:15:26 -0800 (PST) Received: by 10.114.70.111 with HTTP; Sat, 15 Nov 2014 06:15:26 -0800 (PST) In-Reply-To: <5676AB4A25B640DEB6EE877F655D9D77@gmail.com> References: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> <2B42884AD9984C369994567E68611980@gmail.com> <5676AB4A25B640DEB6EE877F655D9D77@gmail.com> Date: Sat, 15 Nov 2014 11:15:26 -0300 Message-ID: Subject: Re: [bpfk] extended rafsi and a tosmabru/slinku'i boondoggle From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c04::22b as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , Content-Type: multipart/alternative; boundary=001a11c2406683f1ff0507e6602e X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --001a11c2406683f1ff0507e6602e Content-Type: text/plain; charset=UTF-8 On Sun, Nov 9, 2014 at 6:26 PM, Alex Burka 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. --001a11c2406683f1ff0507e6602e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= 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&quo= t; 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, "spo= rte'y" is not deemed to be a slinku'i and "sporte'ysk= e" goes through.

So I'm adding these two = new rules:

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

stressed-hy-rafsi =3D (long-rafsi stress=
ed-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-r=
afsi / 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 fi= nally fix the problem.

mu'o mi'e xorxes

--
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.
--001a11c2406683f1ff0507e6602e--