Re: Technical writer dream

[Alexia Prendergast <alexiap -at- SEAGATESOFTWARE -dot- COM>]

Yes, I do understand your point --  I think we are
simply using the term "module" differently. I'm *not*
promoting using print stuff for help stuff as is.
There are several methods by which you can reuse info
and customize it for the audience/purpose along the
way at the same time, some more complex and pricey than
others.

A.
--
Alexia Prendergast
Senior Technical Writer
Seagate Software
alexiap -at- sems -dot- com

>----------
janiceg -at- MARVIN -dot- ENG -dot- SUN -dot- COM said:

>Many help systems are set up so that the user asks specifically
>for task and reference information, which is what I was referring
>to below. In that case, reference or conceptual information that
>is necessary to do the task would have to be in the task "module"
>itself, and having it exist in a separate reference or conceptual
>"module" wouldn't help -- you'd still have to slightly rewrite
>the task, although the main information could, of course, be
>reused. And not all tasks would require such information so
>those task "modules" could be reused from print as is.
>

 TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot-  Send commands
   to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
  Search the archives at http://www.documentation.com/  or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html