Received: from mail-qc0-f185.google.com ([209.85.216.185]:33568) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XmVIc-0006zc-3s; Thu, 06 Nov 2014 14:13:09 -0800 Received: by mail-qc0-f185.google.com with SMTP id l6sf256919qcy.22 for ; Thu, 06 Nov 2014 14:12:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id: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=KDkv8AjO+SLoR7omL3GIAdG5zJzZ/NxhtK8U+NGRVCM=; b=rT2WSV0LiJDVxqvfFSKgElK+eLdnF6QH7Mex6LsDxDNVhl0HcIS7bnufvLykhasZsm 0ku8M1opZkQLkqQo64SVIcE4Fl2oKD/PGLKi7zSRq0bb//+O1tWomiatpf/fPCNLkEyU VadTcewcwXUoHGT3rvN9R4udefj3zpLnNJD5AdZkQuKK2SLtCk33JiM44LEOGuh0nEZl R9SLTGDTmctQSEeT60iqaKPBMORnZW4ZvK3CE8/bGav6LQYmSyPdhdpu095gkwCmHN5v dGdJHMoy9CLQ1mxjktsNBfDxaDe7boICyfP+r2FxiXeRa8+Fgwrh02ZQ7oe4m6BVptGw i4IA== X-Received: by 10.50.79.132 with SMTP id j4mr559525igx.11.1415311975333; Thu, 06 Nov 2014 14:12:55 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.107.158.19 with SMTP id h19ls65898ioe.28.gmail; Thu, 06 Nov 2014 14:12:55 -0800 (PST) X-Received: by 10.42.118.75 with SMTP id w11mr5759098icq.5.1415311975035; Thu, 06 Nov 2014 14:12:55 -0800 (PST) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com. [2607:f8b0:400d:c00::22a]) by gmr-mx.google.com with ESMTPS id lu9si1979194qcb.0.2014.11.06.14.12.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Nov 2014 14:12:55 -0800 (PST) Received-SPF: pass (google.com: domain of durka42@gmail.com designates 2607:f8b0:400d:c00::22a as permitted sender) client-ip=2607:f8b0:400d:c00::22a; Received: by mail-qa0-f42.google.com with SMTP id k15so1483754qaq.1 for ; Thu, 06 Nov 2014 14:12:54 -0800 (PST) X-Received: by 10.140.51.99 with SMTP id t90mr10849922qga.72.1415311974906; Thu, 06 Nov 2014 14:12:54 -0800 (PST) Received: from [2607:f470:6:400d:30b7:db15:100::] ([2607:f470:6:400d:880:b672:7c24:402f]) by mx.google.com with ESMTPSA id k4sm6979647qaf.0.2014.11.06.14.12.53 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 06 Nov 2014 14:12:53 -0800 (PST) Date: Thu, 6 Nov 2014 17:12:52 -0500 From: Alex Burka To: bpfk-list@googlegroups.com Message-ID: <0ECDA8252DB74B6A924A302A02D55629@gmail.com> Subject: [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::22a 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="545bf264_744939a3_13b" X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --545bf264_744939a3_13b Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline 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? mu'o mi'e la durkavore -- 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. --545bf264_744939a3_13b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
This word came up on IRC today:

?{.esporte'yske}

(Assume for the sake of argument that the extended rafsi stress fi= x, 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 {sask= e}. 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 ma= ke a lujvo including a fu'ivla whose first consonant cluster is a valid ini= tial cluster, or something along those lines), or is it a bug in the gramma= r?

mu'o mi'e la durkavore

=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.
--545bf264_744939a3_13b--