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

On Mon, 24 Jul 2023, Gerion Entrup wrote:

Hi Pablo,

...

not sure I’m getting your point right.

Thank you for the detailed answer. But I fear, I have not expressed myself precise enough. The solution that you described does not directly fit to my setting. I'll try to rephrase. Maybe it gets more clear then. I think, named destinations could be a important part in the solution.

I'm do not know the structure of PDFs exactly, therefore some of my terms might be wrong. I'll name the two things from now on the following way: - a destination: This is a defined position within a PDF document; so some position that a PDF viewer is able to jump to. In ConTeXt, you can set such a position most of the time with the "reference" keyword. In LaTeX, you use \label. - a reference: This is a link that you can click on and cause the PDF viewer to jump/scroll to the linked destination. In ConTeXt, you can use \in to create a reference. In LaTeX, you use \ref.

The situation is that I have a PDF-document (inner.pdf) that defines several destinations and I want to embed that document with \externalfigure into another PDF-document (outer.pdf). My question is: Is it possible to create references within the source code of outer.pdf that correctly set a link to a destination that is defined in inner.pdf? Asked in another way: Is is possible that \externalfigure can extract the (maybe named) destinations of inner.pdf and translate them in such a way, that I can use \in within the outer document to link to them.

According to https://wiki.contextgarden.net/Command/setupexternalfigure \externalfigure[....][interaction=reference] should keep all the references (you can also try interaction=all). Not sure how the references get mapped internally, so that they may be linked. Aditya

On 7/25/23 17:38, Pablo Rodriguez wrote:

On 7/24/23 18:04, Gerion Entrup wrote:

...

[…]

I’m in a hurry, excuse my rash reply.

Sorry, Gerion, my reply yesterday was rushed (no skin condition). The solution is already there (in the test files). You have the file with the reference (save it as main.tex): \starttext \dorecurse{15} {\chapter[chap\recurselevel]{Chapter}} \stoptext You have the file that reads the references from main.tuc and generates the inter-document links: \setupinteraction[state=start] \starttext Links to each chapter using \type{main.tuc}: \startitemize[n, packed] \dorecurse{15} {\item Reference to \in[main::chap\recurselevel].} \stopitemize \stoptext The real issue is that I couldn’t make it work with any PDF viewer I have on Linux. Either the viewer doesn’t detect the link (such as PDF.js), or it cannot solve the target file (such as MuPDF and MuPDF-GL), or it cannot reach destinations (such as Xpdf, Evince/Okular or SumatraPDF). I take for granted that Acrobat will deal fine with this, since destinations in links (GoToR) seem to be fine. Of course, to confirm this, it should be tested with Acrobat. Just in case it helps, Pablo