Received: from mail-la0-f64.google.com ([209.85.215.64]:34000) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Yzsj1-00047z-3Q; Tue, 02 Jun 2015 13:23:53 -0700 Received: by labgd6 with SMTP id gd6sf52730822lab.1; Tue, 02 Jun 2015 13:23:44 -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=q2+xSPYTkf8g//h5Ptg9k7Bi5LJu3I8No/sG76coPmk=; b=CxynLuPT5dHchdslhMTRt8wLNCDVTXBoPmpg2ZUYFz1fyJ/HodvBMgQyjsVtnMa6xc o8B+Gr3MgAtM+cWUK35E3D9ojDZz7X2/HF40zNaYh2b0zjTWAsVNxMI7IpmTp2QE/7Sr nCF8y7GaeeTlerB9/h0KFAGr5V5R419dBfc9XeQ1/bAZweKglf4Nt7A5demc4Nm4zE5q APzsqDVxCeCG27pwz0xYIKb4SjJ7qa00Q/44nEMoyWatypUhTYacl9WVM0LenSiuSPJb 4so/9c70mVcnFuNm9cD3QVbL96Hnv1ZlCiVm0ulcfGkNctRmTsz9PhhYMDM+q+Vx2RK2 AFHg== X-Received: by 10.180.39.205 with SMTP id r13mr125715wik.2.1433276624018; Tue, 02 Jun 2015 13:23:44 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.91.231 with SMTP id ch7ls996172wib.47.gmail; Tue, 02 Jun 2015 13:23:43 -0700 (PDT) X-Received: by 10.194.47.179 with SMTP id e19mr27241264wjn.4.1433276623761; Tue, 02 Jun 2015 13:23:43 -0700 (PDT) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com. [2a00:1450:400c:c05::234]) by gmr-mx.google.com with ESMTPS id t6si719820wiz.0.2015.06.02.13.23.43 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jun 2015 13:23:43 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::234 as permitted sender) client-ip=2a00:1450:400c:c05::234; Received: by mail-wi0-x234.google.com with SMTP id d19so30890730wiw.0 for ; Tue, 02 Jun 2015 13:23:43 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.106.6 with SMTP id gq6mr34768013wib.39.1433276623685; Tue, 02 Jun 2015 13:23:43 -0700 (PDT) Received: by 10.27.26.17 with HTTP; Tue, 2 Jun 2015 13:23:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 2 Jun 2015 17:23:43 -0300 Message-ID: Subject: Re: [bpfk] 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=f46d044519a5050b7a05178eb8dc 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::234 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: -3.0 (---) X-Spam_score: -3.0 X-Spam_score_int: -29 X-Spam_bar: --- Content-Length: 4264 --f46d044519a5050b7a05178eb8dc Content-Type: text/plain; charset=UTF-8 On Tue, Jun 2, 2015 at 11:47 AM, Alex Burka wrote: > 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? > None. It only affects "number" and "lerfu-string" directly. li-clause remains the same: li-clause <- LI-clause free* mex LOhO-clause? free* Would it be able to take a pure-lerfu string, a pure-digit string, but not > a mixture? > Among other things, yes. It still takes any mex. > Or would we leave LI alone but create two new gadri selma'o that take > pure-lerfu and pure-digit, respectively? > We leave LI alone and we don't create anything new. 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. --f46d044519a5050b7a05178eb8dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Jun 2, 2015 at 11:47 AM, Alex Burka <durka42@gmail.com>= wrote:
Agreed, the biggest question for me (beyond whether this is a good i= dea at all, zo'o zo'o nai) is what changes would be made to the gra= mmar of LI?

None. It only affec= ts "number" and "lerfu-string" directly. li-clause rema= ins the same:
li-clause <- LI-clause free* mex LOhO-clause? fre=
e*=C2=A0
Would it be able to take a pure-lerfu string, a pure-digit string, bu= t not a mixture?

Among other th= ings, yes. It still takes any mex.
=C2=A0
=
Or would we leave LI alone = but create two new gadri selma'o that take pure-lerfu and pure-digit, r= espectively?

We leave LI alone and we don't create anything new.

mu'o mi'e x= orxes

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