Received: from uga.cc.uga.edu by nfs1.digex.net with SMTP id AA17178
  (5.67b8/IDA-1.5 for <lojbab@ACCESS.DIGEX.NET>); Fri, 27 Jan 1995 19:49:14 -0500
Message-Id: <199501280049.AA17178@nfs1.digex.net>
Received: from UGA.CC.UGA.EDU by uga.cc.uga.edu (IBM VM SMTP V2R2)
   with BSMTP id 0203; Fri, 27 Jan 95 19:51:03 EST
Received: from UGA.CC.UGA.EDU (NJE origin LISTSERV@UGA) by UGA.CC.UGA.EDU (LMail V1.2a/1.8a) with BSMTP id 1874; Fri, 27 Jan 1995 19:13:34 -0500
Date:         Fri, 27 Jan 1995 19:14:49 EST
Reply-To: jorge@PHYAST.PITT.EDU
Sender: Lojban list <LOJBAN@CUVMB.BITNET>
From: jorge@PHYAST.PITT.EDU
Subject:      Re: more on vi/fa'a/to'o
X-To:         lojban@cuvmb.cc.columbia.edu
To: Bob LeChevalier <lojbab@access.digex.net>
Status: RO
X-From-Space-Date: Fri Jan 27 20:50:43 1995
X-From-Space-Address: LOJBAN%CUVMB.BITNET@uga.cc.uga.edu

la i,n cusku di'e

> I thought the idea was that one pair (fa'a/to'o, I think)
> was about motion relative to the specified point (if any),
> and the other (ze'o/zo'i) was about motion starting from
> the specified point, but relative to the origin.

That makes sense. I think I finally understand them!

> So
>
> mo'ifa'a ko'a    towards X
> mo'ito'o ko'a    away from X
> mo'ize'o ko'a    outwards from X (i.e. away from here, starting from X)
> mo'izo'i ko'a    inwards from X (i.e. towards here, starting from X)
>
>          ^
>          | mo'ize'o
>          |
> mo'ifa'a | mo'ito'o
> -------> X ------->
>          |
>          | mo'izo'i
>          v
>
>          O
>
> So {ze'o} and {zo'i} are special cases of {to'o}.
>
> I suggest the following corresponding static interpretations.
>
> fa'a    near to (more or less redundant with {ne'a})
> to'o    distant from (more or less redundant with {na'ene'a})
> zo'i    cis, on this side of
> ze'o    trans, on the other side of

I like it! Thanks for the clarification. I'll remove zo'i and
ze'o from my hit-list  ;)

Jorge