Received: from mail-oi0-f61.google.com ([209.85.218.61]:65425) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XpuRE-0007Yo-Sj; Sat, 15 Nov 2014 23:40:04 -0800 Received: by mail-oi0-f61.google.com with SMTP id a141sf1032337oig.6 for ; Sat, 15 Nov 2014 23:39:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :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=xm4hMc45iL9ZmtXQv7UBWYnxl2KMglEAfDRWYBIKmw8=; b=nR+NyqdgHJzAqA6mr46hbxfYoIQMGei5tu7qc3JiYpycjstsUrihxnjKQrfhkMQ8m1 BWpOD1ywP3GnRYqRUSSMQ5B+DyXxs10wQQLkYPqZvpnEonTuCNyRsZk8M9M1cpOWPdIx LxIlLynhuHWACIalZAo1KoQum3VzPJfDygV2Y8XBu2oXamZdpiDtkpxt8uKmLBqIFw+o uOiy4Rc7FFrrRsC9GYAXyEGF9QU7ZgcrT6zZ4YWacuD+Y65URFqJdGVFSQ4MXzGEtesL t7BWQJiThvMXpRtBJwjMjx1J4kesRZ8bMOiRQP7qQXI+GWAXulINYUh6KyOg8gfgfHRf Ir5A== X-Received: by 10.50.30.98 with SMTP id r2mr194593igh.10.1416123594103; Sat, 15 Nov 2014 23:39:54 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.107.19.220 with SMTP id 89ls302645iot.107.gmail; Sat, 15 Nov 2014 23:39:53 -0800 (PST) X-Received: by 10.66.100.131 with SMTP id ey3mr7131923pab.8.1416123593617; Sat, 15 Nov 2014 23:39:53 -0800 (PST) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com. [2607:f8b0:400d:c00::234]) by gmr-mx.google.com with ESMTPS id kb8si7910675qcb.1.2014.11.15.23.39.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Nov 2014 23:39:53 -0800 (PST) Received-SPF: pass (google.com: domain of durka42@gmail.com designates 2607:f8b0:400d:c00::234 as permitted sender) client-ip=2607:f8b0:400d:c00::234; Received: by mail-qa0-f52.google.com with SMTP id u7so13019970qaz.39 for ; Sat, 15 Nov 2014 23:39:53 -0800 (PST) X-Received: by 10.229.239.3 with SMTP id ku3mr23893221qcb.22.1416123593453; Sat, 15 Nov 2014 23:39:53 -0800 (PST) Received: from [192.168.1.2] (c-69-249-31-89.hsd1.nj.comcast.net. [69.249.31.89]) by mx.google.com with ESMTPSA id a12sm31444607qai.1.2014.11.15.23.39.51 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 15 Nov 2014 23:39:51 -0800 (PST) Date: Sun, 16 Nov 2014 02:39:44 -0500 From: Alex Burka To: bpfk-list@googlegroups.com Message-ID: <5875A54BD3484C8E83827592067DC7AA@gmail.com> In-Reply-To: References: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> <2B42884AD9984C369994567E68611980@gmail.com> <5676AB4A25B640DEB6EE877F655D9D77@gmail.com> Subject: Re: [bpfk] extended rafsi and a tosmabru/slinku'i boondoggle X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 X-Original-Sender: durka42@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of durka42@gmail.com designates 2607:f8b0:400d:c00::234 as permitted sender) smtp.mail=durka42@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="546854c0_324c140e_13b" X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 11937 --546854c0_324c140e_13b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'll put these in. Did you intentionally remove the !y guard from y_less_ra= fsi? Before, I have =20 y-less-rafsi <- !y-rafsi ( CVC-rafsi !y / CCV-rafsi / CVV-rafsi ) !any-exte= nded-rafsi mu'o mi'e la durkavore =20 On Saturday, November 15, 2014 at 4:53 PM, Jorge Llamb=C3=ADas wrote: > =20 > =20 > On Sat, Nov 15, 2014 at 2:05 PM, Jorge Llamb=C3=ADas wrote: > > On Sat, Nov 15, 2014 at 11:15 AM, Jorge Llamb=C3=ADas wrote: > > > =20 > > > hy-rafsi =3D (long-rafsi vowel / CCV-rafsi / CVV-rafsi) h y h? > > > =20 > > > stressed-hy-rafsi =3D (long-rafsi stressed-vowel / stressed-CCV-rafsi= / stressed-CVV-rafsi) h y h? =20 > > > =20 > > > y-less-rafsi <- !y-rafsi !stressed-y-rafsi !hy-rafsi !stressed-hy-raf= si (CVC-rafsi / CCV-rafsi / CVV-rafsi) !h !any-extended-rafsi =20 > > > =20 > > > rafsi-string <- y-less-rafsi* (gismu / CVV-final-rafsi / stressed-y-l= ess-rafsi short-final-rafsi / y-rafsi / stressed-y-rafsi / stressed-y-less-= rafsi? initial-pair y / hy-rafsi / stressed-hy-rafsi) =20 > > > =20 > > > 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 t= o finally fix the problem. > > =20 > > But not quite. The sporte'y cases are fixed, but "slinku'i'yske" slips = by for some reason. "slinku'i'ysaske", "slinkau'yske", "sku'iske" are all s= uccessfully blocked, so the problem seems to be with some slinku'i that end= in CV'V with final stress. I'll have to keep investigating. > =20 > OK, I think I found the glitch. Some further changes: > =20 > slinkuhi <- !rafsi-string consonant rafsi-string =20 > =20 > initial-rafsi <- extended-rafsi / y-rafsi / !any-extended-rafsi y-less-ra= fsi !any-extended-rafsi > =20 > y-less-rafsi <- !y-rafsi !stressed-y-rafsi !hy-rafsi !stressed-hy-rafsi (= CVC-rafsi / CCV-rafsi / CVV-rafsi) !h =20 > =20 > i.e. I moved the !any-extended-rafsi up from the y-less-rafsi rule to the= initial-rafsi rule. I also excluded rafsi strings from satisfying the slin= ku'i rule, otherwise things like "smabru'yske" get excluded. Now all the br= ivla rafsi that I tested work as expected, blocking all the slinku'i cases.= =20 > =20 > mu'o mi'e xorxes > =20 > -- =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= email to bpfk-list+unsubscribe@googlegroups.com (mailto:bpfk-list+unsubscr= ibe@googlegroups.com). > To post to this group, send email to bpfk-list@googlegroups.com (mailto:b= pfk-list@googlegroups.com). > Visit this group at http://groups.google.com/group/bpfk-list. > For more options, visit https://groups.google.com/d/optout. --=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. --546854c0_324c140e_13b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I'll put these in. Did you intentionally remove the !y = guard from y_less_rafsi? Before, I have

y-less-rafsi <- !y-rafsi ( CVC= -rafsi !y / CCV-rafsi / CVV-rafsi ) !any-extended-rafsi
mu'o mi'e la durkavore
=20

On Saturday, November 15, 2014= at 4:53 PM, Jorge Llamb=C3=ADas wrote:



On S= at, Nov 15, 2014 at 2:05 PM, Jorge Llamb=C3=ADas <jjllambias@gmail.com<= /a>> wrote:
On Sat, Nov 15, 2014 at 11= :15 AM, Jorge Llamb=C3=ADas <jjllambias@gmail.com> wrote:=

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

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

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

rafsi-string <- y-less-rafsi* (gismu / CVV-fi=
nal-rafsi / stressed-y-less-rafsi short-final-rafsi / y-rafsi / stressed-y-=
rafsi / stressed-y-less-rafsi? initial-pair y / hy-rafsi / stressed-hy-rafs=
i)

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 cha= nges do seem to finally fix the problem.

But not quite. The sporte'y cases are fixed, b= ut "slinku'i'yske" slips by for some reason. "slinku'i'ysaske", "slinkau'ys= ke", "sku'iske" are all successfully blocked, so the problem seems to be wi= th some slinku'i that end in CV'V with final stress. I'll have to keep inve= stigating.

OK, I th= ink I found the glitch. Some further changes:

slinkuhi = <- !rafsi-string consonant rafsi-string

=
initi=
al-rafsi <- extended-rafsi / y-rafsi / !any-extended-rafsi y-less-rafsi =
!any-extended-rafsi

y-less-rafsi <- !y-rafsi=
 !stressed-y-rafsi !hy-rafsi !stressed-hy-rafsi (CVC-rafsi / CCV-rafsi / CV=
V-rafsi) !h

i.e. I moved the !any-extended-rafsi up fro= m the y-less-rafsi rule to the initial-rafsi rule. I also excluded rafsi st= rings from satisfying the slinku'i rule, otherwise things like "smabru'yske= " get excluded. Now all the brivla rafsi that I tested work as expected, bl= ocking all the slinku'i cases. 

mu'o mi'e xor= xes

--
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 ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
=20 =20 =20 =20
=20

=20

--
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.
--546854c0_324c140e_13b--