Copy link to clipboard
Copied
I have a book with generated lists of figures and tables. I would like to publish them to HTML5 along with the rest of the book, but FrameMaker 2022 skips them in the publishing process. I have tried different "tricks" in order to force publishing like creating cross references to the documents etc but to no avail.
Would anybody know why things work that way? It looks like a bug, but perhaps there is a deeper meaning or merely a button I have overlooked?
Copy link to clipboard
Copied
Are they listed in the TOC?
Copy link to clipboard
Copied
Not at present, but I have tried adding headings like the rest of the book. But what happens is, that I get the headings in the HTML5 navigation, but the content is a 404 page. I would believe that generated lists are no different from a toc or an index and it should not be necessary to include them via headings. But even if that was NOT the case and headings were the proper way to go, HTML5 publishing still ought to work. Adding cross references won't work either.
Copy link to clipboard
Copied
I'm not up on my FM to HTML5 publishing route, but I thought you had to have everything in the TOC for it to make it to the HTML5 generation. Maybe that degree of control isn't in there - I'm a TCS guy that goes the original FM to RH to HTML5 route. With that workflow, you control what TOC is going to be used to create the RH project.
Copy link to clipboard
Copied
yeah well... TOC and Index are really buillt into the HTML5 "product". Like this:
The index words can acessed directly in the HTML5. And I would somehow expect that similar generated lists like a list of figures would be automatically integrated. But I can not make that work for what ever reasons.
Copy link to clipboard
Copied
No, I would expect you would have to go through the TOC to access your LOF and LOT & then use the xrefs back to the content.
Copy link to clipboard
Copied
This is what happens if I add headlines to the generated list of figures, tables, authors what ever:
I can include the lists in the FrameMaker toc, but when published as HTML5...
I will get a blank page. There is some code / lack of code, that means FrameMaker can't figure out how to handle these documents.
Well... I have had a chat with an Adobe employee who would look into it. We shall see what happens 🙂