Received: from ELI.CS.YALE.EDU by NEBULA.SYSTEMSZ.CS.YALE.EDU via SMTP; Wed, 25 Aug 1993 15:35:03 -0400 Received: from YALEVM.YCC.YALE.EDU by eli.CS.YALE.EDU via SMTP; Wed, 25 Aug 1993 15:34:57 -0400 Message-Id: <199308251934.AA26746@eli.CS.YALE.EDU> Received: from CUVMB.CC.COLUMBIA.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2) with BSMTP id 8375; Wed, 25 Aug 93 15:33:26 EDT Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 5159; Wed, 25 Aug 93 15:35:54 EDT Date: Wed, 25 Aug 1993 11:39:28 -0400 Reply-To: John Cowan Sender: Lojban list From: John Cowan Subject: Re: TECH: QUERY on ZI & ZEhA X-To: Lojban List To: Erik Rauch In-Reply-To: <9308240215.AA13756@relay1.UU.NET> from "Logical Language Group" at Aug 23, 93 10:11:08 pm Status: O X-Status: X-From-Space-Date: Wed Aug 25 07:39:28 1993 X-From-Space-Address: @YaleVM.YCC.YALE.EDU:LOJBAN@CUVMB.BITNET la lojbab. cusku di'e > Now if you use certain other interval modifiers, you may create subevents > within the larger interval. #roi obviously does so, and objectively. > The TAhE (I think that's the selma'o) family including "regularly", habitually" > etc. also creates subevents within the larger interval. You're right that subevents are created, but the grammar doesn't allow as much latitude as you think. > You can then assign > relative intervals to these subevents, ad nauseum: Not really. The rule is that you can have runs of TAhE/n-ROI and ZAhO cmavo, but you can't have multiple ZEhAs -- one of those is enough. Furthermore, and quite obscurely, you can't have TAhE TAhE either without an intervening ZAhO, although you can have ZAhO ZAhO without an intervening TAhE. > mi ze'eso'iroize'udi'i klama That actually parses, but as "mi ze'eso'iroi [ku] ze'udi'i klama", in other words as two separate tenses. Whether it means what you say it means, I dunno. -- John Cowan cowan@snark.thyrsus.com ...!uunet!lock60!snark!cowan e'osai ko sarji la lojban.