TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Web Server & Documents From:Dan Roberts <Dan_Roberts -at- IBI -dot- COM> Date:Thu, 3 Apr 1997 11:16:21 EDT
IMHO, I'd probably argue the other way, for a web-based application.
If the application is designed to be used in/with a browser, the only
piece of software you can be sure the user has on the desktop is a
browser. Therefore browser-enabled text (HTML) should be the provided.
Doc in other formats should be considered as options.
Providing doc as HTML and providing help in HTML (I believe the
original posted mentioned providing help) would be a unique challenge,
especially with the ability to interlink the help (for specific tasks)
and the doc (for general understanding).
______________________________ Reply Separator _________________________________
Subject: Re: Web Server & Documents
Author: Mike Collier - SSG <MikeCol -at- sbservices -dot- com> at tcpgate
Date: 4/3/97 11:05 AM
I wouldn't worry about converting documents to HTML. On your intranet
pages, list the available documents and link them to files containing
the documents. The files should be in whatever the users have on their
machines to read text documents (e.g. if they mostly use Word, link to a
Then the users will simply click on the link and download the document.
And they can print their own hard copy on the local printer.