From LOJBAN%CUVMB.bitnet@YaleVM.YCC.YALE.EDU  Sat Mar  6 22:49:45 2010
Received: from YALEVM.YCC.YALE.EDU by MINERVA.CIS.YALE.EDU via SMTP; Mon, 2 Aug 1993 19:47:54 -0400
Received: from CUVMB.CC.COLUMBIA.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2)
   with BSMTP id 4039; Mon, 02 Aug 93 19:46:45 EDT
Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with
 BSMTP id 8513; Mon, 02 Aug 93 19:45:31 EDT
Date:         Mon, 2 Aug 1993 19:43:09 EDT
Reply-To: Logical Language Group <lojbab@GREBYN.COM>
Sender: Lojban list <LOJBAN%CUVMB.bitnet@YaleVM.YCC.YALE.EDU>
From: Logical Language Group <lojbab@GREBYN.COM>
Subject:      Re: TECH: SE rafsi omitted in lujvo (was Re: dikyjvo, too,
X-To:         nsn@mullian.ee.mu.OZ.AU
X-Cc:         lojban@cuvmb.cc.columbia.edu
To: Erik Rauch <erikr@MINERVA.CIS.YALE.EDU>
Status: RO
X-Status: 
X-From-Space-Date: Ukn Aug  2 19:47:56 1993
X-From-Space-Address: lojbab@GREBYN.COM
Message-ID: <r9dcCKcNZ9J.A.dUH.Jy0kLB@chain.digitalkingdom.org>

After thinking about it, I am inclined to agree with you - with one provision:
xekskapi can be a perfectly good word, but it has the places implied by the
final term, which are backwards to the English.  X is the black skin of Y
or X is the skin of black (person?) Y.  This should be allowed as an alternative
and may be preferred in some cases, since you end up with the same places
(I think) just in a non-standard order. If the result otherwise might be
hyphens (not true in this case, but presume so for the example:)
se xekskapi
might be preferable to
xekselskapi
especially if there is frequent occassion to fill in both places instead of
1, if the final term is one that already tends to be "fa"d like cumki, or
maybe iun general when the word is used more in a main selbri than in a
description.

lojbab