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.
Lawrence...You gave me a couple of ideas that I can use. Thanks a bunch!
Laurence Burrows wrote:
> First, we name our files Chapt1, Chapt2 ...Chapt10, Chapt11, etc.
> Now, if I have a Frame crash, it will create a file for Chapt1 called
> Chapt1@ and a file for Chapt11 Chapt1 -at- -dot-
> FrameMaker: Chapter 1, Lesson 1, paragraph 1...
> Filenames shall be:
> (and Appx01, Appx02, etc.)
> Thataway, when you have a Frame crash, it will create a file for Chap01
> called Chap01@ and a file for Chap11 Chap11 -at- -dot- Ain't technology wunnerful?
> Also, as a bonus, all your chapter files will be listed in their correct
> order in Windows Explorer & FrameMaker File dialogs.
> Even better, make a new folder for each revision of the book, and copy
> *all* the Chap & Appx files to the next revision folder before making
> changes. You can then use FrameMaker's file compare function to see what
> changes have been made between revisions, or over all revisions.