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 QAA10149 for <cowan@LOCKE.CCIL.ORG>; Fri, 1 Sep 1995 16:04:18 -0400
Message-Id: <199509012004.QAA10149@locke.ccil.org>
Received: from PSUVM.PSU.EDU by PSUVM.PSU.EDU (IBM VM SMTP V2R2)
   with BSMTP id 5773; Fri, 01 Sep 95 15:00:15 EDT
Received: from PSUVM.PSU.EDU (NJE origin LISTSERV@PSUVM) by PSUVM.PSU.EDU (LMail V1.2a/1.8a) with BSMTP id 8028; Fri, 1 Sep 1995 12:19:52 -0400
Date:         Fri, 1 Sep 1995 12:19:45 EDT
Reply-To: jorge@PHYAST.PITT.EDU
Sender: Lojban list <LOJBAN%CUVMB.BITNET@PSUVM.PSU.EDU>
From: jorge@PHYAST.PITT.EDU
Subject:      Re: Names
X-To:         lojban@cuvmb.cc.columbia.edu
To: John Cowan <cowan@LOCKE.CCIL.ORG>
Status: OR
X-From-Space-Date: Fri Sep  1 16:04:22 1995
X-From-Space-Address: <@PSUVM.PSU.EDU:LOJBAN@CUVMB.BITNET>

la veion cusku di'e

>   I don't especially like using <cu> as the first component because
>   it is all too easy to write bridi which don't parse as expected.

Yes, I agree with that. If the first sumti is of the "le broda" type
it would absorb the supposed predicate, unless a second {cu} is used,
which doesn't sound very nice. I like your idea of having the name
first:

>            mi veion zeime'e

but I would prefer to use something other than {me'e}. I don't want
the predicate to mean "x1 is called 'Veijo'", but rather "x1 is Veijo".
{me'e} brings out the name aspect too much. Other possibilities
to consider:

        do veion zeiku
        do veion zeivau
        do veion zeizei

Jorge