From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Link from a PDF to a reference of an embedded PDF
Date: Mon, 24 Jul 2023 19:13:51 +0200 (CEST) [thread overview]
Message-ID: <q6408o41-43s5-r38n-534r-12129qprs0q5@hzvpu.rqh> (raw)
In-Reply-To: <4626410.LvFx2qVVIh@falbala>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
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
[-- Attachment #2: Type: text/plain, Size: 495 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-07-24 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 14:25 [NTG-context] " Gerion Entrup
2023-07-22 8:29 ` [NTG-context] " Pablo Rodriguez
2023-07-24 16:04 ` Gerion Entrup
2023-07-24 17:13 ` Aditya Mahajan [this message]
2023-07-25 15:38 ` Pablo Rodriguez
2023-07-26 17:47 ` Pablo Rodriguez
2023-07-27 15:20 ` Pablo Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q6408o41-43s5-r38n-534r-12129qprs0q5@hzvpu.rqh \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).