Received: from mail-vn0-f61.google.com ([209.85.216.61]:33538) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Z1rwA-0007JK-5Y; Mon, 08 Jun 2015 00:57:47 -0700 Received: by vnbg129 with SMTP id g129sf29808997vnb.0; Mon, 08 Jun 2015 00:57: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=I5ArzmmcOv9LversNqndKqOxRlA8BqUiGqfBKa/0tzY=; b=Afe/i4rz8yZsTq2GYw+iQGc4rSWOg9vGw6Ckb4m9pCqJJyEj91Ngf3jtEMcBOl+zl4 tiU/EWgq6nYtaX9iBLwOVYQYa9d3vysdJAO0uaLjh8CwrQmHkzNePnKQEnZ0zwb7tYzd RTyvKo6B0mlP9mVBxKLsDlFrlBuOXnpF6VJuGqqyIFGnwYtyY7NNfqub9iuVf7Rm92zo XXoorpeLstD3rhdcJRnpFEev27zbbiqoSrtF9Iuvk3gAwzyio9Aruoaxq8nTj2OU6RYN 45FABL83WfzMvW4a59qIWU/QuWvy9rs01pP7R1xNKkIbPXpMKqHNskupdaqKWSW+Ly3e lLHQ== X-Received: by 10.140.48.11 with SMTP id n11mr163199qga.35.1433750251825; Mon, 08 Jun 2015 00:57:31 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.140.23.231 with SMTP id 94ls2688428qgp.24.gmail; Mon, 08 Jun 2015 00:57:31 -0700 (PDT) X-Received: by 10.52.86.166 with SMTP id q6mr22222168vdz.2.1433750251576; Mon, 08 Jun 2015 00:57:31 -0700 (PDT) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com. [2607:f8b0:400d:c04::231]) by gmr-mx.google.com with ESMTPS id lg9si208776qcb.1.2015.06.08.00.57.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jun 2015 00:57:31 -0700 (PDT) Received-SPF: pass (google.com: domain of spheniscine@gmail.com designates 2607:f8b0:400d:c04::231 as permitted sender) client-ip=2607:f8b0:400d:c04::231; Received: by mail-qg0-x231.google.com with SMTP id 3so21392258qgg.2 for ; Mon, 08 Jun 2015 00:57:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.146.205 with SMTP id 196mr18863448qhs.27.1433750251471; Mon, 08 Jun 2015 00:57:31 -0700 (PDT) Received: by 10.96.36.225 with HTTP; Mon, 8 Jun 2015 00:57:31 -0700 (PDT) In-Reply-To: References: Date: Mon, 8 Jun 2015 15:57:31 +0800 Message-ID: Subject: Re: [bpfk] Re: Grammar of letterals and numerals in {li} From: Jonathan Soo To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=001a11353c706f86a70517fcfeb3 X-Original-Sender: spheniscine@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of spheniscine@gmail.com designates 2607:f8b0:400d:c04::231 as permitted sender) smtp.mail=spheniscine@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: - --001a11353c706f86a70517fcfeb3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We don't do that in English because it is inconvenient. But Lojban numbers are different; they are read digit-by-digit, so it's actually *harder* to add {bu} to everything. On Mon, Jun 8, 2015 at 5:41 AM, Jorge Llamb=C3=ADas = wrote: > > > 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 gram= mar >> *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 append= ing >> {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 thousa= nd > 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 a topic in the > Google Groups "BPFK" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/bpfk-list/GQ9Mnwieue0/unsubscribe. > To unsubscribe from this group and all its topics, 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. > --=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. --001a11353c706f86a70517fcfeb3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We don't do that in English because it is inconvenient= . But Lojban numbers are different; they are read digit-by-digit, so it'= ;s actually *harder* to add {bu} to everything.

On Mon, Jun 8, 2015 at 5:41 AM, Jorge L= lamb=C3=ADas <jjllambias@gmail.com> wrote:


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

I s= ee the problem with the {abu za'u re'u cusku} examples; but all tho= se happen *outside* LI...LOhO. They can be fixed without affecting the gram= mar *inside* LI...LOhO.=C2=A0

It isn't just ab= out my date system, but also arbitrary character strings; what if you are t= rying to spell out a character string like 2164763278536578236z ? You'd= start reading it as a number without appending {bu} to everything, but the= n suddenly run into a mabla vlale'u.

Would you read it as a number in English though? &q= uot;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 c= haracters, 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&#= 39;e xorxes

--
You received this message because you are subscribed to a topic in the Goog= le Groups "BPFK" group.
To unsubscribe from this topic, visit https://groups= .google.com/d/topic/bpfk-list/GQ9Mnwieue0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bpfk-l= ist+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.

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