Re: Generating a TOC without pagenumbering

Article View: adobe.framemaker

Article #23348

#23348

From: Ian Burton
Date: Mon, 02 Dec 2002 15:24

6 lines
1528 bytes

Hello sreelatha,
TOC generation is a book level function. To generate a TOC for each chapter, you'd need to create a "book" for each chapter and setup the book and file numbering schemes by hand so that the <$chapnum> value was set appropriately. This is not complicated but needs a lot of time and careful work to setup and there's no way I know of simply automating this in FM as delivered.

Another atlernative you might try is; once the TOC and book is assembled and nearly finished, copy paste segments of the complete TOC to separate files, and include these in the final pre-publication book without doing a generate/update. I have not tried this and there might be some pitfalls I have not thought of.
Cheers
Ian

Technical Details

Message-ID: <1de6cab5.3@WebX.la2eafNXanI>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!newsswitch.lcs.mit.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!WebX

References: <1de6cab5.-1@WebX.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd315,23214082ac29aa8d
X-Google-Attributes: gidfd315,public
X-Google-ArrivalTime: 2002-12-02 07:38:06 PST
From: "Ian Burton" <iburton@noos.fr>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!newsswitch.lcs.mit.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.framemaker
Subject: Re: Generating a TOC without pagenumbering
Message-ID: <1de6cab5.3@WebX.la2eafNXanI>
Date: Mon, 2 Dec 2002 07:24:50 -0800
References: <1de6cab5.-1@WebX.la2eafNXanI>
Lines: 15
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message