Received: from mail-la0-f57.google.com ([209.85.215.57]:41029) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XpgqC-0001Dc-DK; Sat, 15 Nov 2014 09:08:54 -0800 Received: by mail-la0-f57.google.com with SMTP id s18sf240223lam.2 for ; Sat, 15 Nov 2014 09:08:45 -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=6DFy65LBZSIZAW9r2JoGQkrL7w+oSwnMSmhT02T4h6Y=; b=hgJIqyp3kIjthdGNyBeDJPzp3Y99hKkNtERHrSznvf+w8GAT2YdRWHp6VWOK811NM9 RKFmBMn3nGnl/BvoCKq6pH5fCQgHCOuoHr9yMBdHsKRkOovVe4/h8EOV8dED/zsCfoM0 RIU6mOU7lhWR5laOFMEWj2sWv70+J7rXygOL1zC/S0dZWacKx9LLQXDlA4mgVgaPfQHU IS3DdRYPDgrl4xcjRcERfNIaMoI4xGOaKBe0yZgjfrOUvH0z1o11kttub9p9gFKNPOoy DrXrjDF4PkDTOYyqF0yTAxeODIewXa/dEKzYHS7bRktADWAqgsDVKbL31Fmj7jtBFdLY dLFA== X-Received: by 10.152.87.205 with SMTP id ba13mr537451lab.5.1416071324889; Sat, 15 Nov 2014 09:08:44 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.28.137 with SMTP id b9ls476599lah.29.gmail; Sat, 15 Nov 2014 09:08:44 -0800 (PST) X-Received: by 10.112.201.169 with SMTP id kb9mr9609lbc.20.1416071323924; Sat, 15 Nov 2014 09:08:43 -0800 (PST) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com. [2a00:1450:400c:c00::233]) by gmr-mx.google.com with ESMTPS id r13si334840wib.0.2014.11.15.09.08.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Nov 2014 09:08:43 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c00::233 as permitted sender) client-ip=2a00:1450:400c:c00::233; Received: by mail-wg0-f51.google.com with SMTP id k14so2406595wgh.24 for ; Sat, 15 Nov 2014 09:08:43 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.11.65 with SMTP id o1mr17790674wib.22.1416071323788; Sat, 15 Nov 2014 09:08:43 -0800 (PST) Received: by 10.194.103.65 with HTTP; Sat, 15 Nov 2014 09:08:43 -0800 (PST) In-Reply-To: References: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> <2B42884AD9984C369994567E68611980@gmail.com> <5676AB4A25B640DEB6EE877F655D9D77@gmail.com> Date: Sat, 15 Nov 2014 20:08:43 +0300 Message-ID: Subject: Re: [bpfk] extended rafsi and a tosmabru/slinku'i boondoggle From: Gleki Arxokuna To: bpfk-list@googlegroups.com X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c00::233 as permitted sender) smtp.mail=gleki.is.my.name@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=001a11c259bc3b2a300507e8cc8b X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 8348 --001a11c259bc3b2a300507e8cc8b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable What about checking for validity by humans? Humans wont be able to determine the validity of the resulting brivla on the fly if they use these numerous rules. cant something more simple be proposed (may be at the expense of losing some already valid brivla and/or allowing more forms) ? Who will take always their computer with them just to check words for validity? 2014-11-15 20:05 GMT+03:00 Jorge Llamb=C3=ADas : > > > On Sat, Nov 15, 2014 at 11:15 AM, Jorge Llamb=C3=ADas > 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-rafsi) h y h? >> >> >> 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-raf= si? 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. >> > > 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 > successfully 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. > > 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. > --=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. --001a11c259bc3b2a300507e8cc8b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
What about checking for validity by humans?
Humans won= t be able to determine the validity of the resulting brivla on the fly if t= hey use these numerous rules.

cant something more simple= be proposed (may be at the expense of losing some already valid brivla and= /or allowing more forms) ?

Who will take always th= eir computer with them just to check words for validity?
<= div class=3D"gmail_extra">
2014-11-15 20:05 G= MT+03:00 Jorge Llamb=C3=ADas <jjllambias@gmail.com>:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">


On Sat, Nov 15, 2014 at = 11:15 AM, Jorge Llamb=C3=ADas <jjllambias@gmail.com> wrot= e:

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

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

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

rafs=
i-string <- y-less-rafsi* (gismu / CVV-final-rafsi / stressed-y-less-raf=
si 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 cha= nges do seem to finally fix the problem.

But not quite. The sporte'y cases are fixe= d, but "slinku'i'yske" slips by for some reason. "sl= inku'i'ysaske", "slinkau'yske", "sku'is= ke" are all successfully 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.

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

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