Re: On-Line Vs. Print, Single-Sourcing, and how to ignore the obvious

Subject: Re: On-Line Vs. Print, Single-Sourcing, and how to ignore the obvious
From: dmbrown -at- brown-inc -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Fri, 02 Aug 2002 08:07:51 -0700

Rebecca Downey wrote:
> I would like to know *what* are the differences between On-Line and print
> documentation in your humble opinion.'s online and the other's printed?

Seriously, the concensus is that people generally find on-screen text tougher on the eyes, and that they tend to stop reading long tracts of text on the screen sooner than they'd stop reading the same long tracts of text on paper. The effect of that concensus has been that most of us assume it's good to keep on-screen text short and to the point; if we have to get verbose, we tend do it on paper...or in PDF, that happy marriage of convenient access, hypertext benefits, full-text search, control over print quality, and low production costs.

An exact place where "short" and "long" are delineated is impossible to determine universally. That's why you see all the nonsense about The Magic Number 7 and similar Stone-Carved Truths of Documentation.

> So far you've only mentioned one set:
> > Personally, I prefer to get the "Here is exactly
> > how to do this" kind of information from on-line
> > help. I look to a printed manual for theoretical and
> > conceptual background.
> Are there others in your opinion?

At least one...on this point, anyway. :)

> Should information overlap between the two (print and on-line) when written
> for the same product?

Well, golly. This has been answered to death, too.

Your users may expect the help to contain lots of conceptual topics, a little bit of background information for a few of the more difficult UI elements, or nothing but field descriptions and short procedures. You may need to describe certain procedures (like installation instructions) in print; but since everything else is online, yo uinclude the installation instructions there, too. Your software may be intended for use on multiple platforms where plain text is the only common denominator, so you keep the docs short and include both a text file and a nicely laid out paper copy.

There's almost certainly *some* overlap in content. The question is "How much?"

The answer, as usual, is "It depends." Figuring out what's right for each situation is part of what separates tech writers from desktop publishers.


P.S. Hi, Andrew!


N O W A V A I L A B L E !

HTML Indexer 4 is still the easiest way to create and maintain indexes
for web sites, intranets, HTML Help, JavaHelp, and other HTML documents.

Now with fully integrated cross-references, target frames and windows,
multiple-file output, "one-step accept" of default entries, and more!


Save up to 50% with RoboHelp Deluxe. Get 2 great products for 1 low price!
You'll get RoboHelp Office PLUS RoboDemo, the software demonstration tool
that everyone's been talking about. Check it out and save!

TECHWR-L is supported by ads and sponsorships...and donations.
You can help maintain the TECHWR-L community with donations

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

RE: On-Line Vs. Print, Single-Sourcing, and how to ignore the obvious: From: Rebecca Downey

Previous by Author: Glossary Predicament!
Next by Author: Re: Glossary in Word 2000?
Previous by Thread: RE: On-Line Vs. Print, Single-Sourcing, and how to ignore the obvious
Next by Thread: Re: On-Line Vs. Print, Single-Sourcing, and how to ignore the obvious

What this post helpful? Share it with friends and colleagues:

Sponsored Ads