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: two issues with interactive hyperlinks (please comment)
Date: Sun, 21 Feb 2016 20:54:35 +0100	[thread overview]
Message-ID: <56CA15FB.8070909@gmx.es> (raw)

Hans,

I’m afraid there is a regression partially displayed in the following
code:

    \setupinteraction[state=start, focus=standard]
    \enabledirectives[references.border]
    \setupinteractionscreen[option=fit]
    \setupnote[footnote][way=bytext, location=text]
    \starttext
    \completecontent

    \chapter{Main issue}
    Simple steps to reproduce the issue with notes:

    \startitemize[n]
    \item Open the file and keep browsing it fit to width.
    \item Click on link for note 24 (on next page).
    \item Change view to fit to width.
    \item Search for note 24 in footnotes.
    \item Click back to return to main text from anchor 24.
    \item Change view to fit to width.
    \item Search again for the text with footnote 24 referenced.
    \item Keep in mind that in a 15 inch screen the fit to height,
    text is hardly readable.
    \stopitemize

    \page
    \dorecurse{10}{%
        \dorecurse{10}{This is text.%
            \footnote{This is a footnote.}\par}}
    \placefootnotes
    \stoptext

The regression is that \setupinteraction[focus=standard] doesn’t work
with hyperlink in table of contents for chapter in betas from 2016.02.15
10:26.

Beta from 2016.02.08 15:35 adds a link with named destination (/XYZ).
Next beta from 2016.02.15 10:26 adds a link pointing only to the page
(/Fit).

This is the regression.

And I think it is time to discuss an issue with textual links. I know
you don’t like it. I’m sorry, but I think it is an essential feature for
hyperlinks.

[I’d request other users to contribute their experiences with this
issue, please.]

We need that all links in a text file behave the same way to reach
their destination. Page 2 from sample above describes what is wrong
(and crazy to send a PDF document generated this way [at least, not
relaxing to the reader]).

And if \setupinteraction[focus=standard] is used, all link destinations
should be named ones (/XYZ). Of course, I’m not talking about widgets
for presentations. But footnotes, references, linenotes and other
similar links that may appear in a text should behave the same way in
the same document.

Sorry, but some users complained to me about this behavior. I know that
some PDF readers don’t follow this (only mupdf that I’m aware of
[and I opened an issue:
http://bugs.ghostscript.com/show_bug.cgi?id=696442]). SumatraPDF,
Adobe, evince and xpdf implement named destinations.

It is an extremely useful feature and it isn’t reasonable to expect
from users that they have huge screens to read PDF documents generated
with ConTeXt. And in many scenarios, having a screen version (different
from the print version) is not an option. And as explained in the
sample code above, I have only a 15-inch screen.

Would it be possible that the destinations with links in a text all
honored \setupinteraction[focus=standard]?

Many thanks for your excellent work and 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
___________________________________________________________________________________

             reply	other threads:[~2016-02-21 19:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 19:54 Pablo Rodriguez [this message]
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
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=56CA15FB.8070909@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).