Re: Boring documentation?
Agreed, it is risky for some audiences. But it appears to me that the
people who are turning their noses up at it are the ones who are
"educated" in that field. The fact that they have sold millions of
copies is a testament that that audience is millions strong.
I think that as technical communicators our primary
goal is to communicate *to our audience* appropriately.
People documenting commercial end-user software, such as
Microsoft Word, can probably use a more informal, chatty
style successfully. People documenting UNIX system
administration who use that same style are not going
to be successful and are likely to be seen as condescending
or not authoritative. I don't think it's productive to talk
about which style is "better." This is definitely not a
"one size fits all" profession.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content delivery. Try it today!. http://www.webworks.com/techwr-l
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.componentone.com/TECHWRL/DocToHelp2005
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com
To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.
- Re: Boring documentation?, arroxaneullman
- Re: Boring documentation?, David Loveless
- Re: Boring documentation?, Paul Goble
Search our Technical Writing Archives & Magazine