From <@PSUVM.PSU.EDU:LOJBAN@CUVMB.BITNET> Sat Sep  2 05:23:10 1995
Received: from PSUVM.PSU.EDU (psuvm.psu.edu [128.118.56.2]) by locke.ccil.org (8.6.9/8.6.10) with SMTP id FAA07600 for <cowan@LOCKE.CCIL.ORG>; Sat, 2 Sep 1995 05:23:07 -0400
Message-Id: <199509020923.FAA07600@locke.ccil.org>
Received: from PSUVM.PSU.EDU by PSUVM.PSU.EDU (IBM VM SMTP V2R2)
   with BSMTP id 0697; Sat, 02 Sep 95 05:11:12 EDT
Received: from PSUVM.PSU.EDU (NJE origin LISTSERV@PSUVM) by PSUVM.PSU.EDU (LMail V1.2a/1.8a) with BSMTP id 8728; Sat, 2 Sep 1995 05:11:00 -0400
Date:         Sat, 2 Sep 1995 12:04:40 +0300
Reply-To: veion@XIRON.PC.HELSINKI.FI
Sender: Lojban list <LOJBAN%CUVMB.BITNET@PSUVM.PSU.EDU>
From: Veijo Vilva <veion@XIRON.PC.HELSINKI.FI>
Subject:      Re: Names
To:         lojban@cuvmb.cc.columbia.edu
Status: OR

mi pu cusku di'e

>  How about
>
>         mi veion zeidu

   Still another possibility is

          mi veion zeime

   Using the whole series <zeime'e> / <zeidu> / <zeime> gives the
   possibility of semantically differentiating between naming,
   equating, and just the plain name-to-selbri conversion --
   and there are many more shades available. The essential
   requirement is adherence to the basic pattern

          name ZEIc_cmavo

   <zeida> <zeika> <zeiki> <zeila> <zeila'e> <zeipo'u> etc

   <zeivy> for <v>eion, no additional connotations

          mi vilvan zeika      I am a Vilva! (emphasizing having
                               some real or imagined properties
                               common to all members of a family
                               or clan, perhaps with <.o'a> )

          mi vilvan zei.o'a    I am a Vilva and proud of it (no
                               reference to properties)

  co'o mi'e veion