From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: (again) wrong destination types?
Date: Sun, 3 Dec 2023 16:26:41 +0100 [thread overview]
Message-ID: <b30995e9-6c8a-3cfe-9670-22ed1bcc0c6c@gmx.es> (raw)
In-Reply-To: <AA8D0335-FF61-4167-84A5-9A09311DA496@scorecrow.com>
On 11/22/23 00:06, Bruce Horrocks wrote:
> [...]
> I changed your example to the following:
> \setupinteraction[state=start, page=name, focus=standard]
> \starttext
> \input knuth \par
> a\footnote{b} \par
> \dorecurse{7}{\input knuth \par}
> \stoptext
Many thanks for your fast reply, Bruce.
I wanted to reply much sooner, but it was really impossible for me.
>From your explanation, the first link (body to footnote, your point b)
has destination to fit the whole page inside the viewer.
The second link (footnote to body, your point c) has the destination to
reach a position inside the page (where the destination lies). This is
what "focus=standard" should achieve.
In PDF terms (simplified), fit to page destinations are /Fit
destinations and placed destinations are /XYZ destinations.
This sample shows what might be the root issue here:
\setupinteraction[state=start, page=name, focus=standard]
\starttext
\completecontent
\chapter{Chapter}
a\footnote{b}
\stoptext
ConTeXt handles internally links in categories. For some reason unknown
to me, "page=name" triggers that special operation links contain /Fit
instead /XYZ destinations.
This is similar to the wrong link destinations (fit instead of standard)
from TOC (but not in footnotes [which are right]) when compiled with MkIV:
\setupinteraction[state=start, focus=standard]
\starttext
\completecontent
\chapter{Chapter}
a\footnote{b}
\stoptext
I hope it is clearer now. Let me know if it is not.
My issue is that I cannot avoid having "page=name" for links to external
documents, but this breaks footnotes and other special operation links.
Many thanks for your help,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-12-03 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 18:01 [NTG-context] " Pablo Rodriguez via ntg-context
2023-11-21 23:06 ` [NTG-context] " Bruce Horrocks
2023-12-03 15:26 ` Pablo Rodriguez via ntg-context [this message]
2023-12-04 23:21 ` Bruce Horrocks
2023-12-06 19:05 ` 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=b30995e9-6c8a-3cfe-9670-22ed1bcc0c6c@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).