Received: from mail-yw0-f57.google.com ([209.85.213.57]:44316)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCIfYkcm2DRCl3-f_BBoEPM-3bw@googlegroups.com>)
	id 1SnyF1-0001DU-Pi; Sun, 08 Jul 2012 13:38:18 -0700
Received: by yhr47 with SMTP id 47sf13370740yhr.12
        for <multiple recipients>; Sun, 08 Jul 2012 13:37:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=beta;
        h=x-beenthere:received-spf:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:x-original-sender
         :x-original-authentication-results:reply-to:precedence:mailing-list
         :list-id:x-google-group-id:list-post:list-help:list-archive:sender
         :list-subscribe:list-unsubscribe:content-type;
        bh=85VJqMF6I5G5B16h3yL8Um/HUz8nU9DaKs4T4rO7Egk=;
        b=apzHVjH7f62zRoKKg2qyDSvCoYy7tK6ia2/AeeugB9JHwogxk5S12HaGjaHwhKf69g
         bhs3o6PB+oCZkp6S2jGDwgexUMr+EMOXtdHKNUnufS0MuIi+12B/zfnwI/8MvMe8PzMd
         knEqzjp7P8nkfabkES3qSvhSHe8geS7KUmInQ=
Received: by 10.52.155.207 with SMTP id vy15mr2196216vdb.13.1341779877035;
        Sun, 08 Jul 2012 13:37:57 -0700 (PDT)
X-BeenThere: lojban@googlegroups.com
Received: by 10.220.115.146 with SMTP id i18ls5938322vcq.0.gmail; Sun, 08 Jul
 2012 13:37:56 -0700 (PDT)
Received: by 10.52.89.129 with SMTP id bo1mr29731562vdb.0.1341779876618;
        Sun, 08 Jul 2012 13:37:56 -0700 (PDT)
Received: by 10.52.89.129 with SMTP id bo1mr29731561vdb.0.1341779876603;
        Sun, 08 Jul 2012 13:37:56 -0700 (PDT)
Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49])
        by gmr-mx.google.com with ESMTPS id l12si338856vdf.3.2012.07.08.13.37.56
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 08 Jul 2012 13:37:56 -0700 (PDT)
Received-SPF: pass (google.com: domain of veijo.vilva@gmail.com designates 209.85.212.49 as permitted sender) client-ip=209.85.212.49;
Received: by vbbfo1 with SMTP id fo1so9055741vbb.22
        for <lojban@googlegroups.com>; Sun, 08 Jul 2012 13:37:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.180.230 with SMTP id dr6mr14933373vdc.130.1341779876447;
 Sun, 08 Jul 2012 13:37:56 -0700 (PDT)
Received: by 10.52.159.193 with HTTP; Sun, 8 Jul 2012 13:37:56 -0700 (PDT)
In-Reply-To: <e6a58068-8d8c-4597-bdc4-2ead9d809045@googlegroups.com>
References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com>
	<bac4e707-21fc-49ae-9e5e-6c5790dadcf2@googlegroups.com>
	<62818d3a-c188-43d5-ad25-09c4cc9aca6c@googlegroups.com>
	<1341252212.22198.YahooMailNeo@web184415.mail.bf1.yahoo.com>
	<4FF20621.1090100@lojban.org>
	<1341333405.7836.YahooMailNeo@web184416.mail.bf1.yahoo.com>
	<4FF74E66.1020605@gmail.com>
	<CAHiXx=P_S5v0Qh748TcX_Z+QbscQAPNRYHaRCaYiWx3AoreO7g@mail.gmail.com>
	<28c5220c-26fb-480f-8305-51e3cf0cb5c2@googlegroups.com>
	<CAHiXx=PS-0uHzWJ-ojTE+pyW8C6HW9w7KoCuB60JteG3CgbkSA@mail.gmail.com>
	<da4f73f3-db7a-49c4-bfe5-948e26bd8b4b@googlegroups.com>
	<9d023dbf-28d1-42de-84a4-a630ae020a82@googlegroups.com>
	<CA+4zpkQr4ExohFHKa5V3wMamLo+i-Yqe1aBLV+pbiwYw7otaDA@mail.gmail.com>
	<644f40f5-7ad7-4b17-b455-9eda930769ef@googlegroups.com>
	<e6a58068-8d8c-4597-bdc4-2ead9d809045@googlegroups.com>
Date: Sun, 8 Jul 2012 23:37:56 +0300
Message-ID: <CA+4zpkQeAkX0LyyUNYk7SEb=Q7v+M7yNtFStNOHgwg8Hm1Qh0w@mail.gmail.com>
Subject: Re: [lojban] Re: Is there any demand for LoCCan3?
From: Veijo Vilva <veijo.vilva@gmail.com>
To: lojban@googlegroups.com
X-Original-Sender: veijo.vilva@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 domain of veijo.vilva@gmail.com designates 209.85.212.49 as permitted sender)
 smtp.mail=veijo.vilva@gmail.com; dkim=pass header.i=@gmail.com
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
List-ID: <lojban.googlegroups.com>
X-Google-Group-Id: 1004133512417
List-Post: <http://groups.google.com/group/lojban/post?hl=en_US>, <mailto:lojban@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:lojban+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/lojban?hl=en_US>
Sender: lojban@googlegroups.com
List-Subscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:lojban+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/lojban/subscribe?hl=en_US>, <mailto:googlegroups-manage+1004133512417+unsubscribe@googlegroups.com>
Content-Type: multipart/alternative; boundary=bcaec51a8232e7054504c45778ba
X-Spam-Score: -0.7 (/)
X-Spam_score: -0.7
X-Spam_score_int: -6
X-Spam_bar: /

--bcaec51a8232e7054504c45778ba
Content-Type: text/plain; charset=ISO-8859-1

On 8 July 2012 21:14, la .lindar. <lindarthebard@gmail.com> wrote:

> *Regardless* of the arguments, I'm staunchly against it precisely for the
> fact that people will *use* it. Regardless of whether or not *I* have to
> use it, *other* people will, which means that *I* have to learn to read it.
> Therefore, it *does* affect me, even if I *do* choose to use the original
> sumti connectives. Therefore, I will always veto this idea every time
> forever.
>
> That being said, I will gladly bring it to Robin's attention, who I
> presume will laugh and say, "Fuck no.", but very well may not.
>

I'm not proposing a change in the language, not yet, anyway. I'm using this
as a case study to find out the *purely technical* problems this kind and
magnitude of change would cause, especially at the level of my present
parser framework.

Using a parser as the basis for various linguistic tools can simplify many
tasks, e.g,, syntax sensitive re-coding. It turned out to be a trivial task
to add an official-to-mad coder process to my parser, and adding a
mad-to-official coder is just mechanical work now that the basis for
re-coding is there. After a two-way re-coding mechanism is available, the
parser can be used to ascertain that a supposedly one-to-one change doesn't
break anything. The re-coding process doesn't appreciably affect the
parsing time, even for Alice the increase is of the order of one second.

If we ever get so far that we are seriously considering moving on from the
baseline, we need tools like this to study the effect of the proposed
changes. I also think that before that stage it would be quite useful and
wise to do various kinds of hypothetical case studies, which would help to
chart the territory. It is well nigh impossible to say anything definite on
the basis of a few hand-crafted examples. A proposed change may look good
in theory but turn out to be a flop in practice, and vice versa. Pushing
sections of the existing corpus through an automatic coder and looking at
the result will tell a lot more about various aspects (intelligibility,
learnability, aesthetics &c.) and perhaps help to overcome prejudices
concerning a proposed change, both pro and con, that is.

  veion

-- 

  web site: http://galactinus.net/vilva/
  on Google+: https://plus.google.com/106533767817816079660/posts

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.


--bcaec51a8232e7054504c45778ba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On 8 July 2012 21:14, la .lindar. <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:lindarthebard@gmail.com" target=3D"_blank">lindarthebard@gm=
ail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
*Regardless* of the arguments, I&#39;m staunchly against it precisely for t=
he fact that people will *use* it. Regardless of whether or not *I* have to=
 use it, *other* people will, which means that *I* have to learn to read it=
. Therefore, it *does* affect me, even if I *do* choose to use the original=
 sumti connectives. Therefore, I will always veto this idea every time fore=
ver.<div>
<br></div><div>That being said, I will gladly bring it to Robin&#39;s atten=
tion, who I presume will laugh and say, &quot;Fuck no.&quot;, but very well=
 may not.</div></blockquote><div><br></div><div>I&#39;m not proposing a cha=
nge in the language, not yet, anyway. I&#39;m using this as a case study to=
 find out the *purely technical* problems this kind and magnitude of change=
 would cause, especially at the level of my present parser framework.</div>
<div><br></div><div>Using a parser as the basis for various linguistic tool=
s can simplify many tasks, e.g,, syntax sensitive re-coding. It turned out =
to be a trivial task to add an official-to-mad coder process to my parser, =
and adding a mad-to-official coder is just mechanical work now that the bas=
is for re-coding is there. After a two-way re-coding mechanism is available=
, the parser can be used to ascertain that a supposedly one-to-one change d=
oesn&#39;t break anything. The re-coding process doesn&#39;t appreciably af=
fect the parsing time, even for Alice the increase is of the order of one s=
econd.</div>
<div><br></div><div>If we ever get so far that we are seriously considering=
 moving on from the baseline, we need tools like this to study the effect o=
f the proposed changes. I also think that before that stage it would be qui=
te useful and wise to do various kinds of hypothetical case studies, which =
would help to chart the territory. It is well nigh impossible to say anythi=
ng definite on the basis of a few hand-crafted examples. A proposed change =
may look good in theory but turn out to be a flop in practice, and vice ver=
sa. Pushing sections of the existing corpus through an automatic coder and =
looking at the result will tell a lot more about various aspects (intelligi=
bility, learnability, aesthetics &amp;c.) and perhaps help to overcome prej=
udices concerning a proposed change, both pro and con, that is.</div>
<div><br></div><div>=A0 veion</div><div><br></div></div>-- <br><div dir=3D"=
ltr"><br>=A0 web site: <a href=3D"http://galactinus.net/vilva/" target=3D"_=
blank">http://galactinus.net/vilva/</a><div>=A0 on Google+: <a href=3D"http=
s://plus.google.com/106533767817816079660/posts" target=3D"_blank">https://=
plus.google.com/106533767817816079660/posts</a></div>
</div><br>
</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups "=
lojban" group.<br />
To post to this group, send email to lojban@googlegroups.com.<br />
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou=
ps.com.<br />

For more options, visit this group at http://groups.google.com/group/lojban=
?hl=3Den.<br />



--bcaec51a8232e7054504c45778ba--