Re: On-line vs. print (WAS: Of myth and reality)?

[eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com]

Well, this subject certainly didn't garner much interest did it? After so many
claiming that on-line and print are so different, is there nobody willing to
discuss the requirements of on-line documentation?

I didn't want this thread to touch single sourcing, I wanted to honestly discuss
the differences and similarities in the requirements of each type of
documentation and how those requirements might be addressed.

Geoff Hart pointed out the issue of being 'lost in hyperspace' an issue that I
would think requires further study. How can the user be kept 'in context' when
drilling around in on-line documentation?

Or, in printed documentation how do you best present detailed information yet
still allow the user to quickly find procedural instructions that don't assume
they've read the whole book?

Eric L. Dunn



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
---
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
http://www.raycomm.com/techwhirl/ for more resources and info.