TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
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
> In some cases, we have a 5-10 line diff from the
> manufacturer's own installation or configuration
> 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.)
Senior (only) tech writer
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
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