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: Microsoft Binder? From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:DGoldstein -at- DeusTech -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:21 Jan 2004 21:07:09 GMT
I'm wondering why you'd want to do this, if the purpose is
to keep a record of procedures that are published (and,
presumably, performed?) separately. In this situation, I
would lean toward preserving the formats and page
numbers of the individual documents, and providing front
matter that lists each document by title, part/doc number
and current rev to provide an "executive summary" of docs
and status at the time the record was produced. This
used to be fairly SOP back when I was in the DoD/aircraft
industry where various maintenance procedures were all
issued separately and maintained in huge (hardcopy)
binders. I've done this in the distant past with MS Binder
(these days we do it all with Acrobat) and didn't seem to
have any problems. I have no idea if unifying the headers
and page numbers will introduce any unexpected problems.
------- Original Message -------
Wed, 21 Jan 2004 14:45:33 -0500 Goldstein, Dan?wrote:
Microsoft Binder allows us to print them with a single header and footer,
including page numbering that carries across the documents. The Binder file
is pretty large, but apparently more stable than a Word document of