Received: from mail-lb0-f185.google.com ([209.85.217.185]:57649) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1YFkQ8-00078o-JV for lojban-list-archive@lojban.org; Mon, 26 Jan 2015 06:13:41 -0800 Received: by mail-lb0-f185.google.com with SMTP id b6sf716642lbj.2 for ; Mon, 26 Jan 2015 06:13:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=gmciV47mZJR0dKeJdfJuaMlB+sOFrdERljTiOVoM46s=; b=e+VKN2P7N8oIcUh2y0yhF/mTCvcxpTG3krgGAMLRppMfyMeFgdHBoJEE8f3Kn1M/OT JqwEu8nZl+DusBcuw4jo93BeAnKpp5IPArzZU6GyfoQChUrUW49eWzas5VURdM3mZVAm bayMEn/WLukmpQE2WK5I3udkkO6c2ZVEV9eHeX834ndOtLVgTF4ifQffwRWTvqNPnJwd o2l3XjtRHt6eMbr534/UDh+2XATVYmgPxhbthPra0+BiIc3p51eF8FdH1+tnzUCnysg5 zjW555QfTOg2+t/41vMqop/xkZwy5TIEPn0atkNyTXGpLHB689LUvj72M9fKoizxhAOX 3ibA== X-Received: by 10.152.88.13 with SMTP id bc13mr105070lab.15.1422281613552; Mon, 26 Jan 2015 06:13:33 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.152.42.234 with SMTP id r10ls435701lal.17.gmail; Mon, 26 Jan 2015 06:13:32 -0800 (PST) X-Received: by 10.152.43.166 with SMTP id x6mr764064lal.3.1422281612699; Mon, 26 Jan 2015 06:13:32 -0800 (PST) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com. [2a00:1450:400c:c03::22c]) by gmr-mx.google.com with ESMTPS id s6si680978wif.0.2015.01.26.06.13.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 Jan 2015 06:13:32 -0800 (PST) Received-SPF: pass (google.com: domain of lurifax@gmail.com designates 2a00:1450:400c:c03::22c as permitted sender) client-ip=2a00:1450:400c:c03::22c; Received: by mail-we0-x22c.google.com with SMTP id q59so9258471wes.3 for ; Mon, 26 Jan 2015 06:13:32 -0800 (PST) X-Received: by 10.180.84.39 with SMTP id v7mr33561585wiy.5.1422281612578; Mon, 26 Jan 2015 06:13:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.229.130 with HTTP; Mon, 26 Jan 2015 06:13:11 -0800 (PST) Reply-To: lojban@googlegroups.com In-Reply-To: <54C63614.3060308@gmx.de> References: <54C6332A.6010907@gmail.com> <54C63614.3060308@gmx.de> From: =?UTF-8?Q?Dan_Ros=C3=A9n?= Date: Mon, 26 Jan 2015 15:13:11 +0100 Message-ID: Subject: Re: [lojban] Logical scope of LAhE To: lojban@googlegroups.com Content-Type: multipart/alternative; boundary=14dae9cc998e49d529050d8ebeed X-Original-Sender: lurifax@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lurifax@gmail.com designates 2a00:1450:400c:c03::22c as permitted sender) smtp.mail=lurifax@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: 0.8 (/) 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: Thank you Ilmen for asking, and selpa'i for answering. On Mon, Jan 26, 2015 at 1:41 PM, selpa'i wrote: > Number 1) is correct - {tu'a} is opaque. (The rest of LAhE should be as > well, though Martin seemed to be hesitant about that; see the recent-ish > tersmu thread) > [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 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 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: gmx.de] -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [209.85.217.185 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 (lurifax[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 --14dae9cc998e49d529050d8ebeed Content-Type: text/plain; charset=UTF-8 Thank you Ilmen for asking, and selpa'i for answering. On Mon, Jan 26, 2015 at 1:41 PM, selpa'i wrote: > Number 1) is correct - {tu'a} is opaque. (The rest of LAhE should be as > well, though Martin seemed to be hesitant about that; see the recent-ish > tersmu thread) > This surprised me a little, and I'm happy that there has been a consensus. What about jai? Example: {da jai se djica mi} Which of the following does this mean: 1) mi djica lo su'u da zo'u da co'e 2) da zo'u mi djica lo su'u da co'e (I would expect 2.) Yes, or you could say that it's the {be} that's opaque, since {broda be > su'o da} is itself a selbri. The same happens with tenses inside > {be}-clauses. Of course when the {da} is quantified inside a sub-bridi, > then its scope won't come out either, which is what happens with {poi'i}, > or {noi} in {zo'e noi}. > Good! What about the scope of pe? mi'e .dan. -- 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. --14dae9cc998e49d529050d8ebeed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you Ilmen for asking, and selpa'i for answering.=

On Mon, Jan 2= 6, 2015 at 1:41 PM, selpa'i <seladwa@gmx.de> wrote:
Number 1) is correct - {tu= 9;a} is opaque. (The rest of LAhE should be as well, though Martin seemed t= o be hesitant about that; see the recent-ish tersmu thread)

This surprised me a little, and I'm happy that t= here has been a consensus. What about jai?

Example: {da jai se djica= mi}

Which of the following does this mean:
1) mi djica lo su'= ;u da zo'u da co'e
2) da zo'u mi djica lo su'u da co'= ;e
=C2=A0
(I would expect 2.)

Yes, or you could say that it's the {be} that's opaque, since {brod= a be su'o da} is itself a selbri. The same happens with tenses inside {= be}-clauses. Of course when the {da} is quantified inside a sub-bridi, then= its scope won't come out either, which is what happens with {poi'i= }, or {noi} in {zo'e noi}.

Good! What about th= e scope of pe?

mi'e .dan.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@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 http= s://groups.google.com/d/optout.
--14dae9cc998e49d529050d8ebeed--