ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: random bookmarks not linked (with example)
Date: Mon, 20 Feb 2012 15:12:26 +0100	[thread overview]
Message-ID: <7329A5E6-432A-4B6C-A45B-F71302163F6D@st.estfiles.de> (raw)
In-Reply-To: <4F42347A.7020408@wxs.nl>


Am 20.02.2012 um 12:54 schrieb Hans Hagen:

> On 20-2-2012 11:50, Steffen Wolfrum wrote:
>> 
>> Am 16.02.2012 um 09:48 schrieb Steffen Wolfrum:
>>> 
>>> 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?
>> 
>> 
>> Hi Hans,
>> 
>> is there a chance that there might be a patch that fixes the missing bookmark links in version 2011.05.14,
>> or should I better start locating and linking the large number of missing entries by hand?
> 
> not much chance ... you could grep'n'diff the lpdf-*.lua files and maybe see some change



there are many changes in these files...
so, I replaced all of them in 2011.05.14 by the respective from 2012.02.16, just to see what happens:

1) not very surprisingly, there were no bookmarks at all generated anymore.
2) but in the TOC, the same entries that had no links (as bookmarks and as TOC entries) before, don't have links now.

Doesn't that prove that the changes that fixed this bug were made somewhere else (i.e. in other files)?

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-20 14:12 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
2012-02-20 10:50     ` Steffen Wolfrum
2012-02-20 11:54       ` Hans Hagen
2012-02-20 14:12         ` Steffen Wolfrum [this message]
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=7329A5E6-432A-4B6C-A45B-F71302163F6D@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).