ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: (off-topic) hovering over links in Acrobat Reader
Date: Fri, 21 Jun 2024 18:31:59 +0200	[thread overview]
Message-ID: <b7dac160-b17a-4334-a7f2-74334819b5ba@xs4all.nl> (raw)
In-Reply-To: <25fc4604-d270-4f12-a1de-766b08aca642@gmx.es>

On 6/20/2024 5:33 PM, Pablo Rodriguez via ntg-context wrote:
> On 6/19/24 21:55, Henning Hraban Ramm wrote:
>> Am 19.06.24 um 19:16 schrieb Pablo Rodriguez via ntg-context:
>>> Would you be so kind to test the attached document (and the one you may
>>> generate from the sample source) hovering over the link frames in
>>> Acrobat (ideally DC updated to latest)?
>>>
>>> At least, I would like to be sure what is going on here.
>>>
>>> Hovering over links is basic precaution before clicking them.
>>>
>>> To explain that to others, I’d rather know how Acrobat (Reader) behaves
>>> in these cases.
>>
>> Build 24.2.20857.0 on MacOS 10.15.7:
>> 1: no hover
>> 2: https://contextgarden.net
>> 3: https://contextgarden.net
> 
> Many thanks for your help, Hraban.
> 
> Thanks to your confirmation, I investigated the issue further (since
> there had to be something different with my documents).
> 
> \setuptagging[state=start] is the culprit. "link" is the word displayed
> when links are hovered over.
It's not that hard to get something less generic displayed but the 
question is what and in what detail. A lot of this stuff is not 
consistent over viewers and it being part of the user interface might 
also change over time (some viewers also interpret the page stream for 
urls).

Anyway, a next upload will have this:

% \disabledirectives[backends.references.descriptions]           % just link
% \enabledirectives [backends.references.descriptions]           % some 
detail (some todo) (default)
% \enabledirectives [backends.references.descriptions=reference] % a bit 
less

so that you can experiment a bit with it. We might at some point provide 
optional descriptions per link but the quesiton is how to cleanly 
interface this (easier if you use \define... instead of your own macros 
for urls).

Hans



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------

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

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2024-06-21 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 17:16 [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-19 19:55 ` [NTG-context] " Henning Hraban Ramm
2024-06-19 20:10   ` Wolfgang Schuster
2024-06-19 20:15     ` Henning Hraban Ramm
2024-06-20 16:01     ` Pablo Rodriguez via ntg-context
2024-06-20 15:33   ` Pablo Rodriguez via ntg-context
2024-06-21  9:32     ` Ulrike Fischer
2024-06-21 16:31     ` Hans Hagen [this message]
2024-06-21 17:50       ` Pablo Rodriguez via ntg-context

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=b7dac160-b17a-4334-a7f2-74334819b5ba@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --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).