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:Re: Documenting products integrated with your own From:CASSIN Gilles <GCassin -at- MEGA -dot- COM> Date:Fri, 16 Apr 1999 10:35:51 +0100
We have this type of problem. The solution we agreed on is:
When the information is really useful, give it (though it's tricky,
since, for instance, the update field key changes at each new M$word
release, and sometimes is localized (yes, they change key assignments
when translating...).
But always state: "This part summarize information that you may need to
properly use our software together with So&So's software. This may
change if you use another version (language or release) than the one
described here. Please refer to So&So's software documentation for more
details.", or something like that.
Gilles CASSIN mailto:gcassin -at- mega -dot- com
+33 1 42 75 40 22
My opinions are mine, and neither you nor my company can take credit for
them. YOU can cite them if you think they were of use.
