page number indicator goes wrong in Table of Content

This forum is for Single-Sourcing your Flare content to multiple outputs.
Post Reply
chenyu
Propeller Head
Posts: 33
Joined: Thu May 20, 2010 2:02 am

page number indicator goes wrong in Table of Content

Post by chenyu »

I'm rendering pdf file with Table of Content. Some topics in my TOC repeat. When the topics appears again, the page number indicator in that Table of Content refers to the place where it appears first, but not the actual page number. Can I know how to deal with it?

Thanks!
LTinker68
Master Propellus Maximus
Posts: 7247
Joined: Thu Feb 16, 2006 9:38 pm

Re: page number indicator goes wrong in Table of Content

Post by LTinker68 »

Huh. I've never inserted a topic twice into a print output twice, but this is similar to what happens when you insert a topic twice in online output, except in that case it's the bookmarks that are screwed up. The solution for that problem should work here, too. The solution is to copy the contents of the topic into a snippet file, then create two topic files and insert the snippet into each topic file. You then insert one topic into the TOC at the first location and the second topic in the second location in the TOC. Even though the content in the two topic files is the same and pulling from the same source (so you only make changes in one file), Flare will treat each topic file independently, so the page numbering should be fine.

You can also submit a bug report at http://www.madcapsoftware.com/bugs/submit.aspx.

Just out of curiosity, any particular reason why you don't just use a cross-reference? For example, "see Topic X on page 23 for more information"? Or is the topic something like how to contact tech support?
Image

Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
chenyu
Propeller Head
Posts: 33
Joined: Thu May 20, 2010 2:02 am

Re: page number indicator goes wrong in Table of Content

Post by chenyu »

Thank you very much, LTinker68. Your suggestion is valuable. I'll take it into consideration.

Thanks again.
Post Reply