On 01/11/2023 11:24, David Masterson wrote:
In the Org Mode documentation, I see how hyperlinks are handled in HTML export and how images are handled in Latex export, but is there a clear description of how hyperlinks are handled across export engines (particularly the standard ones)?
Only the code may be more complete reference than backend-specific sections in the manual. There are some issues (e.g. cross-file id links), but in general links should work.
I see that the PDF viewer is seeing file links from exported PDFs from Latex as links, but it seems incomplete (ie. link to a file, but not to a particular CUSTOM_ID in the file).
It seems ::search part is stripped. Perhaps ::#anchor should be exported as #anchor, however it is more tricky with line numbers or text search variants.
I have tried Par <<label>> and [[#cust][link]] * H1 :PROPERTIES: :CUSTOM_ID: cust :END: [[file:t2.org::#anchor]] stripped. [[file:t2.org#anchor]] retained. [[label][link]] and I get Par \label{org59ae2bf} and \hyperref[sec:orgd12b09a]{link} \section{H1} \label{sec:orgd12b09a} \url{t2.org} stripped. \url{t2.org\#anchor} retained. \hyperref[org59ae2bf]{link}
What about Beamer or ascii or Texinfo?
Beamer is derived from LaTeX. In ascii links to headings are supported, but <<anchors>> have no obvious way for export. As to formatting, see the following recent thread:
Max Nikulin. [PATCH] ox-ascii.el: Consistently add brackets around links (was: Re: [RFC][PATCH] Allow to export to ascii custom link types as notes) Tue, 24 Oct 2023 22:06:05 +0700.
https://list.orgmode.org/uh8mgt$lpo$1...@ciao.gmane.io