Received: from mail-we0-f189.google.com ([74.125.82.189]:43959)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <lojban+bncCMHEmaCOBhCXmLT9BBoEaqiRbg@googlegroups.com>)
	id 1SSpN1-0001xR-He; Fri, 11 May 2012 05:55:06 -0700
Received: by werm13 with SMTP id m13sf387842wer.16
        for <multiple recipients>; Fri, 11 May 2012 05:54:48 -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=oTnIosgjJUyOfs8p17WzeD2fWVPI+ILxAK0ENQMeE64=;
        b=RFMZDWND1tx0IZeAISGhcu4o5+JU06xE4io4+I6blCRBfjXPlui+qMNRDlv+fK0yvx
         v3fO3B7utdoB0fCu/afxbUzH7YxVzRWjSJwdu9gZMDOzVMilV+KbBZOHgKPevbIvDUZ3
         XSsB4kTwNWOIswEf41oyjm1cJQvRnMDP7YO1A=
Received: by 10.205.133.208 with SMTP id hz16mr324997bkc.11.1336740887775;
        Fri, 11 May 2012 05:54:47 -0700 (PDT)
X-BeenThere: lojban@googlegroups.com
Received: by 10.204.129.85 with SMTP id n21ls5711470bks.6.gmail; Fri, 11 May
 2012 05:54:45 -0700 (PDT)
Received: by 10.204.157.134 with SMTP id b6mr1107056bkx.5.1336740885872;
        Fri, 11 May 2012 05:54:45 -0700 (PDT)
Received: by 10.204.157.134 with SMTP id b6mr1107055bkx.5.1336740885851;
        Fri, 11 May 2012 05:54:45 -0700 (PDT)
Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178])
        by gmr-mx.google.com with ESMTPS id ig3si10921575bkc.3.2012.05.11.05.54.45
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 11 May 2012 05:54:45 -0700 (PDT)
Received-SPF: pass (google.com: domain of eyeonus@gmail.com designates 209.85.217.178 as permitted sender) client-ip=209.85.217.178;
Received: by lbbgj10 with SMTP id gj10so2432148lbb.37
        for <lojban@googlegroups.com>; Fri, 11 May 2012 05:54:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.39.135 with SMTP id p7mr3600340lbk.78.1336740885336; Fri,
 11 May 2012 05:54:45 -0700 (PDT)
Received: by 10.152.22.68 with HTTP; Fri, 11 May 2012 05:54:45 -0700 (PDT)
In-Reply-To: <28872598.911.1336731707204.JavaMail.geo-discussion-forums@vbws2>
References: <13765994.1942.1336566814390.JavaMail.geo-discussion-forums@ynss9>
	<20120509170127.GR27762@stodi.digitalkingdom.org>
	<27554010.67.1336587846504.JavaMail.geo-discussion-forums@yngr14>
	<20120509192018.GS27762@stodi.digitalkingdom.org>
	<524651.567.1336675068460.JavaMail.geo-discussion-forums@vbak7>
	<28872598.911.1336731707204.JavaMail.geo-discussion-forums@vbws2>
Date: Fri, 11 May 2012 06:54:45 -0600
Message-ID: <CAMKwHj3t7rHwWWUDoWbYzdXtuviVn=iky9S1pJd93WbsEkEtHw@mail.gmail.com>
Subject: Re: [lojban] bugs in jbovlaste
From: Jonathan Jones <eyeonus@gmail.com>
To: lojban@googlegroups.com
X-Original-Sender: eyeonus@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 domain of eyeonus@gmail.com designates 209.85.217.178 as permitted sender)
 smtp.mail=eyeonus@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=485b390f7a76a0912904bfc23ddd
X-Spam-Score: 0.0 (/)
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /

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

On Fri, May 11, 2012 at 4:21 AM, gleki <gleki.is.my.name@gmail.com> wrote:

> On Thursday, May 10, 2012 10:37:48 PM UTC+4, ianek wrote:
>>
>>
>> Fine, I've just added aionys' complaints about familial gismu, and also
>> xorxes' proposed definition of xruti. If anynone knows about other proposed
>> changes, please check whether they're there and if not, add them.
>>
>
> What's that with {xruti}? It's agentive, don't touch it!
> Let's create another experimental gismu with the definition {x1 (agent)
> returns to origin/earlier state x3 from x4} or possibly with another order
> of sumti.
> But {xruti} must retain the meaning.
> *OTHERWISE WE'LL LOSE COMPATIBILITY WITH OLDER TEXTS.*
>

First, this is not the place for this. If you'll notice the topic of this
thread is "bugs in jbovlaste".

Second, you are over-reacting. Also, it is my personal opinion that,
especially in the case of xruti, breaking older text is worth not having a
broken place structure.

Third, that page is about issues, as in things we have found that need to
be reviewed.

Fourth, you are taking the creation a new gismu entirely too lightly. Of
all the possible changes to our language, a new gismu is the absolute
/least/ likely to happen. In fact, the /only/ way a new gismu would be
considered that I know of is in the case that we determine that some
portion of the semantic space can not be represented by any combination of
currently existant valsi, i.e. gismu, tanru, or lujvo, with za'uno cmavo
intermigled, or alternately, is a concept of such widespread use as to
merit it. For example, had Lojban been invented during the colonization of
the Americas, it would obviously not have included "skami", as the very
concept basically didn't exist at the time, but it would have since been
added, considering both that it covers previously semantic space and is an
extremely important part of modern existence.

In short, we do /not/ make new gismu unless it is /absolutely/ necessary.

-- 
mu'o mi'e .aionys.

.i.e'ucai ko cmima lo pilno be denpa bu .i doi.luk. mi patfu do zo'o
(Come to the Dot Side! Luke, I am your father. :D )

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


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

<div class=3D"gmail_quote">On Fri, May 11, 2012 at 4:21 AM, gleki <span dir=
=3D"ltr">&lt;<a href=3D"mailto:gleki.is.my.name@gmail.com" target=3D"_blank=
">gleki.is.my.name@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<div class=3D"im">On Thursday, May 10, 2012 10:37:48 PM UTC+4, ianek wrote:=
<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><br><div>Fine, I&#39;ve just added =
aionys&#39; complaints about familial gismu, and also xorxes&#39; proposed =
definition of xruti. If anynone knows about other proposed changes, please =
check whether they&#39;re there and if not, add them.</div>
</blockquote><div><br></div></div><div>What&#39;s that with {xruti}? It&#39=
;s agentive, don&#39;t touch it!</div><div>Let&#39;s create another experim=
ental gismu with the definition {x1 (agent) returns to origin/earlier state=
 x3 from x4} or possibly with another order of sumti.</div>
<div>But {xruti} must retain the meaning.<br><b>OTHERWISE WE&#39;LL LOSE CO=
MPATIBILITY WITH OLDER TEXTS.</b></div></blockquote></div><br>First, this i=
s not the place for this. If you&#39;ll notice the topic of this thread is =
&quot;bugs in jbovlaste&quot;.<br>
<br>Second, you are over-reacting. Also, it is my personal opinion that, es=
pecially in the case of xruti,=20
breaking older text is worth not having a broken place structure.<br><br>Th=
ird, that page is about issues, as in things we have found that need to be =
reviewed.<br><br>Fourth, you are taking the creation a new gismu entirely t=
oo lightly. Of all the possible changes to our language, a new gismu is the=
 absolute /least/ likely to happen. In fact, the /only/ way a new gismu wou=
ld be considered that I know of is in the case that we determine that some =
portion of the semantic space can not be represented by any combination of =
currently existant valsi, i.e. gismu, tanru, or lujvo, with za&#39;uno cmav=
o intermigled, or alternately, is a concept of such widespread use as to me=
rit it. For example, had Lojban been invented during the colonization of th=
e Americas, it would obviously not have included &quot;skami&quot;, as the =
very concept basically didn&#39;t exist at the time, but it would have sinc=
e been added, considering both that it covers previously semantic space and=
 is an extremely important part of modern existence.<br>
<br>In short, we do /not/ make new gismu unless it is /absolutely/ necessar=
y.<br><br>-- <br>mu&#39;o mi&#39;e .aionys.<br><br>.i.e&#39;ucai ko cmima l=
o pilno be denpa bu .i doi.luk. mi patfu do zo&#39;o<br>(Come to the Dot Si=
de! Luke, I am your father. :D )<br>
<br>

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



--485b390f7a76a0912904bfc23ddd--