Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET> Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0rGCdX-00007DC; Fri, 9 Dec 94 23:13 EET Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 0525; Fri, 09 Dec 94 23:14:09 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 0522; Fri, 9 Dec 1994 23:14:06 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 1962; Fri, 9 Dec 1994 22:10:36 +0100 Date: Fri, 9 Dec 1994 16:07:48 EST Reply-To: jorge@PHYAST.PITT.EDU Sender: Lojban list From: Jorge Llambias Subject: Re: habitual X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 995 Lines: 23 la bob cusku di'e > Its experience previous to what? Does ta'e make reference to what > went on before the interval in question? > > Yes, I think it must. Otherwise the word cannnot have a meaning > different from {na'o}, as you originally pointed out. I'm glad we agree on something! This must be a first. :) > Essentially, what I am saying is that {na'o} suggests looking at the > experiences of *different* entities of the same category, occuring but > (in theory at least, potentially,) at the same in time, while {ta'e} > suggests looking at other experiences in the same category of the > *same* entities, which of neccessity occur at different times. What I understood was that the TAhEs referred exclusively to the way the event fitted inside the interval in question. You are saying that they compare the event with other more or less similar ones, that happened before or simultaneously. I think something like that doesn't really belong with the interval modifiers. Jorge