Received: from mail-qg0-f61.google.com ([209.85.192.61]:34032) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Z1vg8-0001oH-Os; Mon, 08 Jun 2015 04:57:27 -0700 Received: by qgdz60 with SMTP id z60sf30763784qgd.1; Mon, 08 Jun 2015 04:57:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type:x-original-sender:reply-to:precedence :mailing-list:list-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe; bh=JOXO0cB71Omu1MlBtJ2Loj4WVIhVBflB0JPr3yaKIh0=; b=o5GlPvgZ0z0mVk+kN+ZGXVGA9lv3v9xXV7+9kXI3e78T8uXKqBGSfDIBpNuZPFVzQI v7eC5w5zYwf4KUIGlbJ7WisQHVq0b2mfYlw+J3E2QVGSzS7ux4rvgncMtYXSwj4VTOMq 54dDIz//l0EAhhkeiPUzlXyEn4fGOwzqcvQbsHgTAroevR1e3JRav//TO8mfQRiPmYTV xJDOa3r/OnEEBLHiucAzhM2yDCMGdm2GNzdeG+gPPhbJiPAvsn2WQHM3oSTCLs3YLDoc QhJciU17GBTsujpYamJktLnH38Cn2WsFNMXr8ESRH0yyc3oKye5CfJKRs1fTpsFL/MRF QEOQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type:x-original-sender:reply-to:precedence :mailing-list:list-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe; bh=JOXO0cB71Omu1MlBtJ2Loj4WVIhVBflB0JPr3yaKIh0=; b=Ch5vrQEATH2BKQKqfFzYEHMR9Nt/t4Qc7vPlSHlZWzxo/VvPFjgqm89A2FYSy0MVUp JeOO2waXU1UDVy5tdkRAlYEcP0HCz1yjeLX5XEUojD5+8Ykg0dRgJBGm5qb6Wy8ttpDR 2rYS44tnG1kQqQKjUk3nOFTluHS6rRS/AyQI4mZhSFU6q/norIUZ6NchIVFyUYZoHbwl eOu3dkhOWCTP62fYL2TvVUWSmQRROCtvU6yyqmxK2U0HvJRj7m6N83fcFai5BGg11P5B tEczPLHasXINUE+l67EuK4sUHpQLzZ9FvGzFIDxpnmEA/UI3Fo3U6TVp2fqpEbmBJdFs PYMw== X-Received: by 10.50.152.37 with SMTP id uv5mr137980igb.0.1433764632718; Mon, 08 Jun 2015 04:57:12 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.107.11.193 with SMTP id 62ls755209iol.10.gmail; Mon, 08 Jun 2015 04:57:12 -0700 (PDT) X-Received: by 10.50.136.166 with SMTP id qb6mr157570igb.2.1433764632417; Mon, 08 Jun 2015 04:57:12 -0700 (PDT) Date: Mon, 8 Jun 2015 04:57:11 -0700 (PDT) From: spheniscine@gmail.com To: bpfk-list@googlegroups.com Cc: spheniscine@gmail.com Message-Id: <69108030-6005-444c-830a-26aac6447cbc@googlegroups.com> In-Reply-To: References: Subject: Re: [bpfk] Re: Grammar of letterals and numerals in {li} MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2264_2085622104.1433764631804" X-Original-Sender: spheniscine@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.1 (---) X-Spam_score: -3.1 X-Spam_score_int: -30 X-Spam_bar: --- ------=_Part_2264_2085622104.1433764631804 Content-Type: multipart/alternative; boundary="----=_Part_2265_1822615594.1433764631804" ------=_Part_2265_1822615594.1433764631804 Content-Type: text/plain; charset=UTF-8 > > One advantage would be not having two separate rules. > I don't see why that's such a problem. The grammar of LI...LOhO is already unique; that's why it's its own selma'o. And I don't think there are any serious attempts to combine it with any other selma'o, unlike sumtcita. *(Just declare all words to be in selma'o UI, then there'd be no more problems anymore. zo'o)* But seriously, if LI...LOhO is messed with, breaking the functionality of {me'o} (and {li'ai}, which under your proposal might actually be now needed to quote things like R2D2 {li'ai ry re dy re} instead of using it as a bare sumti), we'd be forced to come up with a new selma'o just so we can quote arbitrary character strings without attaching {bu} to every nacle'u. -- 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. ------=_Part_2265_1822615594.1433764631804 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
One adva= ntage would be not having two separate rules.
I don't see why that's such a problem. The grammar of LI...LOh= O is already unique; that's why it's its own selma'o. And I don't think the= re are any serious attempts to combine it with any other selma'o, unlike su= mtcita.

(Just declare all words to be in selma'= o UI, then there'd be no more problems anymore. zo'o)

=
But seriously, if LI...LOhO is messed with, breaking the fun= ctionality of {me'o} (and {li'ai}, which under your proposal might actually= be now needed to quote things like R2D2 {li'ai ry re dy re} instead of usi= ng it as a bare sumti), we'd be forced to come up with a new selma'o just s= o we can quote arbitrary character strings without attaching {bu} to every = nacle'u.

--
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.
------=_Part_2265_1822615594.1433764631804-- ------=_Part_2264_2085622104.1433764631804--