From pycyn@aol.com Fri Jun 16 14:16:09 2000
Return-Path: <Pycyn@aol.com>
Received: (qmail 3081 invoked from network); 16 Jun 2000 21:16:08 -0000
Received: from unknown (10.1.10.142) by m4.onelist.org with QMQP; 16 Jun 2000 21:16:08 -0000
Received: from unknown (HELO imo-d06.mx.aol.com) (205.188.157.38) by mta3 with SMTP; 16 Jun 2000 21:16:08 -0000
Received: from Pycyn@aol.com by imo-d06.mx.aol.com (mail_out_v27.10.) id a.6b.5b27a59 (3948) for <lojban@egroups.com>; Fri, 16 Jun 2000 17:16:01 -0400 (EDT)
Message-ID: <6b.5b27a59.267bf311@aol.com>
Date: Fri, 16 Jun 2000 17:16:01 EDT
Subject: Re: [lojban] Mi za'o klama
To: lojban@egroups.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 41
From: pycyn@aol.com

In a message dated 00-06-16 16:31:43 EDT, pier writes:

<<>goes on to Pineville though aiming at Charlotte -- as {mi klama la 
>painvil la ralix za'o la charlyt}
No, that means "I go from Raleigh to Pineville when Charlotte has outlived 
its
usefulness." >>

RECORD:za'o 
What is gone beyond is anything that would be expected to end what in fact 
continues. In processes, this is most naturally the completion of the 
product, but destroying the machinery, for example, also will do. For states 
and activities (I don't think achievements can go on overtime since they 
don't go on at all), anything will do: presumed interruptions, length of 
time, ... *The most useful task for za'o as a sumti tag is, therefore, to 
indicate the obstacle overcome (or ignored) in the ongoing.*