Received: from mail-wi0-f183.google.com ([209.85.212.183]:52249) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XnYx3-0008IF-Vy; Sun, 09 Nov 2014 12:19:15 -0800 Received: by mail-wi0-f183.google.com with SMTP id hi2sf532780wib.10 for ; Sun, 09 Nov 2014 12:19:03 -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=OhyuXmo2M17CvT3JILm+syUO6b1U06k6AUsTnVRq+CA=; b=HvDYuwL2IoaxKYcPGNipYpo7SpvUSEMneNk0NIsRPEv7MueApJ6D/WgRFMvsolUpMc yjxFVhuNd2PYpxTWhAlfbTaLKj4zsd/Ga3Xw2hZOaPlasjuIvtjHb93tp27NgiE4u5Xk n9ZUV7DfSKA0IpgUT0bTNA4YQAr0wetpJm94TF70b+vQOHYLewGfokIf0Ef6HbcVvfwR pvYxCqwjQb3HjBanL+MXukW7ge5XN8yWe0vkJ9Kk9J4LTEgphAoavUkVt36Ze66mwtLP JGIhn39n461xwbne15HnXjP99eRlud30RoT/g88z8PSCH5gSihwlM6yBLiwKcxApjRX5 PZqg== X-Received: by 10.152.37.194 with SMTP id a2mr354lak.6.1415564342860; Sun, 09 Nov 2014 12:19:02 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.5.38 with SMTP id p6ls381634lap.64.gmail; Sun, 09 Nov 2014 12:19:02 -0800 (PST) X-Received: by 10.152.7.73 with SMTP id h9mr13291laa.6.1415564342080; Sun, 09 Nov 2014 12:19:02 -0800 (PST) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com. [2a00:1450:400c:c05::231]) by gmr-mx.google.com with ESMTPS id n9si607792wix.0.2014.11.09.12.19.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Nov 2014 12:19:02 -0800 (PST) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::231 as permitted sender) client-ip=2a00:1450:400c:c05::231; Received: by mail-wi0-f177.google.com with SMTP id ex7so8619082wid.16 for ; Sun, 09 Nov 2014 12:19:02 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.79.169 with SMTP id k9mr24949379wix.34.1415564341896; Sun, 09 Nov 2014 12:19:01 -0800 (PST) Received: by 10.217.105.201 with HTTP; Sun, 9 Nov 2014 12:19:01 -0800 (PST) In-Reply-To: References: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> <2B42884AD9984C369994567E68611980@gmail.com> Date: Sun, 9 Nov 2014 17:19:01 -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:400c:c05::231 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=f46d04428d1ec16c1b050772c1fb X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --f46d04428d1ec16c1b050772c1fb Content-Type: text/plain; charset=UTF-8 On Fri, Nov 7, 2014 at 4:19 PM, Alex Burka wrote: > I'm looking at the parse tree for "sporte'y" as a brivla_rafsi and I > don't understand it, because it shows "sporte" as a brivla_head. But that > should never happen because brivla_head has a !slinkuhi guard. What's going > on? > OK, I think I figured it out. The problem is that because "orte'y" is a brivla rafsi, it thinks that "porte'y" is a slinku'i, and so "sporte'y" is fine. An additional problem with the slinku'i change is that it will also not accept "sprageti'y" as a rafsi because "prageti'y" is one, but "sprageti" is not a slinku'i! So, we must go back to the original slinkuhi rule, and we add instead three final cases to the rafsi-string rule: slinkuhi <- consonant rafsi-string 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 / long-rafsi vowel h y / CCV-rafsi h y / CVV-rafsi h y) And I think we need to add the !h in this one as well: y-less-rafsi <- !y-rafsi (CVC-rafsi !y / CCV-rafsi / CVV-rafsi) !h !any-extended-rafsi Fingers crossed. 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. --f46d04428d1ec16c1b050772c1fb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Nov 7, 2014 at 4:19 PM, Alex Burka <durka42@gmail.com><= /span> wrote:
I'm looking at the parse tree for "sporte'= y" as a brivla_rafsi and I don't understand it, because it shows &= quot;sporte" as a brivla_head. But that should never happen because br= ivla_head has a !slinkuhi guard. What's going on?

OK, I think I figured it out. The problem is that because = "orte'y" is a brivla rafsi, it thinks that "porte'y&= quot; is a slinku'i, and so "sporte'y" is fine. An additi= onal problem with the slinku'i change is that it will also not accept &= quot;sprageti'y" as a rafsi because "prageti'y" is o= ne, but "sprageti" is not a slinku'i!

So, we must go back to the original slinkuhi rule, and we add instead thr= ee final cases to the rafsi-string rule:

slinkuhi <- =
consonant rafsi-string=20

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 / long-rafsi vowel h y / CCV-rafsi h y / CVV-rafsi h y)

And I think we need to add the !h in this o= ne as well:

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

Fi= ngers crossed.

mu'o mi'e xorxes
=
=C2=A0

--
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.
--f46d04428d1ec16c1b050772c1fb--