Copy link to clipboard
Copied
I have been working on developing a template which allows the user to work with a List of Effective Pages. This feature is essential in many types of documentation.
Lists, however, are not exported as HTML5. Some lists are, in a sense, exported , like the TOC and the Index, but a list of figures, tables etc will not appear in the HTML5 publishing output. I believe this is unfortunate and it makes HTML5 publishing a poor option in many scenarios.
Can it be fixed? Beyond workarounds like pasting the document into other documents and similar "magic"?
Copy link to clipboard
Copied
Can you work around it by having the list present twice:
This workflow might require double Updates (which I do anyway, for other reasons).
There is of course the wide question of how these page-oriented assets are presented in a content-oriented context like HTML. Hyperlinks only?
Copy link to clipboard
Copied
I can import the loep into anothe document and have it publish to html5. Only not with the hyperlinks. It is a doable approach, but it does come with some limitations. No hyperlinks and it will make a mess of pagenumbers/chapternumbers etc.. I have never fully understood why lists are not being published as HTML5. It makes little sense when they are so crucial in highend publishing.
Copy link to clipboard
Copied
I bet the thinking is that LOEP is a print-publishing concept and really doesn't translate well to HTML.
Fire up the Tracker (https://tracker.adobe.com/) and log an enhancement request!
Copy link to clipboard
Copied
Yeah, you may be right. Thank you.
Copy link to clipboard
Copied
Yep, LOEP is (was?) used to ensure the proper paper got updated in a 3-ring binder.
I believe FAA auditors still track PDF pages this way, but once published to HTML, basically everything is today's version. You might use attributes in structured FrameMaker, or version control software to manage, but not a big HTML requirement.
Copy link to clipboard
Copied
Thanks @Matt-Tech Comm Tools I understand that HTML is a different medium. I don't understand why FM is not able to publish generated lists to HTML5. Seems like a big limitation to me. Regarding the track keeping of pages - this is still relevant in HTML as well.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now