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: PDF v paper From:Mark Craig <mcraig -at- WINCAPSOFTWARE -dot- COM> Date:Wed, 16 Dec 1998 14:22:42 +0100
Why is there a need for paper doc. to be shipped with a software product?
Depends on which software product you have in mind. For example, you can
download Perl for free, complete with online documentation. However, so
many people want paper documentation that Tim O'Reilly gets rich selling
Perhaps we could make a list of questions that would help us respond with
substantive arguments, either for or against, when Marketing says, "Books
are heavy... printing takes time... you can't 'leverage' your 'ROI' with a
book... they don't look hi-tech... besides they don't fit in the boxes we
just bought... users never read the doc, anyway... let's just quit
supplying paper copies of our doc." Here are some questions we might start
1. Do my users need a long, linear explanation/tutorial to get started?
2. Would most of my users print out the .pdf and use the paper copy instead
of the online version?
3. Does the whole thing cost as much as a nice new car or a small house
already? Would good looking paper documentation keep customers from feeling
like, "I paid THAT much and all I got was a lousy CD-ROM !?!"
4. Do any customers legally require paper documentation?
5. Is our online documentation easier to use than our paper documentation?