Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!BU-IT.BU.EDU!tower From: tower@BU-IT.BU.EDU (Leonard H. Tower Jr.) Newsgroups: comp.society.futures Subject: Re: Hypertext Usenet Message-ID: <8711111955.AA25718@bu-it.BU.EDU> Date: Wed, 11-Nov-87 14:55:58 EST Article-I.D.: bu-it.8711111955.AA25718 Posted: Wed Nov 11 14:55:58 1987 Date-Received: Sat, 14-Nov-87 03:08:46 EST References: <15316@bu-cs.BU.EDU> <15322@bu-cs.BU.EDU> <15553@bu-cs.BU.EDU> <15380@bu-cs.BU.EDU> Sender: mis@ucbvax.BERKELEY.EDU Reply-To: tower@bu-cs.bu.edu Organization: Distributed Systems Group, Boston University, 111 Cummington Street, Boston, MA 02215, USA +1 (617) 353-2780 Lines: 48 Might I suggest a better way of implementing this? No, not GNU's texinfo ;-} (though anyone serious about Hypertext should have a glance - it is documented with working source code in the GNU Emacs distribution {ask gnu@prep.ai.mit.edu if you don't know how to get it}). [Note: texinfo is a successor to ITS' info: one of the earlier documentation databases with Hypertext capabilities]. Inserting strange strings in the text (aka body) of a netnews article is a bad idea. Just annoys people with the existing news readers. Shouldn't rile the users unnecessarily. Such Hypertalk pointers should be added to news articles as header lines. Following RFC822: X-Hyper-Pt: And maybe have as many in the header as there are references. Could define several X-Hyper-Pt-*: fields, but that seems overkill, particularly since we want it easy for non-Hyper-users to cause non-display of X-Hyper-Pt: header lines. Obviously, I am just suggesting how this information will be stored in the news spool and in the transfer of articles between news spools. It will be the duty of the Hyper-posters/readers to transfer both ways between what's displayed on the screen and X-Hyper-Pt:'s. {And if I hear anyone in this forum complain about the extra cycles ... ! ;-} Might still want to adopt a screen syntax that is unlike any other to save confusion, but this is really a Hyper-news-reader-poster question, and might be best left to the different implementors. This might also be an application for which we declare dead glass 24x80 tty screens. If you people are really serious, write up and submit an RFC, and make sure it receives exposure on USENET. You might convince me to -request a working group mailing list here at BU, and kibitz. enjoy -len PS: The discussion on >80 column lines happening over in news.all mentions SGML as a new format for text/body of news articles. Both the discussion and SGML might be worth a glance. The problems share some attributes. My preference is to leave the text/body clear of embeded commands, and place the commands in the header.