Right, as the point is to represent a physical document, paper and ink (or canvas, toner, whatever -- stuff that doesn't reflow).
Why anyone would use such a format for these situations, where the audience definitely cares way more about consuming it on an electronic device than printing it out, is... mind-boggling.
Of course, AI+ML to the rescue: Liquid Mode [0].
> Files are processed in our secure data servers and immediately deleted from our servers after the experience is generated.
I've found people being precise about the flow of equations and text intermixed can be easier to read than reflowing content. Other than that, not so much.
Edit: Non-reflowing content also works well if you need to refer people to page numbers and paragraphs.
I look forward to playing with liquidmode at some point soon.
CSS flow control and specifying an `id` attribute value as a URL fragment would be my solutions to those particular concerns, if it weren't the case that our context here is capturing from software that offers printing but doesn't offer exporting to HTML very well. I think the solution might be "bring it to a good web dev and have a solid punch list."
Why anyone would use such a format for these situations, where the audience definitely cares way more about consuming it on an electronic device than printing it out, is... mind-boggling.
Of course, AI+ML to the rescue: Liquid Mode [0].
> Files are processed in our secure data servers and immediately deleted from our servers after the experience is generated.
[0] https://www.adobe.com/devnet-docs/acrobat/android/en/lmode.h...