Sender: lojban@googlegroups.com
Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2607:f8b0:400d:c09::22d as permitted sender) client-ip=2607:f8b0:400d:c09::22d;
MIME-Version: 1.0
In-Reply-To: <3cb1fc04-c3d0-3535-099e-30b8b120f219@gmx.de>
References: <3cb1fc04-c3d0-3535-099e-30b8b120f219@gmx.de>
From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= <jjllambias@gmail.com>
Date: Fri, 7 Oct 2016 19:37:18 -0300
Message-ID: <CAO7tK2dvRVjJCqBwSFv4rQFx19+=-5hWdm2ZwYS3=qvFMeMAng@mail.gmail.com>
Subject: Re: [lojban] A Simpler Quantifier Logic (blog article)
To: lojban@googlegroups.com
Content-Type: multipart/alternative; boundary=94eb2c056212909529053e4e0d58
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
X-Spam_score: -1.8
X-Spam_score_int: -17
X-Spam_bar: -

--94eb2c056212909529053e4e0d58
Content-Type: text/plain; charset=UTF-8

On Fri, Oct 7, 2016 at 9:10 AM, selpahi <seladwa@gmx.de> wrote:

>
> https://solpahi.wordpress.com/2016/09/25/a-simpler-quantifier-logic/


Nice. I agree with most of it, although I'm not too sure yet what I think
about ro and su'o becoming ro'oi and su'oi.

Have you thought about "su'e"? Presumably it should pattern with "ru'o",
not with "ro'oi", so the su'o/su'e symmetry would be broken if su'o becomes
su'oi.

Would "no" become "no'oi" as well?

We should also have explicit definitions for me'i, za'u, da'a, so'a, so'e,
etc since they all admit more than one pluralification, but I'm guessing
they would all follow the "ru'o" pattern as well.

mu'o mi'e xorxes

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Oct 7, 2016 at 9:10 AM, selpahi <span dir=3D"ltr">&lt;<a href=
=3D"mailto:seladwa@gmx.de" target=3D"_blank">seladwa@gmx.de</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><br>
<a href=3D"https://solpahi.wordpress.com/2016/09/25/a-simpler-quantifier-lo=
gic/" rel=3D"noreferrer" target=3D"_blank">https://solpahi.wordpress.com/<w=
br>2016/09/25/a-simpler-quantifie<wbr>r-logic/</a></blockquote><div><br></d=
iv><div>Nice. I agree with most of it, although I&#39;m not too sure yet wh=
at I think about ro and su&#39;o becoming ro&#39;oi and su&#39;oi.</div><di=
v><br></div><div>Have you thought about &quot;su&#39;e&quot;? Presumably it=
 should pattern with &quot;ru&#39;o&quot;, not with &quot;ro&#39;oi&quot;, =
so the su&#39;o/su&#39;e symmetry would be broken if su&#39;o becomes su=
9;oi.</div><div><br></div><div>Would &quot;no&quot; become &quot;no&#39;oi&=
quot; as well?=C2=A0</div><div><br></div><div>We should also have explicit =
definitions for me&#39;i, za&#39;u, da&#39;a, so&#39;a, so&#39;e, etc since=
 they all admit more than one pluralification, but I&#39;m guessing they wo=
uld all follow the &quot;ru&#39;o&quot; pattern as well.</div><div><br></di=
v><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;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com">lojban+unsub=
scribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com">lojban@googlegroups.com</a>.<br />
Visit this group at <a href=3D"https://groups.google.com/group/lojban">http=
s://groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

--94eb2c056212909529053e4e0d58--