Received-SPF: pass (google.com: domain of nictytan@gmail.com designates 2607:f8b0:400d:c04::22c as permitted sender) client-ip=2607:f8b0:400d:c04::22c;
MIME-Version: 1.0
In-Reply-To: <CAEimHHDjS+i9xMy2dPbMM-uTEukgM9PyOGTE3f-g93K-87A17A@mail.gmail.com>
References: <CAEimHHDjS+i9xMy2dPbMM-uTEukgM9PyOGTE3f-g93K-87A17A@mail.gmail.com>
From: Jacob Errington <nictytan@gmail.com>
Date: Sun, 11 Jan 2015 01:03:36 -0500
Message-ID: <CAOQ8VDW80-wL6yF2VP-3t5qCq46X8XHampwKUO1pzJtsF6dERw@mail.gmail.com>
Subject: Re: [lojban] lo broda be fa lo brode
To: "lojban@googlegroups.com" <lojban@googlegroups.com>
Content-Type: multipart/alternative; boundary=001a11c116c0b3dda8050c5a27a9
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
X-Spam_score: 0.8
X-Spam_score_int: 8
X-Spam_bar: /
X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org",
 has NOT identified this incoming email as spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 @@CONTACT_ADDRESS@@ for details.
 
 Content preview:  In considering cases like that, I wanted to clarify (to myself
    at least) how exactly {be} works, and in doing so wrote a post to the mailing
    list some months ago, which I thereafter consolidated into an article on
   the wiki. My understanding of {lo broda be ko'a} is exactly the one given
   in the article. [...] 
 
 Content analysis details:   (0.8 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: googlegroups.com]
  2.7 DNS_FROM_AHBL_RHSBL    RBL: Envelope sender listed in dnsbl.ahbl.org
                             [listed in googlegroups.com.rhsbl.ahbl.org.	IN]
                             [A]
 -0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
                             [209.85.213.187 listed in wl.mailspike.net]
  0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                             domains are different
 -0.0 SPF_PASS               SPF: sender matches SPF record
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (nictytan[at]gmail.com)
  0.0 DKIM_ADSP_CUSTOM_MED   No valid author signature, adsp_override is
                             CUSTOM_MED
  0.0 HTML_MESSAGE           BODY: HTML included in message
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
 -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
  0.0 T_FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and
                             EnvelopeFrom freemail headers are different
 -0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders

--001a11c116c0b3dda8050c5a27a9
Content-Type: text/plain; charset=UTF-8

In considering cases like that, I wanted to clarify (to myself at least)
how exactly {be} works, and in doing so wrote a post to the mailing list
some months ago, which I thereafter consolidated into an article on the
wiki. My understanding of {lo broda be ko'a} is exactly the one given in
the article.

http://mw.lojban.org/lmw/Advanced_Place_Structure_Mangling

I also think it's the most consistent understanding of how {be} works,
since it doesn't invoke any magic, and it is basically exceptionless.

.i mi'e la tsani mu'o

On 8 January 2015 at 15:49, Luke Bergen <lukeabergen@gmail.com> wrote:

> Gotten a little rusty over the past year and was running through the CLL
> again as a refresher and while reading through chapter 5 a question
> occurred to me.
>
> If {lo broda} is roughly: "something which fills the x1 place of broda",
> then are {lo broda be fa lo brode} and {lo broda poi/noi/NOI ke'a brode}
> equivalent?
>
> If not equivalent, is it a major distinction or merely a subtle difference
> of flavor?
>
> Most helpfully, when (if) would you use one over the other?
>
> --
> You received this message because you are subscribed to the Google Groups
> "lojban" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to lojban+unsubscribe@googlegroups.com.
> To post to this group, send email to lojban@googlegroups.com.
> Visit this group at http://groups.google.com/group/lojban.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--001a11c116c0b3dda8050c5a27a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In considering cases like that, I wanted to clarify (to my=
self at least) how exactly {be} works, and in doing so wrote a post to the =
mailing list some months ago, which I thereafter consolidated into an artic=
le on the wiki. My understanding of {lo broda be ko&#39;a} is exactly the o=
ne given in the article.<br><br><a href=3D"http://mw.lojban.org/lmw/Advance=
d_Place_Structure_Mangling">http://mw.lojban.org/lmw/Advanced_Place_Structu=
re_Mangling</a><br><br>I also think it&#39;s the most consistent understand=
ing of how {be} works, since it doesn&#39;t invoke any magic, and it is bas=
ically exceptionless.<br><br>.i mi&#39;e la tsani mu&#39;o<br></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On 8 January 2015 at 15:=
49, Luke Bergen <span dir=3D"ltr">&lt;<a href=3D"mailto:lukeabergen@gmail.c=
om" target=3D"_blank">lukeabergen@gmail.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr">Gotten a little rusty over the pa=
st year and was running through the CLL again as a refresher and while read=
ing through chapter 5 a question occurred to me.<div><br></div><div>If {lo =
broda} is roughly: &quot;something which fills the x1 place of broda&quot;,=
 then are {lo broda be fa lo brode} and {lo broda poi/noi/NOI ke&#39;a brod=
e} equivalent?</div><div><br></div><div>If not equivalent, is it a major di=
stinction or merely a subtle difference of flavor?</div><div><br></div><div=
>Most helpfully, when (if) would you use one over the other?</div></div><sp=
an class=3D"HOEnZb"><font color=3D"#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com" target=3D"_b=
lank">lojban+unsubscribe@googlegroups.com</a>.<br>
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com" target=3D"_blank">lojban@googlegroups.com</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/group/lojban" targe=
t=3D"_blank">http://groups.google.com/group/lojban</a>.<br>
For more options, visit <a href=3D"https://groups.google.com/d/optout" targ=
et=3D"_blank">https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote></div><br></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com">lojban+unsub=
scribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com">lojban@googlegroups.com</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/group/lojban">http:=
//groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

--001a11c116c0b3dda8050c5a27a9--