Skip to main content
A
Anonymous
December 27, 2017
Answered

ToC Run in and not Run In

  • December 27, 2017
  • 3 replies
  • 6207 views

I'm sure someone has answered this, but I can't find it. What is the proper way to produce a ToC that has Level 1 entries not run in with Page number, and has Level 2 entries as Run In separated with ;(space) AND has page numbers as shown in the jpg attached?

Each of these can be from paragraph styles in the text. The ToC dialogue has Run In as an option, but I think that's for the whole ToC?

This topic has been closed for replies.
Correct answer Barb Binder

Is this what you are looking for?

So, you are correct about the entire TOC being run in, or not. But here's how it works: when the tag names are sequential, i.e. 2 or more Trails tags in a row they run in. If the tag names change, i.e., 1 Main Heading followed by 1 Trails, they break on to new lines. So, I see two options:

  1. Make the whole thing run-in and manually adjust after the final update OR
  2. Create two tags for the Main Heading. For example Main Heading and Main Heading1. Be sure Main Heading1 is based on Main Heading and has the exact same definition. (This means if you ever update Main Heading, Main Heading1 will update simultaneously.
    • Alternate the tagging for the consecutive heads (1 is Main Heading, the next is Main Heading1, then Main Heading, etc.) If they aren't consecutive (i.e., Evergreen and Steamboat), they can just be Main Headings.


    • Now back the the TOC dialog box. Map both Main Headings to the same TOC style. Turn Run-in on.



    • Then map the Trails tag to the TrailsTOC style and add your em dash between the entry and the number.
    • Then update!

~Barb

P.S. you do have my favorite Evergreen and Steamboat trails in there somewhere, right?

3 replies

Barb Binder
Community Expert
Barb BinderCommunity ExpertCorrect answer
Community Expert
December 31, 2017

Is this what you are looking for?

So, you are correct about the entire TOC being run in, or not. But here's how it works: when the tag names are sequential, i.e. 2 or more Trails tags in a row they run in. If the tag names change, i.e., 1 Main Heading followed by 1 Trails, they break on to new lines. So, I see two options:

  1. Make the whole thing run-in and manually adjust after the final update OR
  2. Create two tags for the Main Heading. For example Main Heading and Main Heading1. Be sure Main Heading1 is based on Main Heading and has the exact same definition. (This means if you ever update Main Heading, Main Heading1 will update simultaneously.
    • Alternate the tagging for the consecutive heads (1 is Main Heading, the next is Main Heading1, then Main Heading, etc.) If they aren't consecutive (i.e., Evergreen and Steamboat), they can just be Main Headings.


    • Now back the the TOC dialog box. Map both Main Headings to the same TOC style. Turn Run-in on.



    • Then map the Trails tag to the TrailsTOC style and add your em dash between the entry and the number.
    • Then update!

~Barb

P.S. you do have my favorite Evergreen and Steamboat trails in there somewhere, right?

~Barb at Rocky Mountain Training
A
Anonymous
January 2, 2018

PERFECT Barb! Thank you! How did you know that having the two duplicate Main Heads would cause it not to run in? I'd like to understand this better.

But this is exactly what I was hoping for!

I'm guessing you're a Colorado gal. As for the hikes, the author has chosen only his favorites within a 2 hour radius of Denver. There can only be 101 in the book, so he had to be choosey. Steamboat has great hikes, but is too far. The book will launch in April 2019. (A long wait!) I'm looking forward to this one, myself.

You can hear more about the hikes he's researched here: https://basecampguides.com I did the earlier book (another author) Base Camp Las Vegas. It's featured here, but the blog currently is all about Colorado.

Sue

Barb Binder
Community Expert
Barb BinderCommunity Expert
Community Expert
January 2, 2018

Hi Sue!

Yes, I'm in Evergreen, CO and picked up on former Coloradan Erica Gamet​'s comment and decided to have some fun with it. The hikes are all so familiar to me that I'm not sure I would have noticed, otherwise. Are you local, as well? If so, come join us at the Denver Adobe CC User Group! We meet every other month in RiNo, pretty close to Coors Field.

Anyway, I know that the run-in works for multiple instances of the same paragraph tag in the source document, so I was just playing with the concept to come up with an idea for you to handle the front matter. I'm so glad it works for you. Happy new year!

~Barb

~Barb at Rocky Mountain Training
Erica Gamet
Erica Gamet
Inspiring
December 31, 2017

Just a comment to say, "Hi, Sue!" I saw all the Colorado trail names, then your name...I thought, "I know all those places!" Haha...hope Cari's solution works out for you!

    A
    Anonymous
    January 2, 2018

    Hi Erica!

    Hope you are enjoying your new home base!

    Sue

    C
    Cari Jansen
    Legend
    December 31, 2017

    I'd opt to set-up the Table of Contents Style as a Run-in style.  The only issue you'll encounter in that case is that where there are no secondary level headings following a preliminary (top level) heading you'll get those top level headings as run-in headings as well, but can probably easily set-up a Find/Change query that -- based on paragraph style -- removes the ';' delimiter and replaces that with a paragraph return to fix that after the Table of Contents is added / updated

    To NOT get page numbers behind the top level headings:

    1. in The Table of Content Style dialog box where you define the table of contents, click on More Options so you see the expanded version of the dialog box.
    2. Select the Heading (H1 in screenshot below), that is formatted as a Level 1 heading, and set Page Number option to 'No Page Number'.


    A
    Anonymous
    January 2, 2018

    Thanks Cari,

    I didn't want to have to do any modification after the fact. Thought this would work too. See Barb's answer. It worked perfect and no need to futz any further. I don't understand WHY it works, but I'm happy it does.

    Sue

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices