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.
Subject:Copyrights and manuals, take II From:"Geoff Hart (by way of \"Eric J. Ray\" <ejray -at- raycomm -dot- com>)" <ght -at- MTL -dot- FERIC -dot- CA> Date:Thu, 25 Feb 1999 06:23:32 -0700
Gilles Cassin responded to my note that material in manuals is
copyrighted and shouldn't be used without permission by stating <<if
your purpose is to create a help or a manual for your company in
order to adapt the contents of the basic material for internal use,
you should ask permission to the software editor, making clear that
the purpose isn't making money, but giving home-users a faster/easier
way to use the software.>>
It's a good point, and one that I didn't fully address in my original
post other than through my brief statement that you can do all kinds
of fun things with other people's documentation if you can get their
permission first. For example, we've had some discussions here on
techwr-l (check the archives) initiated by techwhirlers whose
companies produce products assembled from other companies' products:
in effect, they licence each other company's documentation for use
with the assembled product, either unmodified or by obtaining the
document files and customizing them (which was the approach I'd
proposed in my original posting). In the former case, you still need
to produce some kind of integration guide to help your customers
understand how to use the composite product with the aid of the
unmodified (and thus, nonspecific) manuals. In both cases, you still
need to enter into some form of licensing agreement for the
documentation as part of the licensing agreement for the products
themselves.