ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: random bookmarks not linked (with example)
Date: Thu, 16 Feb 2012 09:48:10 +0100	[thread overview]
Message-ID: <BF0CBA7B-2BC9-4A8F-98E1-EB688C80B30C@st.estfiles.de> (raw)
In-Reply-To: <4F3CBC68.4000706@wxs.nl>


Am 16.02.2012 um 09:20 schrieb Hans Hagen:

> On 15-2-2012 12:28, Steffen Wolfrum wrote:
>> Hi Hans,
>> 
>> finally I managed to figure out a "minimal" 3 page example that can reproduce this strange bug!
>> 
>> It seems to be an interaction of \cite and \index with sectioning/bookmark generation:
>> Please run "chap_1.tex" and click on the bookmark "1.1.2 SIX" ... no destination is set.
>> 
>> (As I explained before, this does not mean that anything strange is going on at \subsection{SIX}.
>> If the minimal file was longer, the missing link would have been somewhere else.)
>> 
>> If I delete the used \index entries the bug is gone.
>> And if I delete the used \mycite commands the bug is gone, too.
>> 
>> 
>> I hope this test file might help ...
> 
> like Luigi I get a pdf where 1.1.2 SIX is a proper link


my project is an already finished and printed book.
it was set with context vers. 2011.05.14, in this version the link is missing

now the publishers asked for the pdf (to provide it on-line too) and thus they noticed the defect.

unfortunately running the same project with todays beta gives different line breaks and so different page breaks. which is not acceptable for the publishers.


I retried it with vers. 2012.01.16, also here the link is missing:
do you remember what changed you made between, say 2012.01.16 (not working) and today (working)?
then maybe a patch can be found out that could also be adapted to my original vers. 2011.05.14?

Steffen
___________________________________________________________________________________
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:[~2012-02-16  8:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 11:28 Steffen Wolfrum
2012-02-15 19:59 ` Steffen Wolfrum
2012-02-15 20:39   ` luigi scarso
2012-02-15 22:51   ` Hans Hagen
2012-02-16  8:00     ` Steffen Wolfrum
2012-02-16  8:20 ` Hans Hagen
2012-02-16  8:48   ` Steffen Wolfrum [this message]
2012-02-20 10:50     ` Steffen Wolfrum
2012-02-20 11:54       ` Hans Hagen
2012-02-20 14:12         ` Steffen Wolfrum
2012-02-21 10:17   ` Steffen Wolfrum
2012-02-21 12:37     ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2012-02-15 11:28 Steffen Wolfrum

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=BF0CBA7B-2BC9-4A8F-98E1-EB688C80B30C@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).