Re: TOC specifications?

[Dan Emory <danemory@xxxxxxxxxxxx>]

At 12:05 PM 4/8/00 -0500, Albert Wagner wrote:
>--------------------------------------Snip
>Problem: I want to split a paratag (ChapterTitle) between two lines,
>each in a different text frame, so that line 1 content is the chapter
>number (paranum) and line 2 content is the chapter name (paratext). I
>have done this by using a 1 line frame just long enough for the paranum,
>forcing the paratext to overflow into the second frame/line. This looks
>fine in the chapter.fm.
=====================================================================
Why would you want to do it that way? You're asking for trouble by creating
two text frames for splitting a single paragraph and then adjusting the
width of the first text frame so as to force an overflow of the chapter
title to the second text frame.

Why not create two paragraph tags, ChapNum and ChapTitle? Use the paragraph
designer to set up the format for these two tags so that they have whatever
juxtaposition (i.e., alignment, space above/below, line spacing, etc.) to
each other you desire. Only the ChapNum para tag has an autonumber
specification.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
The rub comes when trying to get it to show
>correctly in the TOC.  If the paratag 1 is used for TOC and paratag 2,
>the text overflow, is the same then I double number. If paratag 2 is
>different, say ChapterName, then it does not seem to be available when
>the TOC is built.  In short, I am stuck with either double numbering or
>a truncated ChapterTitle.
======================================================================
No you're not. Only the ChapNum paragraph has the autonumber. The first time
you generate the TOC, include both paragraph tags in the list of tags to be
included in the TOC. Now, open the generated TOC file, and go to the TOC
reference page in that file. You will find two paragraph tags, ChapNumTOC
and ChapTitleTOC.
Suppose you want the resulting TOC to show the chapter number ant title this
way:

Chapter 1: Chapter Title ................................................1

To get that result, set up the two paragraph tags this way in the generated
TOC file:

1. For ChapNumTOC

a. On the reference page, specify the the following as the content

Chapter <$paranumonly>

Also:

b. Specify that paragraph ChapNum has an autonumber format of Chapter
c. Specify that paragraph ChapNum has the RunIn Head format, with default
punctuation consisting of a colon followed by a space.


2. For ChapTitleTOC

a. On the reference page, specify the following as the content (<TAB> is to
be replaced by an actual tab character)

<$paratext><TAB>

b. Specify a right-aligned tab stop with dot leader. The tab stop position
must equal to (or slightly less than) the width of the text column in which
the generated TOC listings will appear.


3. After setting up the paragraph formats and reference page content as
described above, save the generated TOC file, and re-generate the TOC. The
correct TOC format will now be produced
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>This sent me digging into the TOC specs, which prompts these questions:
>1)  In the 5.5.6 Dummy book, only creating a TOC.fm file is discussed. 
>How do I import a TOC template, as from the Book template that comes
>with frame, and have it used by frame?
==========================================================
See Step 3 above. the saved generated TOC becomes the template. You can set
up the master pages to have whatever layout you wish.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>2)  I built my chapters from the Book chapter template.  They each have
>a TOC specification that is different from the TOC specification that I
>create. Which TOC specs are used when the book is regenerated and a TOC
>is built?
================================================================
The TOC specifications in the saved generated TOC, as well as the paragraph
formats for ChapNumTOC and ChapTitleTOC take precedence if the saved
generated TOC is defined as the TOC file for the book.

After you get the TOC specifications set up the way you want in the
generated TOC file, you could, if you wish, select all the text on the TOC
reference page in the generated TOC file, and copy it to the clipboard.
Then, use the text on the clipboard to replace the text in the TOC reference
page of each chapter file. 
>
     ====================
     | Nullius in Verba |
     ====================
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com
10044 Adams Ave. #208, Huntington Beach, CA 92646
---Subscribe to the "Free Framers" list by sending a message to
   majordomo@omsys.com with "subscribe framers" (no quotes) in the body.


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **