From pycyn@aol.com Sun Oct 01 16:00:33 2000
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@egroups.com
Received: (EGP: mail-6_0_3); 1 Oct 2000 23:00:33 -0000
Received: (qmail 5683 invoked from network); 1 Oct 2000 23:00:33 -0000
Received: from unknown (10.1.10.26) by m4.onelist.org with QMQP; 1 Oct 2000 23:00:33 -0000
Received: from unknown (HELO imo-d04.mx.aol.com) (205.188.157.36) by mta1 with SMTP; 1 Oct 2000 23:00:32 -0000
Received: from Pycyn@aol.com by imo-d04.mx.aol.com (mail_out_v28.24.) id a.e3.a7088b0 (3953) for <lojban@egroups.com>; Sun, 1 Oct 2000 19:00:26 -0400 (EDT)
Message-ID: <e3.a7088b0.27091c0a@aol.com>
Date: Sun, 1 Oct 2000 19:00:26 EDT
Subject: Re: [lojban] Re: {za'o} in space
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

As I said, aulun's point is a good one and, if we want to be precise -- as we 
do in textbooks and reference grammars, we would do things in the way 
suggested. But, with motion, we have the option to use space to mark time 
and so we often do. We do not disagree about the rule, justy about how 
strictly it is to be applied in some cases. (The motion may, it turns out, 
be implicit -- "He kept on building after 59th street -- i.e., on 60th and 
even 61st -- moving his hideous string of building ever uptownward.)


