Sender: lojban@googlegroups.com
Received-SPF: pass (google.com: domain of scope845hlang343jbo@icebubble.org designates 2607:f2f8:a1d8::b19:0:f0b as permitted sender) client-ip=2607:f2f8:a1d8::b19:0:f0b;
From: scope845hlang343jbo@icebubble.org
To: lojban@googlegroups.com
Subject: [lojban] Re: Gismu in need of place structure extensions (WAS: Re:
 Digest for lojban@googlegroups.com - 2 updates in 1 topic)
References: <00000000000001204505a8d7a580@google.com>
	<CADbAA4UME=AQL9szkinjr44aCasfSd80ipdY3PQc278suSiOWw@mail.gmail.com>
Date: Thu, 09 Jul 2020 01:01:26 +0000
In-Reply-To: <CADbAA4UME=AQL9szkinjr44aCasfSd80ipdY3PQc278suSiOWw@mail.gmail.com>
	(Karen Stein's message of "Sun, 28 Jun 2020 11:46:57 -0400")
Message-ID: <861rllec2h.fsf_-_@cmarib.ramside>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
X-Spam_score: -2.8
X-Spam_score_int: -27
X-Spam_bar: --

Karen Stein <comcaresvcs@gmail.com> writes:

> Adding to the end of a gismu is much less of a change than changing it in
> the middle. When we were originally working on place structures for the
> gismu long ago we knew there would be some that needed to be expanded (and
> shortened).

I was going to point this out... that adding places at the end of a
gismu's existing tersu'iste causes less semantic impact/damage/confusion
than re-ordering or changing the meaning of places with existing
definitions.  That's because seeing an x3 for a gismu which only has 2
defined places automatically implies that a new, different, definition
is being used.

But there is another way to signal that a gismu has new meaning: change
the final vowel of the gismu.  So, instead of re-defining the places of
{kelci}, create a new gismu, {kelco}, and declare {kelci} deprecated.
That way, existing uses of {kelci} would retain their meaning.  Anyone
seeing {kelco} would immediately know that either (1) the writer made a
typo, or (2) some new variant of {kelci} is being used, and would
immediately recognize it as a derivative of {kelci}.  Because only the
final vowel is changed, minimal damage would be done to existing {kelci}
lujvo.  (The places of a lujvo don't necessarily match those of the
tertau.)  Of course, any new lujvo would have to stop using using the
CVV-form rafsi {kei}, because the final vowel would no longer be {i}.
But that seems manageable.

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/lojban/861rllec2h.fsf_-_%40cmarib.ramside.