Received-SPF: none (google.com: me@v4hn.de does not designate permitted sender hosts) client-ip=85.13.134.113;
Date: Thu, 12 Feb 2015 16:00:21 +0100
From: v4hn <me@v4hn.de>
To: lojban@googlegroups.com
Subject: Re: [lojban] the myth of monoparsing
Message-ID: <20150212150021.GB4686@kuebelreiter.informatik.Uni-Osnabrueck.DE>
References: <CAO7bV+hZTwiquY0GcTA0xVjg2t+QnRt_DcY+XafDJYfa10L7ow@mail.gmail.com>
 <20150204124517.GA1243@kuebelreiter.informatik.Uni-Osnabrueck.DE>
 <CAO7bV+jCrZy4cO62r=jJXbdM67W9RZw=k5HBvML2ZgferZiJcQ@mail.gmail.com>
 <e157ff58-8ad1-4ca0-afc9-18cf7d2f352e@googlegroups.com>
 <CAO7bV+gV_p8w-de=N1DcfSt8CzkmSZ=bHp6H1AV3Fqm8wYTh0A@mail.gmail.com>
 <c04eb516-981e-4338-9728-a7e852523b4a@googlegroups.com>
 <CAO7bV+geB+=fq33PeF0duOhwFs-D93gYnyxTZo_SFK9rif-m=g@mail.gmail.com>
 <20150212123856.GA831@kuebelreiter.informatik.Uni-Osnabrueck.DE>
 <CAO7bV+j5dQogpWO9PZ-XkpNmAhWjX+gWhL0Juk0cQWJHZvQvcA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="WYTEVAkct0FjGQmd"
Content-Disposition: inline
In-Reply-To: <CAO7bV+j5dQogpWO9PZ-XkpNmAhWjX+gWhL0Juk0cQWJHZvQvcA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
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: -1.9
X-Spam_score_int: -18
X-Spam_bar: -

--WYTEVAkct0FjGQmd
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline

First off, learn to quote properly.
This whole thread (as well as a number of other threads
you were involved in) is a mess to read.

On Thu, Feb 12, 2015 at 04:22:52PM +0300, Gleki Arxokuna wrote:
> 2015-02-12 15:38 GMT+03:00 v4hn <me@v4hn.de>:
> > So, in essence, you do not question monoparsing in lojban,
> > but instead propose a new theory on how to parse natural languages.
> > Why didn't you say so right away?
>
> May be because I did say it in the first sentence of the first post of this
> thread?

> Since the original post on monoparsing as something unique or defining
> feature of Lojban provided no examples on how this monoparsing differs from
> English here is once again my full understanding using one example that is
> monoparsed both in English and Lojban:

You use your version of "monoparsing" here without explaining anything.
So, no, you did not. Whatever.

> My complaint is (ke'usai) [about]
> <quote>monoparsing as something unique or defining feature of Lojban</quote>

Ok, it seems to be of no relevance to you at all.
That's your opinion, so, for me and a number of others on this list,
it's just another "Someone is wrong on the internet". http://xkcd.com/386/
I consider implemented and usable monoparsing to be
one of the most important features of lojban.

> This is like comparing sweet with red. If both parsers could be aligned we
> would see monoparsing (or polyparsing) in both languages.
> [...]
> It seems to me that monoparsing is not a defining feature of Lojban and in
> fact it's quite natural for most languages to be monoparsed in most cases

That's untying knots with a sword.
"Every sentence (regardless the language) monoparses
because all of its ambiguity is hidden in its structure."
helps no one, but sure, you can go there.

For me, the crutial difference between your {poi vofli} sentence and
the English "flying" sentence is that you need a zero-morpheme to "gleki-monoparse"
the latter one, where the first one moves the structure ambiguity
to a semantic level. Your argumentation here pe'i seems analogous to saying that
"Fred saw a plane while he flew over Zurich or he saw a plane that flew over Zurich"
is the same as "Fred saw a plane flying over Zurich".
This is not the case w.r.t. parsing. W.r.t. utterance analysis they are also quite
different, as Grice tells us that if somebody spends so many words on making
the uncertainty in this sentence explicit (instead of identifying one interpretation),
either the uncertainty is quite important or the speaker is a linguist...

> No example has been shown of how can monoparsing be never reached in
> natlangs if compared to how Lojban parses them.

I can't even parse that sentence properly, so I'm not sure what kind of
"example" you want as proof that something cannot be done.

> No wonder that such myths are spread without any corroboration from real
> English and Lojban grammars and examples.

You can call everything a myth,
but when it punches you in your stomach,
it will still hurt.

> I'm replying to the idea of monoparsing:
> "monoparsing is the essential Lojban virtue."
> [ http://pckipo.blogspot.ru/2014/06/lojban-is-monoparsing.html ]
>
> As I showed it is not an essential Lojban virtue.

You didn't. It's your opinion.

> It's an essential feature (not even virtue) of current Lojban parsers,
> although this may change in future [...]

Everything you proposed in this thread to make lojban "polyparse"
is about semantic analysis, not about parsing.

Last message from me in this thread,


v4hn

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

--WYTEVAkct0FjGQmd
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJU3MAFAAoJEDyttJEo9ww/GnUP/RvA611yF6vsKpqMFGBiN2Vq
LqrSVDdaNt6IMomYSQZgrI+oTK7pXWr7hhSqhayyLdQ0T5xcre0A4noAuXwge+0Q
KXEqAKWJCK1vRq7ledk0UwN+EmnVwhuon3XaU98I/ERa6BE/8RTPMqfnJYIw3t4O
YPoqphT8WEFwo9Zy02m6tRTbfu5aPSHiofL4tMOmhwBtycDdhsvoKjRHIo88rZmc
MspBGyK0/OB4V3GH3AtRj0A3L+DA66UNOh3tR3VNK8AliwggWadPs4D4xUkcyrF8
t6Uo0z/SiKBt+ZP9D6H9q8wk42Oqvm62lIdlMDZ/RaPxmqtRjY7VL8E4Rz0jyCYx
an+o4NUzoIZMBiaNd/YldFaOtMe6nzwKu4Wufqaqzx0Jx1YG1e4GAFzgY4tvNP6L
79rJhBDOkHquNfnM3U7S81zV7pqpfI3o2T/XW6UmaE4Xd4ejMdMnVf6dal+qsvql
Ek8e0NYy1F9eiF74Ofeqn8giS3R4Mu7VWKZknovjDfbnKw2TmYb38gCt6cueCy80
T4uL1ZM67Iihfty9RkyHn8E9GmjEkHb3QFcPShKkX+Bgz0rU0l30SMPQC9ThoLLI
5viOCnQ5vizWWRXUH+/RCzqrwGokLKZgCKPXP0+AXba92rhDZ4uobuAIYKpo+Aq9
n3TjoQMgOLsP0b3BaLwe
=nqZU
-----END PGP SIGNATURE-----

--WYTEVAkct0FjGQmd--