Methods to redo book

[Les Smalley]

Do you mean there are hundreds of references going between files within the one book, or going between files in different books?



If the former, it's not as daunting as you may think, especially as you 
have clean templates and a new book file ready.  I would re-create the 
book exactly in a parallel folder with empty files - just save copies of
 the clean template with the desired names in the folders of your new 
book directory.

Then copy the content of each of the orginal FM 
files into the same-named 'chapter' in the clean book and save them.  
Don't worry about cross-references until that's complete.  Once 
it is, you should be able to simply update the book, and as the 
file names are the same, the XRefs should all resovle
 properly.

The final task may be to recheck that all the content 
is tagged with formats in the catalogs (paragraphs, char strings, tables
 and XRefs), and of course do any tweaking needed to paginate as
 you desire.


If instead there are numerous references between files in multiple 
books, the process is the same but just longer... keep copying content 
from old files to clean template files until everything is done, then go
 back and update every book.  It make take twice going through them all 
to get the references resolved but still should work.


aside: FM understands more of the path data than just the current 
('dot') or parent ('dot-dot') directory... it stores references as 
relative paths using a unix-like dotted notation unless it crosses a 
root folder of a drive, then FM switches to an absolute reference (drive
 & path) notation.  So you can go up four levels and then down a
 new path  (../../../../dir1/dir2) and FM happily follows along.

– Les

--- On Sat, 3/12/11, Steve Rickaby <srickaby at wordmongers.demon.co.uk> wrote:
At 08:31 +1300 13/3/11, Alan T Litchfield wrote:

> It may make it easier if the directory structure is the same as previous and
> with the same file
 names.

Absolutely. Best to always keep a book under the same 
root folder; just clone that and work on the clone. Always worked for
 us. I think this is because FrameMaker stores links using Unix dot and 
dot-dot notation, which means that it understands siblings and parents, 
but nothing higher in the directory path.

It gets harder if you have a lot of imported files shared between books.

-- 
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20110313/9d96f0af/attachment.htm>