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 XAA21488 for ; Sat, 24 Feb 1996 23:02:45 -0500 Message-Id: <199602250402.XAA21488@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 98858925 ; Sat, 24 Feb 1996 22:26:25 -0500 Date: Sat, 24 Feb 1996 13:02:59 +0000 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: {ti} (was: Re: *old response to And on fuzzy proposals) X-To: lojban@cuvmb.cc.columbia.edu To: John Cowan X-Mozilla-Status: 0001 Content-Length: 1040 X-From-Space-Date: Mon Feb 26 10:35:31 1996 X-From-Space-Address: - > >> >> "sei ti jitfa" embedded in a sentence (this sentence is a lie). > >> >where {ti} refers to {dei}, I presume. > >> Correct. "ti" was wrong, not sloppy in the sei statement. > >I think calling it "wrong" is a bit extreme. Misleading, maybe. Glico, > >yes. Malglico, maybe. > "ti" is wrong in any printed text without some overt deitic pointer > like a pretty graphic arrow (omitting of course the degenerate case > of "ti" being quoted, in which case one need not expect the deitic > reference to be identified. "dei" and "di'u" and "ri" and probably a > few other words were added to Loglan/Lojban specifically to rid the ir > meanings from "ti". {dei} & co are more precise, but I don't see why {ti} can't point to an utterance. (Of course, if you could use {dei} then why use {ti}, but that's not the issue.) Further, the relationship between deixis and writing is rather messy. If {ca} can mean "at the time when {ca} was coa written down" then {ti} could mean "this here thing proximate to me as I write {ti}". i coo i mie and