Date: Mon, 8 Jun 2015 19:38:01 -0700 (PDT)
From: spheniscine@gmail.com
To: bpfk-list@googlegroups.com
Message-Id: <983f5a31-9fc4-426b-9565-a315d23b6d84@googlegroups.com>
In-Reply-To: <CAO7tK2em0FAp2Y5fZvCnjrBJtp9vwgRHi27ekNjnAi1wnVJm1Q@mail.gmail.com>
References: <CAO7bV+ibEzM0Pig3Ch5uHYtkWUzf+zWNi3UANbp+C7CqQ2T6ag@mail.gmail.com>
 <a043f08a-8832-49ec-8f96-8effb47f619b@googlegroups.com>
 <CAO7tK2de12cUviLUXbjhPKB8pHNVeUrO-1NauDj=qMzU+mP=Ew@mail.gmail.com>
 <CAEhjWWM6Yqm77jA8m1r3q3y6kXEi1DD9rQfp3bCVp662DcXXiw@mail.gmail.com>
 <69108030-6005-444c-830a-26aac6447cbc@googlegroups.com>
 <CAO7tK2em0FAp2Y5fZvCnjrBJtp9vwgRHi27ekNjnAi1wnVJm1Q@mail.gmail.com>
Subject: Re: [bpfk] Re: Grammar of letterals and numerals in {li}
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2931_773197363.1433817481144"
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
Sender: bpfk-list@googlegroups.com
X-Spam_score: -3.1
X-Spam_score_int: -30
X-Spam_bar: ---

------=_Part_2931_773197363.1433817481144
Content-Type: multipart/alternative; 
	boundary="----=_Part_2932_704531944.1433817481144"

------=_Part_2932_704531944.1433817481144
Content-Type: text/plain; charset=UTF-8


>
> If I understand correctly, you are proposing that "operand" would no 
> longer be "quantifier" or "lerfu-string" (among other things) but some new 
> mixed entity. Whether this is a problem or not depends on your idea of 
> simplicity, and whether or not it's worth striving for.
>

The thing is in this particular context, it's causing so many problems. 
Simplicity is worth it up to a point, but not when it causes so many 
problems.

Don't get me wrong; I actually support your proposal. I'm just trying to 
come to a compromise for what I and others see is the part of it that 
causes the most problems, for the least benefit.
 

> We now have to attach "bu" to every vowel, is that so different? 
> Lerfu-strings are relatively rare in usage. I just don't see much need to 
> have special rules for them.
>
>
For one thing there is an experimental letteral series that uses a'y, e'y, 
i'y, o'y, and u'y (however, it's not been decided what to do with y'y under 
this system). For another thing, it introduces opacity to the Lojban 
numeral system. They are embarrassingly simple compared to most other 
languages in that they are read out nacle'u by nacle'u. Having to figure 
out when {bu} needs to be added to them before reading any character string 
aloud ruins that simplicity.

It's like this. "abu, ebu" etc are treated as one "word" in people's minds, 
and represent the letters {a} and {e}. However, deciding when to use {pa} 
and when to use {pabu}, when both are rendered as the simple numeral {1}, 
introduces practical usage difficulties.

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

------=_Part_2932_704531944.1433817481144
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin: 0;margi=
n-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir=3D"l=
tr"><div class=3D"gmail_quote"><div>If I understand correctly, you are prop=
osing that "operand" would no longer be "quantifier" or "lerfu-string" (amo=
ng other things) but some new mixed entity. Whether this is a problem or no=
t depends on your idea of simplicity, and whether or not it's worth strivin=
g for.</div></div></div></blockquote><div><br></div><div>The thing is in th=
is particular context, it's causing so many problems. Simplicity is worth i=
t up to a point, but not when it causes so many problems.</div><div><br></d=
iv><div>Don't get me wrong; I actually support your proposal. I'm just tryi=
ng to come to a compromise for what I and others see is the part of it that=
 causes the most problems, for the least benefit.</div><div>&nbsp;</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border=
-left: 1px #ccc solid;padding-left: 1ex;"><div dir=3D"ltr"><div class=3D"gm=
ail_quote"><div>We now have to attach "bu" to every vowel, is that so diffe=
rent? Lerfu-strings are relatively rare in usage. I just don't see much nee=
d to have special rules for them.</div><div><br></div></div></div></blockqu=
ote><div><br></div><div>For one thing there is an experimental letteral ser=
ies that uses a'y, e'y, i'y, o'y, and u'y (however, it's not been decided w=
hat to do with y'y under this system). For another thing, it introduces opa=
city to the Lojban numeral system. They are embarrassingly simple compared =
to most other languages in that they are read out nacle'u by nacle'u. Havin=
g to figure out when {bu} needs to be added to them before reading any char=
acter string aloud ruins that simplicity.</div><div><br></div><div>It's lik=
e this. "abu, ebu" etc are treated as one "word" in people's minds, and rep=
resent the letters {a} and {e}. However, deciding when to use {pa} and when=
 to use {pabu}, when both are rendered as the simple numeral {1}, introduce=
s practical usage difficulties.</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 />

------=_Part_2932_704531944.1433817481144--
------=_Part_2931_773197363.1433817481144--