ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two issues with interactive hyperlinks (please comment)
Date: Thu, 25 Feb 2016 07:51:29 +0100	[thread overview]
Message-ID: <56CEA471.8020000@gmx.es> (raw)
In-Reply-To: <56CC194C.5080400@wxs.nl>

On 02/23/2016 09:33 AM, Hans Hagen wrote:
> the hyperlink mechanism currently has the options page,name,auto (auto 
> being default) so you can try name but still not get what you want; the 
> page variant is needed for documents with 100K or more hyperlinks (and 
> in fact the ability to choose between name/page is also there because in 
> principle we can have backends that only support page linking ... i 
> forgot the details but when pdf came out and acrobat / dvipsone was 
> supported one had named only and the other page only destinations; if i 
> kick out that kind of flexibility we're locked into pdf completely)

Hans,

sorry, but I could only test it yesterday.

I’m afraid it doesn’t work. I suspect what the issue here is.

\setupinteraction[page=name] (or \setupinteraction[focus=standard]) only
affects to the links generated by lpdf-ano.lua.

But footnotes (endnotes, linenotes, index references and similar ones)
have destination links generated by lpdf-epa.lua.

I may be misreading your comment from line 85 in lpdf-epa.lua. But this
is what I get after grepping for "/Fit" in
tex/texmf-context/tex/context/base/ from the beta.

Wouldn’t it be better to have a single code to generate (destination)
links? At least, this would prevent problems such as this one (if I’m
not missing something).

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2016-02-25  6:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 19:54 Pablo Rodriguez
2016-02-22 19:08 ` Hans Hagen
2016-02-22 23:21   ` Pablo Rodriguez
2016-02-23  8:33     ` Hans Hagen
2016-02-24  9:01       ` Pablo Rodriguez
2016-02-24  9:50         ` Wolfgang Schuster
2016-02-25  6:55           ` Pablo Rodriguez
2016-02-25 18:19         ` Hans Hagen
2016-02-25  6:51       ` Pablo Rodriguez [this message]
2016-02-25 10:20         ` Hans Hagen
2016-02-22 19:13 ` Hans Hagen
2016-02-22 20:40   ` Alan BRASLAU
2016-02-22 22:54     ` Martin Schröder
2016-02-23 22:07       ` Alan BRASLAU
2016-02-24  9:25         ` Pablo Rodriguez
2016-02-22 23:32   ` Pablo Rodriguez
     [not found] <mailman.1.1456225201.14598.ntg-context@ntg.nl>
2016-02-23 14:30 ` Christoph Reller
2016-02-23 22:24   ` Alan BRASLAU

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=56CEA471.8020000@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).