I think you misunderstood my suggestion. A hypothetical FrameMaker
book named bookname.book would be built as follows:

FrontMatter.fm, a single, non-generated file containing this content: 
   -title page content
   -legal page content
   -TOC heading
   -text inset containing TOC content
   -LOF heading
   -text inset containing LOF content
   -LOT heading
   -text inset containing LOT content
Preface.fm
FirstChapter.fm
...
LastChapter.fm
BooknameIX.fm (generated file for index, used directly in book)
BooknameTOC.fm (generated file for TOC content, source for text inset)
BooknameLOF.fm (generated file for LOF content, source for text inset)
BooknameLOT.fm (generated file for LOT content, source for text inset)  

When you get ready to publish, you need to do the Update Book 
operation *at*least*twice* because the text insets get updated as the 
first step in the update sequence, before the generated files are
rebuilt. 
The first update picks up all the paragraphs that need to go into the 
generated files so the generated lists will be the correct length; but
the 
generated files may not reflect the correct page numbers at this point
if there have been any significant changes in the length of any of the 
the generated lists. The second update pass updates the text insets
first so that the FrontMatter file has the correct length and the book
has its final pagination, and this time the generated files will pick up

the correct page numbers. Then you either need to manually update 
the text insets in the FrontMatter file or repeat the Update Book 
operation a third time to ensure that the generated lists with the final
page numbers are reflected in the file that gets printed.

Then to print the final result, select all files except the last three
(i.e.
FrontMatter.fm through BooknameIX.fm, omitting the generated files 
that are the sources for the text insets) and use the Print Selected 
Files in Book command rather than the Print Book command. 

Or you could use Jeremy's approach and have a second book file 
that doesn't even include the three generated files that are used as
source files. You would *never* perform the Update Book command 
on this second file, which would only exist as a convenience for 
printing purposes. 

The only master pages that ever get involved are those in the 
FrontMatter.fm file, and all the final formatting of the generated lists
is controlled from the Paragraph Catalog of this file. If the headings 
for the LOF and LOT are not set to start at top of page, the three
generated lists will follow one on the other with no page breaks and
certainly no blank pages since everything is printed from a single file.

My opinions only; I don't speak for Intel.
Fred Ridder (fred dot ridder at intel dot com)
Intel
Parsippany, NJ



-----Original Message-----
From: framers-bounces+fred.ridder=intel....@lists.frameusers.com
[mailto:framers-bounces+fred.ridder=intel.com at lists.frameusers.com] On
Behalf Of Anne Robotti
Sent: Tuesday, February 21, 2006 11:24 AM
To: framers at lists.frameusers.com
Subject: RE: Importing Generated Files Into TOC

Fred Ritter wrote:
> I think what you'll need to do is import all three generated tables
> into a container file that is not a generated file. For example, you
> might have a non-generated book component called FrontMatter.fm
> that has the headings for the TOC, LOF, and LOT, but which
> includes the actual listings for each as a text inset. The actual
> generated files would be included in the book file as the last three
> items so that you can easily exclude them when it comes time to
> print the book.

Fred, how would I handle the master pages? I don't want any blank pages
in the middle of the TOC, LOF and LOT, but the TOC length keeps changing
and I don't want to keep switching the master pages manually.

This is so frustrating because I *know* I've done this before with no
manual upkeep, I just can't remember how.

Thanks for your help, and keep the suggestions coming everybody!

Anne

--------------------------------------------------------

The information contained in or attached to this e-mail contains
confidential or privileged information. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
the contents of this e-mail is PROHIBITED. If you have received this
e-mail in error, please notify the sender and delete the e-mail
immediately. Thank you.
_______________________________________________


You are currently subscribed to Framers as fred.ridder at intel.com.

Send list messages to framers at lists.frameusers.com.

To unsubscribe send a blank email to 
framers-unsubscribe at lists.frameusers.com
or visit
http://lists.frameusers.com/mailman/options/framers/fred.ridder%40intel.
com

Send administrative questions to lisa at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Reply via email to