Issues with Index (TOC) nesting with Basic HTML

Forum|Forum|4 years ago
September 14, 2021
4 replies
243 views

Hello,

I am in FrameMaker 2019, and I am publishing Basic HTML. When I create the output, the index.html file contains the same content as my FrameMaker TOC. However, the nesting is not correct--For example, the TOC entries for the second chapter are nested under the first chapter, and so on through the book. I have tried adjusting various settings, which changes some of what shows up but none of it seems to fix the nesting issues.

As a point of reference, when I publish to responsive HTML, the index there is fine--it is exactly what I have in my FrameMaker TOC.

Has anyone else seen and/or fixed this?

Thanks!

This topic has been closed for replies.

Jeff_Coatsworth

Community Expert

My suspicion is that not a lot of us are producing raw HTML for consumption in other products (or if they are, it's coming out as XML for applications that can consume that instead). You might want to drop a line to the Adobe FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

L

Lisa M123Author

Participant

Thanks so much! I will follow up as you suggest.

Jeff_Coatsworth

Community Expert

My suspicion is that it probably keys to paragraph tags like Heading1 & Heading2 only - what does the code look like in the file? Are there any Settings you can adjust in that Publishing pane for it?

L

Lisa M123Author

Participant

Thanks. The resulting code is just nested <ul> tags. And it actually includes the lower-level headings when I add them to the TOC, but the nesting seems to go haywire. I experimented quite a bit with the various settings, but have not been able to track down anything that fixes it. Thanks for the suggestions. I think that I will continue to experiment with the settings as I expect that the answer is somewhere in all of that. My hope was that someone else might have seen this before.

Jeff_Coatsworth

Community Expert

So you're doing this through the Publishing panel? If that's the case, I thought that the idea of that "raw" HTML was to not have any JavaScript in it (so no TOC or stuff like that).

L

Lisa M123Author

Participant

Thanks for the reply!

You are correct; we are doing it through the publishing panel. And that option produces an index.html page, which contains the contents of the FrameMaker TOC--but in a raw format. We are then using that file as an input into another conversion process, which is why we care about it at all.

That index.html renders (at least in theory) the nesting of the TOC as a series of nested <ul> elements. At the most basic level, this works with some settings, but then, for example, when I try to add additional heading levels, the nesting of <ul> elements gets messed up and stops replicating the structure of the FrameMaker TOC.

Jeff_Coatsworth

Community Expert

This isn't the old method of HTML creation is it? The one that relied upon the settings in your master or reference pages?

L

Lisa M123Author

Participant

Thanks for this idea. I reviewed the reference pages, and while there are HTML-related settings in there, there wasn't anything that I think is impacting the TOC.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded