Mini TOC hypertext link issues in HTML5

[default6reu278ny2xc]

When creating the Mini TOC, I have checked the box to create hypertext links. The Mini TOC links work in FrameMaker, and they work when I publish as PDF. However, when I publish as HTML5 or even basic HTML, the Mini TOC shows up as normal texts and are not linked.

[Jeff_Coatsworth]

I honestly don't know if those survive the translation into HTML5, but the first thing I would be checking is your Publish Settings for creating HTML5. Have a look in there to see if you need to map those mini-TOC elements to some HTML style of CSS format. Another thing is to check out the resulting HTML output and see how those mini-TOC bits came through - are they just like plain text or are they wrapped in some mal-formed HTML syntax? That might give you a lead on what's going wrong.

[Jeff_Coatsworth · Accepted solution]

Follow up - see this thread - https://community.adobe.com/t5/framemaker-discussions/how-to-change-appearance-of-mini-toc-in-html5/... 

[default6reu278ny2xc]

I figured it out. I had to manually define a mini TOC in the HTML template for it to show up on HTML5. Thanks for your help!

[default6reu278ny2xc]

But then I ran into the issue of the mini TOC appearing twice like this:

[April38363617si18]

We are generating Frameless. if that makes any difference.

[davidcfrye]

I'm glad you got what you needed, and I wouldn't want to quibble about your approach. But... when you create the HTML5, if you have a full TOC file for your book, it will create a complete, nested, collapsible headings list in the left-hand nav bar. When we generate our output in PDF, the mini toc's are kept because we offer chapter by chapter PDFs in addition to a single book version. But, in the HTML sts file, we exclude mini toc formats altogether. Users can then use the nav bar to get wherever they're going. To each his own, but I thought I'd mention it in case you have some case where you don't already have a full book TOC.

[April38363617si18]

Thanks for the information, we do use the full TOC. However, we are still having the issue. We have a work around for the users but we have the issue again even after making all the changes.