Re: Maintaining COTS documentation

Subject: Re: Maintaining COTS documentation
From: Keith Hood <klhra -at- yahoo -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 16 Aug 2006 14:18:00 -0700 (PDT)

If the company is OK with the idea of producing
manuals by just doing a little trimming on the
original manufacturer documentation, it seems to me
that developing the information for your deliverables
should be fairly cut and dried. Is it just that there
is so much of it?

If they are literally lifting material from the
manufacturer's docs, that of course is a copyright
issue. Have the company lawyers been asked about this?

--- Peter Sturgeon <prsturgeon -at- yahoo -dot- com> wrote:

> I'm working on a multi-vendor, multi-platform system
> and trying to write a sys config and a sysops
> manual.
> In some cases, we have a 5-10 line diff from the
> manufacturer's own installation or configuration
> information.
> So far the people on the project have been cloning
> the source information (into MS Word), then editing
> it to make it specific for our systems.
> I'm the first writer hired to buld two fairly
> massive manuals out of all this stuff.
> Should I just walk away?
> (It's a bit overwhelming.)


Keith Hood
Senior (only) tech writer
ACS, Inc.

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around

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!

Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at

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

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 for more resources and info.

Maintaining COTS documentation: From: Peter Sturgeon

Previous by Author: What not to write when you have no content
Next by Author: Re: Cases for telecommuting/working remotely
Previous by Thread: Maintaining COTS documentation
Next by Thread: looking for feedback re: search engine for uncompiled HTML help

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

Sponsored Ads