From owner-freebsd-chat Mon Mar 2 20:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03945 for freebsd-chat-outgoing; Mon, 2 Mar 1998 20:58:55 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from const. (willow14.verinet.com [199.45.181.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03927 for ; Mon, 2 Mar 1998 20:58:30 -0800 (PST) (envelope-from allenc@verinet.com) Received: (from allenc@localhost) by const. (8.8.8/8.8.8) id VAA11558; Mon, 2 Mar 1998 21:41:07 -0700 (MST) (envelope-from allenc) Date: Mon, 2 Mar 1998 21:41:07 -0700 (MST) From: allen campbell Message-Id: <199803030441.VAA11558@const.> To: grog@lemis.com Subject: Re: ps2pdf (was: newbies mailing list) Cc: chat@FreeBSD.ORG Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > What's "Word format"? Microsoft Word format. The de-facto standard word processor format. Typically has the extension .doc. Converts readily to RTF. IMHO, HTML is the best choice for this documentation. HTML is accessible from nearly everywhere, space efficient and by definition, hypertext. About the only place where accessing HTML might be a challenge is DOS. This is offset by the fact that nearly all contemporary formats are no easier (ps, pdf, Word, rtf, etc) to get at from DOS (I don't need to be reminded that it IS possible.) Microsoft has recognized the simple elegance of HTML is it's own help system. If a plain text version is necessary for ease of printing and access where a browser isn't available, use the existing SGML tools to produce HTML and text from one base. This will also integrate nicely with the existing FreeBSD documentation structure. This wheel has already been invented. Allen Campbell allenc@verinet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message