ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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:58:02 +0100	[thread overview]
Message-ID: <f20171674a8bb374a2d7adff0b7ebbbb.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <54CCEBB3.5020602@gmx.es>

> On 01/31/2015 01:36 PM, Hans Hagen wrote:
>> On 1/31/2015 1:12 PM, Pablo Rodriguez wrote:
>>> [...]
>>> It doesn’t show what you meant, the link destination is not on the
>>> heading itself, but on the next paragraph.
>>
>> \enabletrackers[*references*]
>> \enabletrackers[*destinations*]
>
> Hi Hans,
>
> many thanks for your reply.
>
> I’m afraid there might be something wrong with this. I have been using
> poppler-glib-demo to check it (and this is the first time I use it, so I
> might be wrong as well).
>
> The minimal sample:
>
>     \enabletrackers[*destinations*]
>     \setupinteraction[state=start, focus=standard]
>     \setupinteractionscreen[width=fit]
>     \starttext
>     \completecontent
>     \chapter{Chapter}
>     \stoptext
>
> Link destination for “Chapter” seems to be:
>
>     << /D [27 0 R /XYZ 70.867 689.409 null]>>
>
> But both chapter headings are placed at x,y (70.87, 122.22), according
> to poppler-glib-demo.
>
> Anyway, there is a proof that something might be rotten, because the
> link itself has a higher box (an it is lower in the page):
>
>     << /Subtype /Link /Dest (#2) /F 4
>         /Rect [70.867 652.344 496.06 666.772] /Border [0 0 0]>>
>
> I cannot give a more accurate description (the PDF spec is all Greek to
> me), but I think there is something wrong with link destinations (they
> seem to be lower than they should be).
>
> BTW, does the sample above work right with Adobe? (I’m don’t have it
> installed.) It doesn’t work with either evince-3.10.3 or mupdf-1.6.
>
>>> I think this should be improved. And I guess it goes unnoticed, because
>>> after clicking on a link, the browser fits view to page.
>>
>> this is also a bit browser dependent i think
>
> I guess this is caused by the link destination syntax (section 12.3.2.2
> of the PDF specification).
>
> Withouth specifying "focus=standard" in the sample above, the link is:
>
>     << /Subtype /Link /Dest [13 0 R /Fit] /F 4
>         /Rect [70.867 652.344 496.06 666.772] /Border [0 0 0]>>
>
> /Fit specifies that the page should be so that its entire width and
> height are magnified enough so that they fit in the window.
>
> Having said that, I cannot see why it makes sense that ConTeXt generates
> documents with this default.
>
> I mean, the default paper size is A4, if the default behavior after
> cliciking on a link is to fit page height (or width in landscape), one
> needs a huge screen not to render the text unreadable.
>
> Sorry, but I cannot see the gain in this default. Would it be possible
> that the default would be the behaviour set by "focus=standard"?
>
> Could you consider both suggestions?
>
> Many thanks for your help,
>
>
> Pablo
> --
> http://www.ousia.tk
>


What I forgot to include in the code ex, was this settings:

\setupinteraction
  [state=start,
  title={Leerboek politieke economie},
  subtitle={politieke economie},
  author={Academie der Wetenschappen van de Sovjet-Unie},
  keyword={economie, politieke economie, marxisme, marxisme-leninisme},
  openaction=FitWidth,
  focus=width,
  date={31 januari 2015}]

I will replace this with:

\setupinteraction[state=start]

and see if that makes a difference...

Greetings,

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
___________________________________________________________________________________

  reply	other threads:[~2015-01-31 18:58 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 [this message]
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
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=f20171674a8bb374a2d7adff0b7ebbbb.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).