Received: from mail-wg0-f59.google.com ([74.125.82.59]:54586) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1YGS3i-0000JH-Un for lojban-list-archive@lojban.org; Wed, 28 Jan 2015 04:49:28 -0800 Received: by mail-wg0-f59.google.com with SMTP id l2sf1790941wgh.4 for ; Wed, 28 Jan 2015 04:49:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-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=GNCH0fqdSjcnFS0WQBiG93D5Nz2/zHqlYaEJCFrkVs8=; b=m8AG7G7S3/tpUCkr+2MmJyEdto7YMDTgbQVeXSZqNi2s4HL728SGmox6cyhuC6t+4m nGJtF4beqDNKFpdzha6CM+3Owgt52qXlND9sGiKg4+b6lOWMswhoWMsKsGhw8yXteFZy MHXj1Xx/TaacB2IPcsYLWvoWLkpQaWvtGqAkHlKC2T8wLtIAmHq47A6+CTO4M87tEHwm HaPxlmddE8/vQHfEGV0ZjlSXiBjEL1setHhZNisQjw/5tVQ7s/a3Ff4JA4MhzrE9/Xra wSf1rDNUfxceexN8PQj4vvzw3+zl7ON5o6KEPpmycgTn3lTxbI5aVuOsx7WWYJM7HHl6 tI7w== X-Received: by 10.180.208.67 with SMTP id mc3mr29257wic.20.1422449359927; Wed, 28 Jan 2015 04:49:19 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.38.69 with SMTP id e5ls313033wik.27.gmail; Wed, 28 Jan 2015 04:49:19 -0800 (PST) X-Received: by 10.194.241.163 with SMTP id wj3mr456191wjc.5.1422449359439; Wed, 28 Jan 2015 04:49:19 -0800 (PST) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com. [2a00:1450:400c:c03::22e]) by gmr-mx.google.com with ESMTPS id ev8si1106039wib.3.2015.01.28.04.49.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 28 Jan 2015 04:49:19 -0800 (PST) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c03::22e as permitted sender) client-ip=2a00:1450:400c:c03::22e; Received: by mail-we0-x22e.google.com with SMTP id w55so15182424wes.5 for ; Wed, 28 Jan 2015 04:49:19 -0800 (PST) X-Received: by 10.180.20.47 with SMTP id k15mr6659350wie.83.1422449359322; Wed, 28 Jan 2015 04:49:19 -0800 (PST) Received: from [192.168.0.102] (95-210-212-178.ip.skylogicnet.com. [95.210.212.178]) by mx.google.com with ESMTPSA id dc1sm2664288wib.18.2015.01.28.04.49.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jan 2015 04:49:17 -0800 (PST) Message-ID: <54C8DABC.9030307@gmail.com> Date: Wed, 28 Jan 2015 13:49:00 +0100 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Re: Questions about Lojban References: <63c70fb2-f85a-49bf-8bac-848e04682b3a@googlegroups.com> <1434464239.890000.1422398168059.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------070206070203000503030904" X-Original-Sender: ilmen.pokebip@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c03::22e as permitted sender) smtp.mail=ilmen.pokebip@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: lojban@googlegroups.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: On 28/01/2015 07:34, Gleki Arxokuna wrote: > > 2015-01-28 1:36 GMT+03:00 'John E Clifford' via lojban > >: > > Every utterance of Lojban (in particular, though the goal goes > back to Loglan) can be shown grammatical in only one way, it has a > unique parse. (And presumably a correct one, that is one that > corresponds perfectly to that underlying proposition from which > the sentence is derived by the selection of rules peculiar to this > language. Whatever the fate of the monoparsing claim is at the > moment, this second point – which is the interesting one for > refuting the Hypothesis – is not demonstrated.) > > > Please, note that as I showed earlier what is definitely "different > parses of the same sentence" in English still can be achieved in > Lojban. I mean "I saw a plane flying over Zurich" example. > The precisely ambiguous version {mi pu viska lo vinji ca lo nu lo se > xivei pa a re no'a cu vofli ga'u la tsurix} is a perfect Lojban. > It both means "I saw a plane while I was flying over Zurich" and "I > saw a plane while it was flying over Zurich". > > So your claim about "monoparsing" has to be clarified. > See reply above showing more of this example. [...] 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) [74.125.82.59 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 (ilmen.pokebip[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 This is a multi-part message in MIME format. --------------070206070203000503030904 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable On 28/01/2015 07:34, Gleki Arxokuna wrote: > > 2015-01-28 1:36 GMT+03:00 'John E Clifford' via lojban=20 > >: > > Every utterance of Lojban (in particular, though the goal goes > back to Loglan) can be shown grammatical in only one way, it has a > unique parse. (And presumably a correct one, that is one that > corresponds perfectly to that underlying proposition from which > the sentence is derived by the selection of rules peculiar to this > language. Whatever the fate of the monoparsing claim is at the > moment, this second point =E2=80=93 which is the interesting one for > refuting the Hypothesis =E2=80=93 is not demonstrated.) > > > Please, note that as I showed earlier what is definitely "different=20 > parses of the same sentence" in English still can be achieved in=20 > Lojban. I mean "I saw a plane flying over Zurich" example. > The precisely ambiguous version {mi pu viska lo vinji ca lo nu lo se=20 > xivei pa a re no'a cu vofli ga'u la tsurix} is a perfect Lojban. > It both means "I saw a plane while I was flying over Zurich" and "I=20 > saw a plane while it was flying over Zurich". > > So your claim about "monoparsing" has to be clarified. > See reply above showing more of this example. =C2=ABI saw a plane flying over Zurich=C2=BB can be rendered as {mi puku vi= ska lo=20 vinji ca lo nu (zo'e) vofli pa'o lo gapru la .tsurix.}; this Lojban=20 sentence is structurally unambiguous, but leaves explicitly the identity=20 of the flying thing to the context (zo'e vofli). As for the English=20 sentence, in addition to not being clear about what is flying, it's=20 parse tree is ambiguous, "flying over Zurich" could either attach to "a=20 plane" (as an adjective would do), or act as an adverbial (targetting=20 the proposition "I saw a plane" as a whole, if I'm not mistaken). As for the Lojban sentence proposed by Gleki, {mi puku viska lo vinji ca=20 lo nu lo se xi vei pa .a re no'a cu vofli ga'u la .tsurix.}, it can be=20 simplified to {mi puku viska lo vinji ca lo nu ri .a mi vofli ga'u la=20 .tsurix.}, which is similar to what I suggested but having =C2=ABme and/or= =20 the aircraft=C2=BB as the flying thing; this is also structurally=20 unambiguous, and very explicitly not saying what exactly is flying (me,=20 the aircraft or both?). mi'e la .ilmen. mu'o --=20 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 e= mail 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. --------------070206070203000503030904 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 28/01/2015 07:34, Gleki Arxokuna wrote:

2015-01-28 1:36 GMT+03:00 'John E Clifford' via lojban <l= ojban@googlegroups.com>:
Every utterance of Lojban (in particular, though the goal goes back to Loglan) can be shown grammatical in only one way, it has a unique parse. (And presumably a correct one, that is one that corresponds perfectly to that underlying proposition from which the sentence is derived by the selection of rules peculiar to this language. Whatever the fate of the monoparsing claim is at the moment, this second point =E2=80=93 which is the interesting one for refut= ing the Hypothesis =E2=80=93 is not demonstrated.)

Please, note that as I showed earlier what is definitely "different parses of the same sentence" in English still can be achieved in Lojban. I mean "I saw a plane flying over Zurich" example.
The precisely ambiguous version {mi pu viska lo vinji ca lo nu lo se xivei pa a re no'a cu vofli ga'u la tsurix} is a perfect Lojban.
It both means "I saw a plane while I was flying over Zurich" and "I saw a plane while it was flying over Zurich".

So your claim about "monoparsing" has to be clarified.
See reply above showing more of this example.

=C2=ABI saw a plane flying over Zurich=C2=BB can be rendered as {mi puk= u viska lo vinji ca lo nu (zo'e) vofli pa'o lo gapru la .tsurix.}; this Lojban sentence is structurally unambiguous, but leaves explicitly the identity of the flying thing to the context (zo'e vofli). As for the English sentence, in addition to not being clear about what is flying, it's parse tree is ambiguous, "flying over Zurich" could either attach to "a plane" (as an adjective would do), or act as an adverbial (targetting the proposition "I saw a plane" as a whole, if I'm not mistaken).

As for the Lojban sentence proposed by Gleki, {mi puku viska lo vinji ca lo nu lo se xi vei pa .a re no'a cu vofli ga'u la .tsurix.}, it can be simplified to {mi puku viska lo vinji ca lo nu ri .a mi vofli ga'u la .tsurix.}, which is similar to what I suggested but having =C2=ABme and/or the aircraft=C2=BB as the flying t= hing; this is also structurally unambiguous, and very explicitly not saying what exactly is flying (me, the aircraft or both?).

mi'e la .ilmen. mu'o


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