Date: Tue, 9 Jun 2015 21:20:39 -0700 (PDT)
From: spheniscine@gmail.com
To: bpfk-list@googlegroups.com
Message-Id: <e674a174-2457-4457-b1cc-6470142509a6@googlegroups.com>
In-Reply-To: <CAO7tK2fEkfS77_U72=QTXx7D7+_b3yr_cSxxeNHSKQAqUeZK1g@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>
 <983f5a31-9fc4-426b-9565-a315d23b6d84@googlegroups.com>
 <CAO7tK2fEkfS77_U72=QTXx7D7+_b3yr_cSxxeNHSKQAqUeZK1g@mail.gmail.com>
Subject: Re: [bpfk] Re: Grammar of letterals and numerals in {li}
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_283_83142152.1433910039264"
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: -2.0
X-Spam_score_int: -19
X-Spam_bar: --
Content-Length: 4105

------=_Part_283_83142152.1433910039264
Content-Type: multipart/alternative; 
	boundary="----=_Part_284_1505778114.1433910039264"

------=_Part_284_1505778114.1433910039264
Content-Type: text/plain; charset=UTF-8


> I guess I don't really see the many problems. I have fallen, and seen 
> others fall, into the "abu za'u re'u cusku" trap and similar traps many 
> times. I don't recall seeing things like "li 827266128281627362816Z" or 
> even like "li R2D2" much in use. 
>

It isn't about how common it is; it is that your proposal will make it such 
that there aren't any good solutions for arbitrary character strings 
anymore. Many established and proposed conventions (jo'au*, my proposed 
date system, Pierre's coordinate system)  also depend on arbitrary 
character strings, often heavy in digits.

* {jo'au}, under my halfway proposal, could be patched by using {mo'e me'o 
cylyly pa pi'e pa jo'au}
 

>
> Having to decide when digits can be mixed with letters and when they can't 
> would introduce more usage difficulties in my opinion. I just don't see 
> lerfu-strings being used that much, let alone ones containing digits.
>

LI...LOhO is the only exception; I don't see what's so difficult to grasp 
about that. 

-- 
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_284_1505778114.1433910039264
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><blockquote class=3D"gmail_quote" style=3D"margin: 0;m=
argin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir=
=3D"ltr"><div class=3D"gmail_quote"><div>I guess I don't really see the man=
y problems. I have fallen, and seen others fall, into the "abu za'u re'u cu=
sku" trap and similar traps many times. I don't recall seeing things like "=
li 827266128281627362816Z" or even like "li R2D2" much in use.&nbsp;</div><=
/div></div></blockquote><div><br></div><div>It isn't about how common it is=
; it is that your proposal will make it such that there aren't any good sol=
utions for arbitrary character strings anymore. Many established and propos=
ed conventions (jo'au*, my proposed date system, Pierre's coordinate system=
) &nbsp;also depend on arbitrary character strings, often heavy in digits.<=
/div><div><br></div><div>* {jo'au}, under my halfway proposal, could be pat=
ched by using {mo'e me'o cylyly pa pi'e pa jo'au}</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><br></div><div>Having to decide when digits can be mixed wi=
th letters and when they can't would introduce more usage difficulties in m=
y opinion. I just don't see lerfu-strings being used that much, let alone o=
nes containing digits.</div></div></div></blockquote><div><br></div><div>LI=
...LOhO is the only exception; I don't see what's so difficult to grasp abo=
ut that.&nbsp;</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_284_1505778114.1433910039264--
------=_Part_283_83142152.1433910039264--