Received: from mail-ie0-f187.google.com ([209.85.223.187]:33081) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YznTL-0008S6-7B; Tue, 02 Jun 2015 07:47:24 -0700 Received: by iebtr6 with SMTP id tr6sf41122049ieb.0; Tue, 02 Jun 2015 07:47:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :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=lmfFjfHZTDIvjhiMl2/Z8hS6J7owgdoQBllKgehF2JE=; b=ELtOvYJMFnhjDZKgV5wQRECI00M5W0SUQ3eLy5p/4xUUUSrn6nhBHaJhHrwPDpeS0O xJO+RQHuFaUAN84gG/ltma9Y97TWE4MJO6ttWqEbL/BcgjQTT2RVuO704iFgK2NNMo8z tRtSZO8nz29hpL7+vYr0iDx2HAH5X9oUIFIucmyHZ5aPKy96jar9VoRRy2EPK4/acxeL s0pnd2cfFrZDyeMEFvI0pqyTdFT+XYU10t2lUgTiCDK8c7qORQ/em3FsSpZyyfM7DxMD SYb0UO0Mfs8VF6mM6+CE67aih1O4UM8dXidAiqHIVb9KO8ZrxQF8bmA8vq7lQf02RRt9 NFSg== X-Received: by 10.50.64.179 with SMTP id p19mr254025igs.6.1433256432836; Tue, 02 Jun 2015 07:47:12 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.107.135.234 with SMTP id r103ls1922280ioi.67.gmail; Tue, 02 Jun 2015 07:47:12 -0700 (PDT) X-Received: by 10.43.80.195 with SMTP id zv3mr44537494icb.28.1433256432500; Tue, 02 Jun 2015 07:47:12 -0700 (PDT) Received: from mail-vn0-x232.google.com (mail-vn0-x232.google.com. [2607:f8b0:400c:c0f::232]) by gmr-mx.google.com with ESMTPS id z9si461725vdj.0.2015.06.02.07.47.12 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jun 2015 07:47:12 -0700 (PDT) Received-SPF: pass (google.com: domain of durka42@gmail.com designates 2607:f8b0:400c:c0f::232 as permitted sender) client-ip=2607:f8b0:400c:c0f::232; Received: by vnbf1 with SMTP id f1so20717361vnb.2 for ; Tue, 02 Jun 2015 07:47:12 -0700 (PDT) X-Received: by 10.52.135.4 with SMTP id po4mr26530019vdb.78.1433256432361; Tue, 02 Jun 2015 07:47:12 -0700 (PDT) Received: from Alexs-MacBook-Air-2.local (c-69-249-31-89.hsd1.pa.comcast.net. [69.249.31.89]) by mx.google.com with ESMTPSA id aj20sm27358122vdc.21.2015.06.02.07.47.11 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Jun 2015 07:47:11 -0700 (PDT) Date: Tue, 2 Jun 2015 10:47:12 -0400 From: Alex Burka To: bpfk-list@googlegroups.com Message-ID: In-Reply-To: References: Subject: Re: [bpfk] Grammar of letterals and numerals in {li} X-Mailer: Airmail Beta (308) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="556dc1f0_2f656ee6_8eb0" X-Original-Sender: durka42@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of durka42@gmail.com designates 2607:f8b0:400c:c0f::232 as permitted sender) smtp.mail=durka42@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: -3.0 (---) X-Spam_score: -3.0 X-Spam_score_int: -29 X-Spam_bar: --- Content-Length: 9445 --556dc1f0_2f656ee6_8eb0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Agreed, the biggest question for me (beyond whether this is a good idea at = all, zo'o zo'o nai) is what changes would be made to the grammar of LI? Wou= ld it be able to take a pure-lerfu string, a pure-digit string, but not a m= ixture? Or would we leave LI alone but create two new gadri selma'o that ta= ke pure-lerfu and pure-digit, respectively? mu'o mi'e durkavore On June 2, 2015 at 5:34:15 AM, Gleki Arxokuna (gleki.is.my.name@gmail.com) = wrote: 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=C2=A0: On Sun, May 31, 2015 at 2:09 PM, Spheniscine (la zipcpi)=C2=A0=C2=A0wrote: I've not heard of that proposal. Wouldn't that just break all uses of {xy p= a} when talking about the definitions of words?=C2=A0 Those are "xy xi pa". The contexts where we don't want digits and lerfu to mix (e.g. ".abu za'u r= e'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 the = 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=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 reasonable. Besides, {me'o} still works, paralleling the use of strings for entry of IS= O 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 ways 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 meks= o which is a special subset of Lojban with its own grammar. {by} as a anaphorical marker and {by} within {li} are two different entitie= s. 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 prop= osal then? -- 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. --=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. --556dc1f0_2f656ee6_8eb0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =
Agreed, the biggest question for me (beyond whethe= r this is a good idea at all, zo'o zo'o nai) is what changes would be made = to the grammar of LI? Would it be able to take a pure-lerfu string, a pure-= digit string, but not a mixture? Or would we leave LI alone but create two = new gadri selma'o that take pure-lerfu and pure-digit, respectively?
=
mu'o m= i'e durkavore

On Ju= ne 2, 2015 at 5:34:15 AM, Gleki Arxokuna (gleki.is.my.name@gmail.com) wrote:

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 = <jjllambias@gm= ail.com>:


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 {xy 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 the 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 ways 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?
--
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 ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://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.
--556dc1f0_2f656ee6_8eb0--