Re: Appendix entries in TOC

Article View: adobe.framemaker

Article #26787

#26787

From: Tim Murray
Date: Thu, 16 May 2002 15:32

12 lines
1579 bytes

Since you have FM6, I would use the new <$chapnum> variable. You set its
value in the book file. In chapters, you simply insert the variable where
you need it -- you don't need to use paragraph numbering. So the heading
might say Appendix <$chapnum>, which will show up as Appendix A on the
screen (if you've set to A in the book file).

The TOC would then use
Appendix <$chapnum>

I noticed you said "I also have this". If you mean you have two sets of TOC
specifications (rather than "I also tried this"), that's a problem ... you
should have only one specification.

Technical Details

Message-ID: <230954776AEA0B51089581BB084D7C1F@in.WebX.aaQKaf7vad4>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!news-out.visi.com!hermes.visi.com!newsfeed.wirehub.nl!newsfeed.media.kyoto-u.ac.jp!newsfeed01.sul.t-online.de!t-online.de!WebX

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

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd315,c4352eb6c0b4b57a
X-Google-Attributes: gidfd315,public
X-Google-ArrivalTime: 2002-05-16 08:37:56 PST
From: "Tim Murray" <tlmurray@techknowledgecorp.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!news-out.visi.com!hermes.visi.com!newsfeed.wirehub.nl!newsfeed.media.kyoto-u.ac.jp!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.framemaker
Subject: Re: Appendix entries in TOC
Message-ID: <230954776AEA0B51089581BB084D7C1F@in.WebX.aaQKaf7vad4>
Date: Thu, 16 May 2002 08:32:18 -0700
References: <ef8909a.-1@WebX.aaQKaf7vad4> <ef8909a.1@WebX.aaQKaf7vad4>
Reply-To: "Tim Murray" <tlmurray@techknowledgecorp.com>
Lines: 14
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message