Received: from mail-lb0-f189.google.com ([209.85.217.189]:33021) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1Ycd76-0000c6-St; Mon, 30 Mar 2015 10:04:43 -0700 Received: by lbiv14 with SMTP id v14sf10715135lbi.0; Mon, 30 Mar 2015 10:04:18 -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=SUskkC7RbfuAXmHFBMxpp/P/23Ba1K+i/TtA9fZ13BE=; b=h3fQhp4MSw3CgnLXYEld40I2S7ELzp1xryP/dcjtXjZlW/9XOrIWqsytXsD8dwqpTl HEA575F9u+q8cD5Bm1BizM6z+M7yiNqAV/J5xjh8cTm2tL5AdlatzZKZXxYuMzCiTpAp SL7PDH2wpX3OGR0KkG31zDdmoxqJ0t9dn2YYhvWGD3VpnKKhgc762tBWBFrcryUiAAL/ DilXthq5MRmu1irexSWHlvWkdKdSmcjl1aj7GhgC7Ovuc5lfiPvUYh4NsDqpO0cBUD73 7mybpdrcKIEgMOX7pgX60JbRsEurFSiOYB9F3oDVBHqr9WaTDwLWnjplW3xHsdiqgJHr aeqQ== X-Received: by 10.152.43.200 with SMTP id y8mr9148lal.41.1427735058381; Mon, 30 Mar 2015 10:04:18 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.37.194 with SMTP id a2ls540895lak.88.gmail; Mon, 30 Mar 2015 10:04:17 -0700 (PDT) X-Received: by 10.112.142.1 with SMTP id rs1mr7360231lbb.19.1427735057897; Mon, 30 Mar 2015 10:04:17 -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 a14si361834wib.3.2015.03.30.10.04.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2015 10:04:17 -0700 (PDT) Received-SPF: pass (google.com: domain of gleki.is.my.name@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 ne17so38811987wic.0; Mon, 30 Mar 2015 10:04:17 -0700 (PDT) X-Received: by 10.180.81.104 with SMTP id z8mr24640052wix.23.1427735057746; Mon, 30 Mar 2015 10:04:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.240.197 with HTTP; Mon, 30 Mar 2015 10:03:57 -0700 (PDT) From: Gleki Arxokuna Date: Mon, 30 Mar 2015 20:03:57 +0300 Message-ID: Subject: [bpfk] Two meanings of {bu} To: "lojban@googlegroups.com" , bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=f46d04426b64f3538605128478de 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::234 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.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - Content-Length: 6967 --f46d04426b64f3538605128478de Content-Type: text/plain; charset=UTF-8 1. {bu} is used after vowels to anaphorically reference LA/LE-sumti with sumti tails that start with the same vowel. 2. {bu} is proposed by gejyspa in {nu bu} and {du'u bu} to reference sumti that have sumti tails that start (or probably contain at main level) {nu} or {du'u} abstractions. This immediately raises a question: can a {nu bu} according to rule 1. reference {lo nupre}? If not 2. is indeed a new rule. 3. {bu} is proposed to be used in mekso to reference certain symbols like {.alfas. bu} for alpha. Probably it's about {me'o .alfas. bu} since we are talking about formulae. In this case it doesn't conflict with 1. and 2. and just adds this new third rule, namely, that inside {me'o} strings such constructs as {abu}, {nu bu}, {.alfas. bu} get a new meaning strictly defined in the dictionary. 4. Using {denpa bu} for "dot" without {me'o} can't fit into rules 1. and 2. From rule 1. and 2. we can assume that it anaphorically references {LE/LA denpa}. Neither using {.alfas. bu} without {me'o} can reference the symbol alpha. Instead, it would reference {la .alfas.}. 5. Neither {uibu} can be used without {me'o} to denote smileys. If {denpa bu} and {.alfas. bu} can be used without {me'o} to reference dots and alpha symbols then a,e,i,o,u, nu,du'u are exclusions to this rule. And in this case we aren't able to reference "a" as a symbol without {me'o} since {abu} is always an anaphorical marker. So my proposal is: 1. to always use {me'o} to reference symbols or to use fu'ivla for them like {denpabu} and {slakabu}. 2. The letteral meanings of uibu, denpa bu, slaka bu are to be defined in the dictionary. 3. {denpa bu} means {lo denpa} referenced anaphorically, it is close to {le} explained here or ri'oi . But even more correctly would be to show two examples identical in meaning: a) {lo denpa cu pendo mi .ije dy. xendo} b) {lo denpa cu pendo mi .ije denpa bu xendo} Clearly, {denpa bu prenu bu} would reference {lo denpa prenu} (no matter how often one would need that). {mi bu} would refer to {lo mi broda}. {ca bu} would refer to {lo ca broda} or {i ca broda} and thus be similar to {lo go'oi }. Interesting that in past people suggested using different {SOMETHING bu} to mark keyboard keys. No wonder {a bu} was never suggested as a name of A keyboard key because it's already taken by an anaphorical construct. -- 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. --f46d04426b64f3538605128478de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
1. {bu} is used after vowels to anaphorically reference LA= /LE-sumti with sumti tails that start with the same vowel.
2. {bu} is p= roposed by gejyspa in {nu bu} and {du'u bu} to reference sumti that hav= e sumti tails that start (or probably contain at main level) {nu} or {du= 9;u} abstractions.

This immediately raises a quest= ion: can a {nu bu} according to rule 1. reference {lo nupre}? If not 2. is = indeed a new rule.

3. {bu} is proposed to be used = in mekso to reference certain symbols like {.alfas. bu} for alpha. Probably= it's about {me'o .alfas. bu} since we are talking about formulae. = In this case it doesn't conflict with 1. and 2. and just adds this new = third rule, namely, that inside {me'o} strings such constructs as {abu}= , {nu bu}, {.alfas. bu} get a new meaning strictly defined in the dictionar= y.

4. Using {denpa bu} for "dot" without= {me'o} can't fit into rules 1. and 2. From rule 1. and 2. we can a= ssume that it anaphorically references {LE/LA denpa}. Neither using {.alfas= . bu} without {me'o} can reference the symbol alpha. Instead, it would = reference {la .alfas.}.

5. Neither {uibu} can be u= sed without {me'o} to denote smileys.

If {denp= a bu} and {.alfas. bu} can be used without {me'o} to reference dots and= alpha symbols then a,e,i,o,u, nu,du'u are exclusions to this rule. And= in this case we aren't able to reference "a" as a symbol wit= hout {me'o} since {abu} is always an anaphorical marker.

=
So my proposal is:
1. to always use {me'o} to = reference symbols or to use fu'ivla for them like {denpabu} and {slakab= u}.
2. The letteral meanings of uibu, denpa bu, slaka bu are to b= e defined in the dictionary.
3. {denpa bu} means {lo denpa} refer= enced anaphorically, it is close to {le} explained here=C2=A0or ri'oi. But even more correctly wou= ld be to show two examples identical in meaning:

a= ) {lo denpa cu pendo mi .ije dy. xendo}
b)=C2=A0{lo denpa cu pend= o mi .ije denpa bu xendo}

Clearly, {denpa bu prenu= bu} would reference {lo denpa prenu} (no matter how often one would need t= hat).

{mi bu} would refer to {lo mi broda}.
<= div>
{ca bu} would refer to {lo ca broda} or {i ca broda} and= thus be similar to {lo go'oi}.

Interesting that in past peopl= e suggested using different {SOMETHING bu} to mark keyboard keys. No wonder= {a bu} was never suggested as a name of A keyboard key because it's al= ready taken by an anaphorical construct.

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