Re: Page numbering in TOC with Parts separators

Article View: adobe.framemaker

Article #25478

#25478

From: Anastasia Semerok
Date: Fri, 05 Jul 2002 09:19

10 lines
1519 bytes

I'm basing my answer on my knowledge of FM6. 

1. Make sure that in the body of the book, you use different styles for Chapters and Parts. (For ex, ChapStyle and PartStyle). The numbering for PartStyle should be something like <n+>, and the one for ChapStyle -- <n>-<n+>. 
This will guarantee correct numbering in the body of the book. 

2. TOC is generated based on the styles set in the book. Thus, the TOC itself has corresponding styles like ChapStyleTOC and PartStyleTOC. 

3. In the Reference pages of the TOC, make sure that the numbers for these styles are taken directly from the corresponding styles in the body. For this, use tags <$paranum> or <$paranumonly>. Note: do not force the numbering of the styles in TOC. 

Hope this helps.

Technical Details

Message-ID: <ef973dc.1@WebX.aaQKaf7vad4>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!newsfeed.gamma.ru!Gamma.RU!diablo.netcom.net.uk!netcom.net.uk!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX

References: <ef973dc.-1@WebX.aaQKaf7vad4>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd315,bbb8be8b1caab2a4
X-Google-Attributes: gidfd315,public
X-Google-ArrivalTime: 2002-07-05 02:38:23 PST
From: "Anastasia Semerok" <anastasia@semerok.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!newsfeed.gamma.ru!Gamma.RU!diablo.netcom.net.uk!netcom.net.uk!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.framemaker
Subject: Re: Page numbering in TOC with Parts separators
Message-ID: <ef973dc.1@WebX.aaQKaf7vad4>
Date: Fri, 5 Jul 2002 02:19:42 -0700
References: <ef973dc.-1@WebX.aaQKaf7vad4>
Lines: 17
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message