From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: list not following "focus=standard"
Date: Fri, 14 Oct 2022 23:24:39 +0200 [thread overview]
Message-ID: <af31a577-3f8d-b3b2-b436-d1dd62168086@gmx.es> (raw)
Hi Hans,
I have the following sample:
\setupinteraction[state=start,
focus=standard]
\starttext
\completecontent
\section{section}
a\footnote{\contextversion}
\stoptext
With version from 2022.09.11 20:44, the link from the TOC reads in the
PDF file:
4 0 obj
<<
/D [ 1 0 R /Fit ]
/S /GoTo
>>
endobj
Instead of being a named destination, such as in:
5 0 obj
<<
/D (#3)
/S /GoTo
>>
endobj
11 0 obj
<<
/D [ 1 0 R /XYZ 61.65861 129.0214 null ]
>>
endobj
40 0 obj
<<
/Limits [ (#3) (content) ]
/Names [ (#3) 11 0 R (*3) 10 0 R (content) 7 0 R ]
>>
endobj
This is the problem originally reported by Sylvain
(https://mailman.ntg.nl/pipermail/ntg-context/2022/106836.html).
I apologize, but I’m afraid I cannot provide a patch.
Could you take a look at it?
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://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-10-14 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 21:24 Pablo Rodriguez via ntg-context [this message]
2022-10-16 11:28 ` Pablo Rodriguez via ntg-context
2022-10-16 11:48 ` Pablo Rodriguez via ntg-context
2023-01-30 11:18 list not following "focus=standard"? Pablo Rodriguez via ntg-context
2023-01-31 11:29 ` 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=af31a577-3f8d-b3b2-b436-d1dd62168086@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).