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.
This wasn't what you asked, but keep in mind that most likely these
updates, if you are talking about chapters that users have to insert
in binders, are most likely sitting in a pile on the floor in the user's
or system administrator's office. My last company used to provide
updates, but we switched to send out whole manuals because we knew
the updates weren't proving effective.
If your company has a web site, it may make more sense to post updated
PDFs on the web and let customers download the whole manual or the
parts they need.
> My coworker and I are trying to come up with a way to provide multiple
> clients with updates to our user guide. The problem is that each client
> receives a version of the same book, but renumbering the book chapters is
> always necessary, which is time-consuming. So my coworker had the ideal of
> eliminating the chapter numbering and implement a naming convention for
> sections instead. This would actually work quite well if we want to use
> source files to create online help. The only problem I see this causing is
> in the index, where page numbers and entries would be convoluded. So our
> idea is to use an appreviation for the section name in place of the
> number in the index. Then we could provide a legend at the bottom of each
> page in the index for quick reference.
> Thanks for any input,
> Cathleen McIntosh
> cathleen -dot- mcintosh -at- vistacpg -dot- com