Received: from mail-lb0-f188.google.com ([209.85.217.188]:54431)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.80.1)
	(envelope-from <bpfk-list+bncBCOZJTMR5YGRBTWFVGRQKGQE7ETYD6Q@googlegroups.com>)
	id 1XqTTD-00012P-25; Mon, 17 Nov 2014 13:04:36 -0800
Received: by mail-lb0-f188.google.com with SMTP id l4sf1676270lbv.5
        for <multiple recipients>; Mon, 17 Nov 2014 13:04:15 -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=S+zpfVLGuolnPWG7DgASuVQZHYzkdfs76k0GFKEqoJg=;
        b=ZBmjKRnauFxM1lSsxj8Y4anTyooO0fqB39vLgpn077ttKP1M/3arzv4z/ZhYaPPcd3
         Gb4apsrVnTe/6D08clxftxMGKw3QYM46Q6riezKeFVTnnV9HfVDnfuJaRYFT5Lavbm78
         h7E+nM4nlXs266mOIEISLMlnxaTqqFSMINNaLiX3iUCLISrO5iEPXIYongBekEyPQRLA
         gquISA87VOQ1FDFPSQLYmLrX7J0E+2cnNGW8pudwjWki7iSNL/QRKiTsDDn0alTUmiBO
         MWhs0Ccyv9b/nxUvaStbLXWlmwbKJ+sH5P1nrSQJYGqPWBtgz7OQL1u2yJuwFVIW9KvG
         DTrQ==
X-Received: by 10.152.22.7 with SMTP id z7mr47103lae.19.1416258255383;
        Mon, 17 Nov 2014 13:04:15 -0800 (PST)
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.152.10.39 with SMTP id f7ls1143617lab.75.gmail; Mon, 17 Nov
 2014 13:04:14 -0800 (PST)
X-Received: by 10.152.8.67 with SMTP id p3mr4683824laa.4.1416258254367;
        Mon, 17 Nov 2014 13:04:14 -0800 (PST)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com. [2a00:1450:4010:c03::22c])
        by gmr-mx.google.com with ESMTPS id jj5si696520lbc.0.2014.11.17.13.04.14
        for <bpfk-list@googlegroups.com>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 17 Nov 2014 13:04:14 -0800 (PST)
Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:4010:c03::22c as permitted sender) client-ip=2a00:1450:4010:c03::22c;
Received: by mail-la0-f44.google.com with SMTP id hz20so8966451lab.3
        for <bpfk-list@googlegroups.com>; Mon, 17 Nov 2014 13:04:14 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.41.168 with SMTP id g8mr30335046lbl.59.1416258254255;
 Mon, 17 Nov 2014 13:04:14 -0800 (PST)
Received: by 10.114.70.111 with HTTP; Mon, 17 Nov 2014 13:04:14 -0800 (PST)
In-Reply-To: <20141116202004.GK13604@mercury.ccil.org>
References: <2B42884AD9984C369994567E68611980@gmail.com>
	<BBAF1D8CFB81404881C8C6D1E4790DF6@gmail.com>
	<CAO7tK2ebtPZM3uFwhZPPqR_auDRXOnTV4hQuh+tVxKkaxV_zQQ@mail.gmail.com>
	<5676AB4A25B640DEB6EE877F655D9D77@gmail.com>
	<CAO7tK2fS4LZhZpMCchcjc_+RKTWuTNQ5KWHhL3eyFam0CHk8ig@mail.gmail.com>
	<CAO7tK2cgPLK45DvEn1ZsAA8HD4yTdDfBxOiOCxHWcr7JsVq1Dg@mail.gmail.com>
	<CAO7bV+j_8hPmHEMT_wq5x7tk8BwYO+Jpb-_4Gz6bzRn6Ek7CNQ@mail.gmail.com>
	<CAO7tK2fpTcm89FYxdmyg8kqUcYpx6pkWNZOoLRszRdB1ts6eLg@mail.gmail.com>
	<5467EDB6.6010304@gmx.de>
	<CAO7tK2dLjF6oRnKmP_g95oyJG9ky+Z4Sn-pWsOrgvXipehXBXQ@mail.gmail.com>
	<20141116202004.GK13604@mercury.ccil.org>
Date: Mon, 17 Nov 2014 18:04:14 -0300
Message-ID: <CAO7tK2cTtwe8zPLs8fKmadaxREoSs8Ju8GdutZCXpUHbbM5AFA@mail.gmail.com>
Subject: Re: [bpfk] extended rafsi and a tosmabru/slinku'i boondoggle
From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= <jjllambias@gmail.com>
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:4010:c03::22c
 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: <bpfk-list.googlegroups.com>
X-Google-Group-Id: 972099695765
List-Post: <http://groups.google.com/group/bpfk-list/post>, <mailto:bpfk-list@googlegroups.com>
List-Help: <http://groups.google.com/support/>, <mailto:bpfk-list+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/bpfk-list
Sender: bpfk-list@googlegroups.com
List-Subscribe: <http://groups.google.com/group/bpfk-list/subscribe>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+972099695765+unsubscribe@googlegroups.com>,
 <http://groups.google.com/group/bpfk-list/subscribe>
Content-Type: multipart/alternative; boundary=001a11345d7627ba9d05081452d5
X-Spam-Score: -1.9 (-)
X-Spam_score: -1.9
X-Spam_score_int: -18
X-Spam_bar: -
Content-Length: 4805

--001a11345d7627ba9d05081452d5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 16, 2014 at 5:20 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Jorge Llamb=C3=ADas scripsit:
>
> > Well, if we throw away rafsi but keep the look-and-feel of brivla, we c=
an
> > replace the current 35 rules that deal with brivla with just a single
> one:
>
> Of course, that puts us back before the 1983 GMR, the purpose of which
> was to reduce the number of colliding lujvo.  It's still possible to
> have semantic collisions between lujvo coined by different people to mean
> different things, but at least they are all decomposable in the same way.
>

Yep. An intermediate possibility would be to keep the rafsi system, but
discard the slinku'i exception. That would make the rules for brivla
recognition much simpler, so that for example slinku'i and sporte would be
valid fu'uvla, at the cost of requiring "y" in some more CVC- initial
lujvo. So for example, the first two lujvo that would be affected from the
jbovlaste alphabetical list are backemselrerkru, which would have to become
bacykemselrerkru, and badjamblo, which would have to become badyjamblo,
because ckemselrerkru and djamblo would be valid fu'ivla. The tosmabru rule
would also become simpler: -y- would be required whenever the final
consonant of an unstressed CVC- initial rafsi formed a valid onset when
combined with the onset of the following rafsi. No need to examine the
lujvo all the way to the first y or the end of the word, as is the case now=
.

mu'o mi'e xorxes.

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

--001a11345d7627ba9d05081452d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sun, Nov 16, 2014 at 5:20 PM, John Cowan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:cowan@mercury.ccil.org" target=3D"_blank">cowan@mercury.ccil.org=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jorge Llamb=C3=ADa=
s scripsit:<br>
<span class=3D""><br>
&gt; Well, if we throw away rafsi but keep the look-and-feel of brivla, we =
can<br>
&gt; replace the current 35 rules that deal with brivla with just a single =
one:<br>
<br>
</span>Of course, that puts us back before the 1983 GMR, the purpose of whi=
ch<br>
was to reduce the number of colliding lujvo.=C2=A0 It&#39;s still possible =
to<br>
have semantic collisions between lujvo coined by different people to mean<b=
r>
different things, but at least they are all decomposable in the same way.<b=
r></blockquote><div><br></div><div>Yep. An intermediate possibility would b=
e to keep the rafsi system, but discard the slinku&#39;i exception. That wo=
uld make the rules for brivla recognition much simpler, so that for example=
 slinku&#39;i and sporte would be valid fu&#39;uvla, at the cost of requiri=
ng &quot;y&quot; in some more CVC- initial lujvo. So for example, the first=
 two lujvo that would be affected from the jbovlaste alphabetical list are =
backemselrerkru, which would have to become bacykemselrerkru, and badjamblo=
, which would have to become badyjamblo, because ckemselrerkru and djamblo =
would be valid fu&#39;ivla. The tosmabru rule would also become simpler: -y=
- would be required whenever the final consonant of an unstressed CVC- init=
ial rafsi formed a valid onset when combined with the onset of the followin=
g rafsi. No need to examine the lujvo all the way to the first y or the end=
 of the word, as is the case now.</div><div><br></div><div>mu&#39;o mi&#39;=
e xorxes.</div><div><br></div></div></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;BPFK&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bpfk-list+unsubscribe@googlegroups.com">bpfk-list=
+unsubscribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href=3D"mailto:bpfk-list@googlegrou=
ps.com">bpfk-list@googlegroups.com</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/group/bpfk-list">ht=
tp://groups.google.com/group/bpfk-list</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

--001a11345d7627ba9d05081452d5--