Hi Darren,
yes, you can generate standalone TOCs and import them by reference into a
chapter, but you'll have to update and check each chapter individually each
time you add, remove or change titles in that chapter.
Like Art said the ChapterTOC Framescript is the easiest but also the best
?
-Original Message-
From: Yves Barbion [mailto:[EMAIL PROTECTED]
Sent: Monday, July 07, 2008 8:44 AM
To: Butler, Darren J CTR USAF AFMC 584 CBSS/GBHAC
Cc: [EMAIL PROTECTED]
Subject: Re: TOC within a chapter
Hi Darren,
yes, you can generate standalone TOCs and import them by reference
Hi Darren,
Those that won't buy FrameScript will have to settle for either manual
method: inserting cross-references to make a chapter TOC, or using Special
Table of Contents to generate a TOC and then import it by reference into the
chapter. Considering the significant time savings that a
USAF AFMC 584 CBSS/GBHAC; [EMAIL PROTECTED]
Subject: Re: TOC within a chapter
Hi Darren,
Those that won't buy FrameScript will have to settle for either manual
method: inserting cross-references to make a chapter TOC, or using Special
Table of Contents to generate a TOC and then import
I don't think this option will help in your case, Darren, but in structured
FrameMaker, you can generate mini-TOCs very easily using the FrameSLT plug-in.
In this case, updating each chapter individually is what we want.
I didn't own a copy of FrameScript until recently, so I'll create a
Rick has a good point here, and this brings us to the discussion about the
hidden costs of (doing things manually to create and update) technical
documentation and return on investment (ROI).
You can do the math: 1 tech writer creating, updating and checking all the
local TOCs once in 1 book (of
At 04:58 AM 7/7/2008, Butler, wrote:
I'm considering generating the TOC to a separate file, then importing
the TOC as a text inset.
Any thoughts on this?
Darren,
Are your documents structured? As Yves pointed out, updating an
unstructured book does not update the local tables of contents.
