Received: from mail-la0-f62.google.com ([209.85.215.62]:33467) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Z1iK3-0001hT-75; Sun, 07 Jun 2015 14:41:44 -0700 Received: by lams18 with SMTP id s18sf7052442lam.0; Sun, 07 Jun 2015 14:41:31 -0700 (PDT) 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 :content-type: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; bh=+437RPB192u3uHPToHldHYX7sp9tOoDgx28arwvaU5U=; b=lrJNJVYxwt6E8mtQn7QKOhMcKARTyfonT5zLZjDKAD+kiVnrlfqrJpsZkdLQm/1SxT svmAuwr3DCWoB9N19/fPNZduzRtCeaMV65qdxNEzo60i6VlKDHLemP4B9rCvzOCQ5Eba XhNfe+HSePGcIiH6aEkV/27TH9sfwQcpWb8o1LSkNDlGui6UCQwdOCfeodSehg1OzwhH m7+SPXbIF5SXA6tAGrRsi5a/XHolgU6ge/VBKevUedvgHG99wX1Jx0ACS2HIRJxyggLK GQPbfPMn47n+En+VYdWQqBzSsPOxZp1UHLfd9CJzEpaLERzozfaGF2+HZxenuYpCkAhL vquA== X-Received: by 10.152.42.138 with SMTP id o10mr139751lal.31.1433713291755; Sun, 07 Jun 2015 14:41:31 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.115.161 with SMTP id jp1ls548165lab.96.gmail; Sun, 07 Jun 2015 14:41:31 -0700 (PDT) X-Received: by 10.112.122.13 with SMTP id lo13mr13907665lbb.5.1433713291164; Sun, 07 Jun 2015 14:41:31 -0700 (PDT) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com. [2a00:1450:400c:c05::229]) by gmr-mx.google.com with ESMTPS id gt9si171321wib.2.2015.06.07.14.41.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 Jun 2015 14:41:31 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) client-ip=2a00:1450:400c:c05::229; Received: by mail-wi0-x229.google.com with SMTP id d19so67545593wiw.0 for ; Sun, 07 Jun 2015 14:41:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.206.65 with SMTP id lm1mr26506440wjc.117.1433713291046; Sun, 07 Jun 2015 14:41:31 -0700 (PDT) Received: by 10.27.26.17 with HTTP; Sun, 7 Jun 2015 14:41:30 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Jun 2015 18:41:30 -0300 Message-ID: Subject: Re: [bpfk] Re: Grammar of letterals and numerals in {li} From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=047d7b8739d26c36170517f46396 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:400c:c05::229 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: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - Content-Length: 4216 --047d7b8739d26c36170517f46396 Content-Type: text/plain; charset=UTF-8 On Sun, Jun 7, 2015 at 10:50 AM, wrote: > I just wanted to say this. > > I see the problem with the {abu za'u re'u cusku} examples; but all those > happen *outside* LI...LOhO. They can be fixed without affecting the grammar > *inside* LI...LOhO. > > It isn't just about my date system, but also arbitrary character strings; > what if you are trying to spell out a character string like > 2164763278536578236z ? You'd start reading it as a number without appending > {bu} to everything, but then suddenly run into a *mabla vlale'u*. > Would you read it as a number in English though? "Two sixtillions one hundred and sixty-four quintillions ... two hundred and thirty-six zee" (if you are in the US) or "two quadrillions one hundred and sixty-four thousand seven hundred and sixty-three trillions ... and thirty-six zed". I think if it's an arbitrary string of characters, it makes more sense to read it as characters, not as a number. I do not see any advantage to affecting LI...LOhO. > One advantage would be not having two separate rules. mu'o mi'e xorxes -- 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. --047d7b8739d26c36170517f46396 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Jun 7, 2015 at 10:50 AM, <spheniscine@gmail.com> wrote:
I just want= ed to say this.

I see the problem with the {abu za'u= re'u cusku} examples; but all those happen *outside* LI...LOhO. They c= an be fixed without affecting the grammar *inside* LI...LOhO.=C2=A0

It isn't just about my date system, but also arbitrar= y character strings; what if you are trying to spell out a character string= like 2164763278536578236z ? You'd start reading it as a number without= appending {bu} to everything, but then suddenly run into a mabla vlale&= #39;u.

Would you read it as= a number in English though? "Two sixtillions one hundred and sixty-fo= ur quintillions ... two hundred and thirty-six zee" (if you are in the= US) or "two quadrillions one hundred and sixty-four thousand seven hu= ndred and sixty-three trillions ... and thirty-six zed". I think if it= 's an arbitrary string of characters, it makes more sense to read it as= characters, not as a number.

I do not see any advantage to affecting LI...LO= hO.

One advantage would be not = having two separate rules.

mu'o mi'e xorxe= s

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