Possible to replicate InDesign-to-PDF Hyperlink Destinations directly in Acrobat Pro DC?

[N1t51rk]

When I produce a PDF from InDesign that contains internal links to specific sections within pages (not to just the pages, but a specific heading or other specific anchor point within the page), Acrobat respects the user's zoom level (i.e., inherit zoom). For example, I'm working at 200%, and I click on a link that's endnote superscript marker, clicking that link takes me to that specific endnote, retaining the 200% zoom (or whatever other zoom level I'm at).

When I view that link in Acrobat, it's set to:

- Go to a page in this document > Use Named Destination (with the Named Destination being the Text Anchor created in InDesign)

This is the ideal functionality; a user is working at 200%, they click the link, and are redirected to that link's destination within the document (for example, an endnote at the bottom of the page, within the Endnotes sections, at the end of the document), retaining the zoom level.

In InDesign, I'm creating Hyperlink Destinations (of the type Text Anchor); when exported to a PDF, Acrobat sees these as Named Destinations, and the links pointing to these destination work as described above.

But, if I do this same thing in Acrobat, directly (for example, when remediating a PDF for accessibility and I don't have access to the source the PDF was generated from), this same type of link results in different functionality, with the zoom being set to a fixed zoom level (whatever it was when the Named Destination was created, manually, within Acrobat). And there's no way to link to some text at the bottom a of page (as, when working with Named Destinations in Acrobat, when you've scrolled down to the bottom of a page, Acrobat is now referencing the next page in the document; so there's no way to create the Named Destination properly (without zooming in to an unusable zoom level). The best you can do is link to the correct page (as you can't actually create the Named Destination based on text at the bottom of the page).

I've had this issue for a couple years now, but revisting the issue today as a client was asking why one document (source: InDesign) acts one way, then another document (source: Acrobat direct, as we didn't have access to the original InDesign file) acts another, less desirable way.

So, wondering if anyone knows of a way—within Actobat directly—to create links (interal links, within the PDF itself) that link to a specific destination, retaining the user's zoom level, etc., the same as when using links and Named Destinations in PDF generated from InDesign? Obviously Acrobat "understands" these types of links, but there doesn't seem to be a way to generate them within Acrobat directly?

Any advice would be appreciated.

Thanks,

Kristin.

[JR Boulay]

You can use "PDF Articles": https://helpx.adobe.com/acrobat/using/pdf-articles.html

or

"PDF Destinations": https://evermap.com/Tutorial_ABM_Destinations.asp

(curiously missing from Adobe's documentation)

[N1t51rk]

Appreciate the attempt, but neither of these provide a solution to the question asked. I'm not really sure how PDF Articles is even relevent to the question? And I mentioned the Destination functionality a number of times in my OP, and in fact the question itself asks why Destinations created in Acrobat directly don't function the same as Destinations in Acrobat that are automatically created when exporting a PDF from InDesign; that was kinda the whole point of my question. It's nearly impossible to create a Destination in Acrobat (directly) that is anchored to, say, a footnote at the bottom of the page (as, Destinations, when created in Acrobat directly, rely upon the "current view" of the page; and when you try and set a Destination that targets content at the bottom of the page, the Destination that's created ends up referening the completely wrong page; the next page). In addition to that, Destinations created directly in Acrobat are set based on the zoom level and scroll location of the document, when the Destination itself is created; so Acrobat-based Destinations end up causing the user's zoom to change (and if targeting content at the bottom of the page, get set to the wrong page); yet, Destinations in Acrobat, when coming from InDesign, inherit the zoom of the user, and the jump to the exact, precise location. But, I'm just restatating everything that I was asking in my OP.