Received: from mail-lb0-f190.google.com ([209.85.217.190]:34305) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YziaR-000429-H2; Tue, 02 Jun 2015 02:34:27 -0700 Received: by lbdu14 with SMTP id u14sf46144531lbd.1; Tue, 02 Jun 2015 02:34:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:from:date:message-id:subject: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=HyxZrFlL3n1dHbZ6IV44FK+Imgw1y/R0wxTwKShCDII=; b=TIu0Kww8qWtglE6Zq3GCd3h47pAcw3zF6F6CICHKJdUXPiyXj5v4y5mGBcvPpVlI0q OSXxeIMjpWwZ1BCVnzPA7YH35hc5IRGG1DbD9FlcgWUYAR5ZOrwDxoMKHkcCslYV3mFt 3dO+U8Tpart9Sh4/jxmC3IiyWIGNlyBrN21e8SyOrEUwfOvEny29tOphBWh6vO6n6Qxr 7BPYyVJIszy9DajjN4WjQzXGkmHuMRklVD7Issz6GPUAwwR/lOM/1iudVAHqIKamENLW YaWdkiJOO23e9IZptQkwqrHrLf84TGDFyKjMuNPGfnhwUh7wRJaxzjLL9Z5rnqD5mzKc WrMQ== X-Received: by 10.152.44.135 with SMTP id e7mr269837lam.23.1433237652052; Tue, 02 Jun 2015 02:34:12 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.22.10 with SMTP id z10ls757614lae.24.gmail; Tue, 02 Jun 2015 02:34:11 -0700 (PDT) X-Received: by 10.112.122.13 with SMTP id lo13mr10935312lbb.5.1433237651091; Tue, 02 Jun 2015 02:34:11 -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 ec7si632894wib.3.2015.06.02.02.34.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jun 2015 02:34:11 -0700 (PDT) Received-SPF: pass (google.com: domain of gleki.is.my.name@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 dq8so52737968wib.1 for ; Tue, 02 Jun 2015 02:34:11 -0700 (PDT) X-Received: by 10.180.90.228 with SMTP id bz4mr29266209wib.69.1433237650951; Tue, 02 Jun 2015 02:34:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.221.167 with HTTP; Tue, 2 Jun 2015 02:33:49 -0700 (PDT) From: Gleki Arxokuna Date: Tue, 2 Jun 2015 12:33:49 +0300 Message-ID: Subject: [bpfk] Grammar of letterals and numerals in {li} To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=f46d043be0a61056d8051785a5e9 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::229 as permitted sender) smtp.mail=gleki.is.my.name@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: 6887 --f46d043be0a61056d8051785a5e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Namely, that mixed lerfu/number strings should be banned. xorxe's vision quoted at the end of this message. 2015-05-31 20:51 GMT+03:00 Jorge Llamb=C3=ADas : > > > On Sun, May 31, 2015 at 2:09 PM, Spheniscine (la zipcpi) < > spheniscine@gmail.com> wrote: > >> I've not heard of that proposal. Wouldn't that just break all uses of {x= y >> pa} when talking about the definitions of words? >> > > Those are "xy xi pa". > > The contexts where we don't want digits and lerfu to mix (e.g. ".abu za'u > re'u cusku", "by re mei", "lo re bolci zo'u pa by xunre .i je pa by blanu= ", > "xy xi pa dunda xy xi re xy xi ci" etc. are much much more common than th= e > need for mixed strings, and having to use "boi" for those is a pain. > So they are to be currently: abu boi za'u re'u cusku i by boi re mei i lo re bolci zo'u pa boi by xunre .i je pa boi by blanu i xy xi pa dunda xy xi re boi xy xi ci I can agree that it can be a pain so this proposal may sound reasonable. > > Besides, {me'o} still works, paralleling the use of strings for entry of >> ISO dates in programming languages. I just prefer {li} because >> >> - It's shorter >> - Dates and periods technically *are* numbers in a certain sense; >> arithmetic can be performed on them, despite the fact that in some wa= ys >> they don't act like real-numbers, due to the varying length of months= and >> years. >> >> "me'o" and "li" are in the same selma'o, so the issue is the same for > both. > I can't agree with changing anything within {li}, however. {li} is for mekso which is a special subset of Lojban with its own grammar. {by} as a anaphorical marker and {by} within {li} are two different entities. Terminating {li} with {boi} or {lo'o} isn't that hard IMO. But how would "(n+1.3)^(3.15*r^2)" be expressed under this new xorxe's proposal then? --=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. --f46d043be0a61056d8051785a5e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Namely, that mixed lerfu/number strings should be banned.<= div>
xorxe's vision quoted at the end of this message.

2015-05-31 20:51 GMT+03:00 Jorge Llamb=C3=ADas=C2=A0<jjllambias@gmail.com>:


=
On Sun, May 31, 2015 at 2:09 PM= , Spheniscine (la zipcpi)=C2=A0<spheniscine@gmail.com>= =C2=A0wrote:
I've not heard of tha= t proposal. Wouldn't that just break all uses of {xy pa} when talking a= bout the definitions of words?=C2=A0

Those are "xy xi pa".

The context= s where we don't want digits and lerfu to mix (e.g. ".abu za'u= re'u cusku", "by re mei", "lo re bolci zo'u pa= by xunre .i je pa by blanu", "xy xi pa dunda xy xi re xy xi ci&q= uot; etc. are much much more common than the need for mixed strings, and ha= ving to use "boi" for those is a pain.

So they are to be currently:
abu bo= i za'u re'u cusku=C2=A0
i by boi re mei=C2=A0
i= lo re bolci zo'u pa boi by xunre=C2=A0
.i je pa boi by blanu= =C2=A0
i xy xi pa dunda xy xi re boi xy xi ci=C2=A0

=
I can agree that it can be a pain so this proposal may sound reasonabl= e.

Besides, {me'o} still works, paralleling the use of st= rings for entry of ISO dates in programming languages. I just prefer {li} b= ecause
  • It's shorter
  • Dates and periods technic= ally *are* numbers in a certain sense; arithmetic can be performed on them,= despite the fact that in some ways they don't act like real-numbers, d= ue to the varying length of months and years.
"me'o" and "li" are in the same se= lma'o, so the issue is the same for both.

I can't agree with changing anything within = {li}, however. {li} is for mekso which is a special subset of Lojban with i= ts own grammar.

{by} as a anaphorical marker and {= by} within {li} are two different entities.
Terminating {li} with= {boi} or {lo'o} isn't that hard IMO.

But = how would "(n+1.3)^(3.15*r^2)" be expressed under this new xorxe&= #39;s proposal then?

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