Re: Corrupted Files

[Laurence Burrows <burrows -at- IBM -dot- NET>]

John Posada wrote:

--------------snip
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- 
--------------snip

FrameMaker: Chapter 1, Lesson 1, paragraph 1...

Filenames shall be:
 Chap01
 Chap02
 Chap03
 ...
 Chap10
 Chap11
 etc.

(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.

Example:

 BlobManual-Release 5.1
    |-Graphics
    |   |-BMP
    |   |-EPS
    |   |-TIF
    |-Original
    |-Rev01
    |-Rev02
    |-Rev03
    |-...
    |-SignOff

This structure also preserves the relative pathnames for all your
IncludeByReference graphics, thereby saving mucho de greef when collecting
files together for publication.

** above lessons learnt the *hard* way  :-)

Regards,

....................................................
Laurence Burrows, Navex Pty Ltd
mailto:burrows -at- ibm -dot- net, 100026 -dot- 172 -at- compuserve -dot- com
tel: +61 3 9602 4533  fax: +61 3 9602 4854
....................................................

 From ??? -at- ??? Sun Jan 00 00:00:00 0000=