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:"Randy C. Smart" <rsmart -at- THEGRID -dot- NET> Date:Wed, 16 Dec 1998 23:41:29 -0800
I was waiting for someone to ask a question like, "How do people use these
books and how do we provide those users their 'book-benefits' on-line?"
Gutierrez, Diane said
>I want a book to dogear, crack the spine, to scribble in, carry, occupy my
downtime and waiting time, use before or after hassling with the object, and
just to depend on, knowing it's not going to be as slippery as a scrolling
monitor screen. >
As a user, I just need a book. I have to make notes all over the pages and
cover. I have to underline and highlight it when I read it. I see
relationships in the topography of a book that I don't relate to when using
on-line instructions. I remember that spot in the manual near the back that
had the picture of a dog bone that told me how the thermal gonkulator
worked. I can find it again and again. I remember the dog-eared part or the
coffee stained page.
So why can't I mess up and mark up the on-line documentation so it leaves
the "landmarks" I so desperately need?
I'm getting around on-line documentation easier all the time and see big
advantages but, as it's configured now, it's not as good as a book (for some
programs).