On 7/20/23 16:25, Gerion Entrup wrote:
[...] Can I somehow access the references of inner.tex from outer.tex? For me, it is not that relevant, that the correct number is set, but the interaction within the outer PDF should work, so clicking on the reference should scroll to the correct content.
Hi Gerion, not sure I’m getting your point right. As such, one of the features of PDF are named destinations, such as in: https://www.pragma-ade.com/general/manuals/luametatex.pdf#%2381 I consider them as identifiers: https://wiki.contextgarden.net/Installation#Unix If that could be what you might need, here is a sample. First you have the destination file: \setupinteraction[state=start, focus=standard, prefix=n_,] \starttext \dorecurse{50} {a\footnote{b} } \startluacode luatex.wrapup( function() os.rename(tex.jobname .. ".pdf", "ba.pdf") end ) \stopluacode \stoptext Then you have calling file (with file:///): \setupinteraction[state=start, focus=standard] \def\MyURL#1{\goto{\tt#1}[url(#1)]} \starttext Link to other document: \MyURL{file:///path/ba.pdf\letterhash n_73} Link to the web: \MyURL{https://www.pragma-ade.com/general/manuals/luametatex.pdf#%2381} \stoptext file:/// requires an absolute path. It might be handled right or not, depending on your PDF viewer. On Linux, Evince cannot open a file with named destination specified as doc.pdf#destination (or doc.pdf#nameddest=destination). But it understands file:///. MuPDF-GL seems also not to handle named destinations, but it understands file:/// too. PDF.js (the default PDF viewer that comes with Firefox) handles named destinations, but doesn‘t seem to understand file:/// as a link.
Background of my question: I normally do graphics in a separate PDFs. Some graphics consists of source code together with a graphical representation and I want to be able to link to single source code lines.
I think it may be possible, but I don’t know how to generate named destinations for source code lines. Just in case it may help, Pablo