ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andres Conrado Montoya Acosta <elandi@chiquitico.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with interaction=all and \insertpages
Date: Tue, 22 Sep 2020 23:34:35 -0500	[thread overview]
Message-ID: <CAGhDZhCWZNfaGBNsgZn-6pnO5UOuv3qRqfQNEUm4X5AtmQm7Mg@mail.gmail.com> (raw)
In-Reply-To: <mailman.1.1600682401.26760.ntg-context@ntg.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --]

I am also following this question and some related ones by Pablo with great
interest, and it seems to me that it's falling through the cracks... so, I
am asking again: is it possible to preserve links correctly when imposing /
inserting pdf pages in ConTeXt?

El lun., 21 sept. 2020 a las 5:00, <ntg-context-request@ntg.nl> escribió:

>    3. issue with interaction=all and \insertpages (Pablo Rodriguez)
>
> Dear list,
>
> I have the following sample:
>
>   \setuplayout[page]
>   \setupinteraction
>      [state=start, color=, contrastcolor=, focus=standard]
>   \enabledirectives[references.border=red]
>   \setupexternalfigures[interaction=all, method=pdf]
>   \setupinteractionscreen[option={portrait, paper}]
>   \starttext
>   %~ \insertpages[http://gaceta.rsme.es/abrir.php?id=1495][width=0pt]
>   \insertpages[GacRSocMatEsp.pdf][width=0pt]
>   \stoptext
>
> I have some issues with it.
>
> 1. For some strange reason, the first \insertpages command with a remote
> file cannot deal with the interaction from the file (no internal or
> external links).
>
> 2. The local file includes internal destinations to page parts. After
> imposition, destinations to page for internal links cannot reach the
> page parts as links in original document do.
>
> 3. Even external links are converted. On last page,
> https://www.cs.umb.edu/~offner/files/pi.pdf is rewritten as
> https://www.cs.umb.edu/õffner/files/pi.pdf.
>
> Besides the rewritten link, would it be possible that links are added so
> they reach the same destinations as their source PDF document?
>
> Many thanks for your help,
>
> Pablo
> --
> http://www.ousia.tk
>

Thanks for your attention.
-- 
Andrés Conrado Montoya
http://chiquitico.org

[-- Attachment #1.2: Type: text/html, Size: 2799 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

       reply	other threads:[~2020-09-23  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1600682401.26760.ntg-context@ntg.nl>
2020-09-23  4:34 ` Andres Conrado Montoya Acosta [this message]
2020-09-20 16:29 Pablo Rodriguez
2020-09-23  9:59 ` Taco Hoekwater
2020-09-23 15:06   ` 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=CAGhDZhCWZNfaGBNsgZn-6pnO5UOuv3qRqfQNEUm4X5AtmQm7Mg@mail.gmail.com \
    --to=elandi@chiquitico.org \
    --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).