From: "Rob Heusdens" <robheus@xs4all.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Interactive table of content -- jumps always 1 page too far
Date: Sat, 31 Jan 2015 19:28:33 +0100 [thread overview]
Message-ID: <9c1365f5fe99e0f778e872d795dac7d4.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <54CD1B51.1000904@gmx.es>
> On 01/31/2015 05:42 PM, Rob Heusdens wrote:
>> [...]
>> The code looks likes this, but this examples does not exhibit the same
>> faulty off-by-1-page interactive page jump behaviour. In the chapters in
>> the body matter, always directly after a new chapter a section begins
>> (in
>> this example omitted).
>
> Hi Rob,
>
> include in your preamble the following command to avoid makeups not
> being numbered as pages:
>
> \setupmakeup[pagestate=start]
>
> So you donât have to worry about setting counters for userpage.
>
> I donât see any special problem here.
>
> You could define a colophon makeup for the colophon:
>
> \definemakeup[colophon][bottom=]
>
> (BTW, I thought colophons were at the end of the book.)
>
> I wonder what makes your links point to the next page from their
> destinations.
>
> BTW, which OS and PDF interpreter are you using?
>
>
> Pablo
Hello Pablo,
The problem is NOT that the pagenumber as displayed on the page and the
page counter in the viewer ar not in sync (because that is repairable by
either setting the pagestate=start in the makeup, or by setting the page
counter directly, as I did as temoporary workaround).
The problem is that the viewer sends me to the wrong page (always off by 1
page too far) in the interactive table of contents.
So far I have not figured out where to look for, or make a MWE that
exposes the same problem.
The code I sent, resembling the setups I use and document structure I use,
did NOT expose that error, so I conclude that the problem is (most likely)
not viewer related.
I use an Evince Document Viewer 3.10.3 on Ubuntu.
If I have time I will use the \enabletrackers to see if that can direct me
to where the problem may be located.
Greetings & thanks,
Rob
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-01-31 18:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 0:16 Rob Heusdens
2015-01-31 9:54 ` Hans Hagen
2015-01-31 17:53 ` Rob Heusdens
2015-01-31 12:12 ` Pablo Rodriguez
2015-01-31 12:36 ` Hans Hagen
2015-01-31 14:50 ` Pablo Rodriguez
2015-01-31 18:58 ` Rob Heusdens
2015-01-31 22:39 ` Hans Hagen
2015-01-31 16:42 ` Rob Heusdens
2015-01-31 18:04 ` Wolfgang Schuster
2015-01-31 18:16 ` Rob Heusdens
2015-01-31 18:13 ` Pablo Rodriguez
2015-01-31 18:28 ` Rob Heusdens [this message]
2015-01-31 19:02 ` Pablo Rodriguez
2015-01-31 19:11 ` Rob Heusdens
2015-01-31 19:32 ` Pablo Rodriguez
2015-01-31 19:51 ` Rob Heusdens
2015-01-31 20:23 ` Rob Heusdens
2015-01-31 20:31 ` Pablo Rodriguez
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=9c1365f5fe99e0f778e872d795dac7d4.squirrel@webmail.xs4all.nl \
--to=robheus@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).