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: Maintaining a Readme From:John Boland <JohnMethod -at- AOL -dot- COM> Date:Wed, 9 Jun 1999 12:40:09 EDT
Gerry, you write to techwr-l:
<< How do you deal with last minute information that needs to go into a
Readme file [with] InstallShield [, so] if the Readme changes (which it often
does), a new build must be generated (and subsequently tested). >>
I am having my software contractor put the ReadMe.txt, help.chm, sample data,
and tutorial(s) outside the InstallShield "brick", since I "change" or
"improve" these per customer complaints and suggestions.
The unchanging InstallShield script copies these files into the
This somewhat decouples the software development from the documentation and
builds in some flexibility.
CWQ (Call With Questions) or improvements. 8^D
John G. Boland, president