Received: from wnt.dc.lsoft.com (wnt.dc.lsoft.com [205.186.43.7]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id BAA29053 for ; Sun, 25 Feb 1996 01:22:04 -0500 Message-Id: <199602250622.BAA29053@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by wnt.dc.lsoft.com (LSMTP for Windows NT v1.0a) with SMTP id 4A0BC920 ; 25 Feb 1996 0:43:32 -0500 Date: Sat, 24 Feb 1996 11:26:33 -0600 Reply-To: "Steven M. Belknap" Sender: Lojban list From: "Steven M. Belknap" Subject: html and lojban To: John Cowan X-Mozilla-Status: 0001 Content-Length: 1385 X-From-Space-Date: Mon Feb 26 10:35:48 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}". So if we use {ti} and various lujvo corresponding to html commands, we could generate web pages in lojban, no? Sounds good to me. -Steven Steven M. Belknap, M.D. Assistant Professor of Clinical Pharmacology and Medicine University of Illinois College of Medicine at Peoria email: sbelknap@uic.edu Voice: 309/671-3403 Fax: 309/671-8413