[NTG-context] Re: (again) wrong destination types?

4 Dec 2023

...
On 3 Dec 2023, at 15:26, Pablo Rodriguez via ntg-context  wrote:
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.
What are you using for links to external documents? If just a single command such as \goto then you might be able to get away with defining a wrapper (e.g. \myGoto) that does \setupinteraction[state=start,page=name,focus=standard] then the \goto command then \setupinteraction[state=start,page=fit,focus=standard] afterwards.

(Assuming calling \setupinteraction that many times does not cause problems in itself.)

—
Bruce Horrocks
Hampshire, UK