Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id NAA06861 for ; Fri, 27 Oct 1995 13:06:07 -0400 Message-Id: <199510271706.NAA06861@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id B24678FE ; Fri, 27 Oct 1995 12:53:37 -0400 Date: Fri, 27 Oct 1995 10:29:48 -0600 Reply-To: Chris Bogart Sender: Lojban list From: Chris Bogart Subject: Re: perfective counting & katna X-To: lojban@cuvmb.bitnet To: John Cowan Status: OR X-From-Space-Date: Fri Oct 27 13:06:09 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU >> > > mi co'a citka le plise --> I start eating the apple >> > > should be the same as: >> > > mi co'a ku citka le plise >> > > and therefore >> > > mi citka le plise co'a ku >> > > and therefore >> > > mi citka le plise co'a da ku >> > But {coa citka} is a kind of tanru. {coa} alters the meaning of >> > the selbri, like {toe} but unlike, say, {na} or {pu}. I agree with >> > you both as far as {na} and {pu} are concerned, but see little >> > basis for deciding what the meaning of ZAHO as sumtcita shd be. I was off the list for a while and missed the rest of the message that contained this response, so I've only heard it out of context. But with BAI tags and tense tags there's a nice correspondence between the meaning when sticking it before the broda and using it as a sumti tcita. It seems like a nice idea to have ZAhO be consistent with {pu} and {bai}. {na} is a different story, pe'i, because it can't be a sumti tcita. >> A better comparison might be with BAI. {broda bai } is >> essentially {bai broda} but with an extra place, in this case for >> the compeller. Or to put it another way, {bai broda} could be seen as a shorthand for {broda bai zo'e}, just as {pu broda} is short for {broda pu zo'e}