From: Pablo Rodriguez <oinos@gmx.es>
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: Thu, 27 Jul 2023 17:20:44 +0200 [thread overview]
Message-ID: <ada902ce-e451-1dc8-a2ee-02fb58c1e226@gmx.es> (raw)
In-Reply-To: <705db9bb-2864-5f6d-6ef0-bde83042644e@gmx.es>
On 7/26/23 19:47, Pablo Rodriguez wrote:
> [...]
> The real issue is that I couldn’t make it work with any PDF viewer I
> have on Linux.
> [...]
> I take for granted that Acrobat will deal fine with this, since
> destinations in links (GoToR) seem to be fine.
Gerion, I was wrong, since I forgot enabling interaction in the main PDF
document to generate the targets (or named destinations).
\setupinteraction[state=start, focus=standard]
\starttext
\dorecurse{15}
{\chapter[chap\recurselevel]{Chapter}}
\stoptext
The first line was missing yesterday.
After that (and with the ouput from the second sample from my previous
message
[https://mailman.ntg.nl/archives/list/ntg-context@ntg.nl/message/IEEGSAL636X32C3WWMO2KWKXMTIARRGZ/]),
Xpdf/Evince/Okular solve remote links fine.
MuPDF-GL cannot solve the file (even when full path is provided) and
PDF.js doesn’t even seem to care there might be a link.
I’m totally ignorant about what Acrobat and Edge/Chrome might do.
I hope this helps,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-07-27 15:24 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
2023-07-25 15:38 ` Pablo Rodriguez
2023-07-26 17:47 ` Pablo Rodriguez
2023-07-27 15:20 ` Pablo Rodriguez [this message]
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=ada902ce-e451-1dc8-a2ee-02fb58c1e226@gmx.es \
--to=oinos@gmx.es \
--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).