Text Insets Appear In TOC

[Art Campbell]

Just askin. ;-  )

If it were me, I'd include a special trigger para tag in the text inset and
in the TOC that only appears at the beginning nad end of the text inset ..
something like TextInsetMarker.

They either delete everything between the beginning and ending entries in
the TOC manually or with a script, or map it out with a conditional text
setting that's set to Hide.

Art

Art Campbell
         art.campbell at gmail.com
 "... In my opinion, there's nothing in this world beats a '52 Vincent and a
redheaded girl." -- Richard Thompson
                                                     No disclaimers apply.
                                                              DoD 358


On Mon, Jan 19, 2009 at 12:56 PM, Joseph <panopticon23 at gmail.com> wrote:

> Hi Art,
>
> Due to the volume of information in this particular document, it is not
> feasible to include every single heading within the document. Furthermore,
> this document is specifically geared towards an audience who is *only*interested in the feature name itself. In other words, the audience ONLY
> wants to know about H1s that correspond to a feature name.
>
> By contrast, the text insets are used throughout documentation that
> consists of over 2,000 pages and 8 documents.  While, the headings are
> appropriate in the rest of the documentation. It is NOT appropriate in the
> 600-page Feature and Specifications document because the H1s for the text
> insets do not correspond to a feature name.
>
> Sincerely,
> Joe
>
> On Mon, Jan 19, 2009 at 10:36 AM, Art Campbell <art.campbell at gmail.com>wrote:
>
>> Joseph, your understanding is incorrect.
>> Because the text in a text inset is in the document, it's indexed, TOCed,
>> and otherwise treated as typed text.
>>
>> ***
>> Just as a usability thing, why wouldn't you want content from the insets
>> to be tracked?
>> Or put another way, what are you trying to do?
>>
>> Art
>>
>>
>> Art Campbell
>>            art.campbell at gmail.com
>>  "... In my opinion, there's nothing in this world beats a '52 Vincent and
>> a redheaded girl." -- Richard Thompson
>>                                                      No disclaimers apply.
>>                                                               DoD 358
>>
>>
>> On Wed, Jan 14, 2009 at 7:53 AM, Joseph <panopticon23 at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am currently working on a 600 page document. This document contains
>>> several text insets. When I update the book, the TOC is populated with
>>> H1s
>>> from the text insets. I understand what is happening, but not why. Since
>>> I
>>> have the TOC set to include H1s, it is looking inside the text inset,
>>> finding an H1, and then putting it in the TOC.  However, I did not think
>>> text insets worked that way. My understanding is that FM ignores the
>>> contents of a Text Inset.
>>>
>>> I  know I could create unique paragraph tags for headings in the text
>>> inset,
>>> which the TOC would not search for. But that would require modifying the
>>> template which hundreds of pages of documentation relies on and importing
>>> that paragraph style into about 20 different books.  I consider that a
>>> last
>>> resort. Is there any other method aside from creating unique para tags,
>>> that
>>> would prevent the inclusion of headings from a text inset in the TOC?
>>>
>>> --
>>> Sincerely,
>>>
>>> Joseph Lorenzini
>>> _______________________________________________
>>>
>>>
>>> You are currently subscribed to Framers as art.campbell at gmail.com.
>>>
>>> Send list messages to framers at lists.frameusers.com.
>>>
>>> To unsubscribe send a blank email to
>>> framers-unsubscribe at lists.frameusers.com
>>> or visit
>>> http://lists.frameusers.com/mailman/options/framers/art.campbell%40gmail.com
>>>
>>> Send administrative questions to listadmin at frameusers.com. Visit
>>> http://www.frameusers.com/ for more resources and info.
>>>
>>
>>
>
>
> --
> Sincerely,
>
> Joseph Lorenzini
> Naperville, IL
> 309-319-4487
>
>