Received: from mail-lb0-f184.google.com ([209.85.217.184]:40736) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XmWL4-000079-UT; Thu, 06 Nov 2014 15:19:44 -0800 Received: by mail-lb0-f184.google.com with SMTP id z11sf134211lbi.1 for ; Thu, 06 Nov 2014 15:19:31 -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=2kLkSbQmFJVEySsr/hxaC2eT+g/m2tkqtRog0o1I+K0=; b=YoyQUBIur6M6wAd9MTy/sg5tzSMdrZakO7VnllelCyXPZMa5YVBxXKcKb/Dfm7QAA1 p0Qu2Z+8mQius1LoGpJu+SdSR4vknz4K9Tf4Wsi3FsR08pTBY3FWLPHdd8Tsw+ca7uLv dqFD/Pi33TWQGIJRj1QEwaUGooCFfJ3uHeeNUXztaskq4NxZD/9kGnaN4k68Z1UEllKF kA23TutYi/rozA+2VHag72oKHTi8pKgnWbb7E7Q/nHZuccECFD9V5EMTiimch6EeIWSR iJxeh5FGFAb1E1xhpvqGW2AwEIUhytp0zu/8YF1L2KiTSAbzNTMWy3gUoUEgwkx03/25 /0Rg== X-Received: by 10.180.72.71 with SMTP id b7mr152659wiv.20.1415315971226; Thu, 06 Nov 2014 15:19:31 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.103.163 with SMTP id fx3ls1245451wib.46.canary; Thu, 06 Nov 2014 15:19:30 -0800 (PST) X-Received: by 10.181.11.193 with SMTP id ek1mr106360wid.0.1415315970861; Thu, 06 Nov 2014 15:19:30 -0800 (PST) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com. [2a00:1450:400c:c05::229]) by gmr-mx.google.com with ESMTPS id p14si985179wie.1.2014.11.06.15.19.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Nov 2014 15:19:30 -0800 (PST) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) client-ip=2a00:1450:400c:c05::229; Received: by mail-wi0-f169.google.com with SMTP id n3so2904172wiv.2 for ; Thu, 06 Nov 2014 15:19:30 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.207.77 with SMTP id lu13mr19453326wic.12.1415315970770; Thu, 06 Nov 2014 15:19:30 -0800 (PST) Received: by 10.217.105.201 with HTTP; Thu, 6 Nov 2014 15:19:30 -0800 (PST) In-Reply-To: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> References: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> Date: Thu, 6 Nov 2014 20:19:30 -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::229 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=001a11c3a16aaecb93050738eda5 X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --001a11c3a16aaecb93050738eda5 Content-Type: text/plain; charset=UTF-8 On Thu, Nov 6, 2014 at 7:12 PM, Alex Burka wrote: > This word came up on IRC today: > > ?{.esporte'yske} > > (Assume for the sake of argument that the extended rafsi stress fix, noted > recently by la xorxes, has been applied.) > > Now, camxes says this is a tosmabru: *{.e sporte'yske}. Note that > {sporte'yske} by itself _does_ parse. It is a lujvo formed from *{sporte} > and {saske}. But *{sporte} is a slinku'i! So how can it show up in a lujvo? > > Is this a limitation of extended rafsi (we can't really make a lujvo > including a fu'ivla whose first consonant cluster is a valid initial > cluster, or something along those lines), or is it a bug in the grammar? > It's just a bug. The extended rafsi part of the morphology was never thoroughly tested, so it's good that people are starting to look at it. This *may* be the fix: 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) / brivla-rafsi Adding the "/ brivla-rafsi" at the end. I'd be grateful if you can check it. ki'e 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. --001a11c3a16aaecb93050738eda5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Nov 6, 2014 at 7:12 PM, Alex Burka <durka42@gmail.com><= /span> wrote:
This word came up on IRC today:

?{.esporte'yske}
(Assume for the sake of argument that the extended rafsi stres= s fix, noted recently by la xorxes, has been applied.)

=
Now, camxes says this is a tosmabru: *{.e sporte'yske}. Note that = {sporte'yske} by itself _does_ parse. It is a lujvo formed from *{sport= e} and {saske}. But *{sporte} is a slinku'i! So how can it show up in a= lujvo?

Is this a limitation of extended rafsi (we= can't really make a lujvo including a fu'ivla whose first consonan= t cluster is a valid initial cluster, or something along those lines), or i= s it a bug in the grammar?

It's j= ust a bug. The extended rafsi part of the morphology was never thoroughly t= ested, so it's good that people are starting to look at it. This *may* = be the fix:
=C2=A0
rafsi-string <- y-less-rafsi* (gismu =
/ CVV-final-rafsi / stressed-y-less-rafsi short-final-rafsi / y-rafsi / str=
essed-y-rafsi / stressed-y-less-rafsi? initial-pair y) / brivla-rafsi

Adding the "/ brivla-rafsi" at th= e end. I'd be grateful if you can check it.

ki= 'e 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.
--001a11c3a16aaecb93050738eda5--