ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ref.vet.uu.nl
Subject: Re: Fwd: Strange error...
Date: Tue, 05 Nov 2002 09:43:42 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20021105094122.03654ea8@server-1> (raw)
In-Reply-To: <20021104102600.44fc18f9.morawski@gmx.net>

At 10:26 AM 11/4/2002 +0100, Jens-Uwe Morawski wrote:

>After the update to version 2002-10-23 i get the same error. I'm sure
>that it was not there using the previous ConTeXt version. Here the
>message is:
>! pdfTeX warning (ext4): destination with the same identifier 
>(name{page:16}) h
>as been already used, duplicate ignored
><recently read> fit
>
><to be read again>
>                    \egroup
>\fakePDFpagedestination ...e:\realfolio }}\egroup
>                                                   \fi \fi \fi
>\actualshipout ...chbox \hbox {\the \everyshipout
>                                                   \ifnum \realpageno 
> =\lastp...
>
>\myshipout ...pout {\thisisrealpage \realfolio #1}
>                                                   \fi \gotonextrealpage 
> \nap...
>
>\dofinaloutput ...pagebody #1#2\setpagecounters }}
>                                                   \fi \the 
> \everyaftershipou...
>...
>l.40 \stopproduct
>                   [17.17] )
>
>Are you sure that this is not a bug in ConTeXt? I normally do not label
>destinations/references as "name{page:16}".

You can search for page: in spec-fdf.tex, there should be something:

\def\fakePDFpagedestination
   {\iflocation \ifovercomePDFpage \ifarrangingpages \else
      \bgroup
      \advance\realpageno \minusone
      \expanded{\doPDFdestination name {page:\realfolio}}%
      \egroup
    \fi \fi \fi}

\appendtoksonce
   \fakePDFpagedestination
\to \everyshipout

This was added because there was some not upward compatibility handling of 
page refs in acrobat 5 (simple pag enumber destinations worked ok <5, now 
it should be object numbers, for which we need some low level support in 
pdftex).

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  reply	other threads:[~2002-11-05  8:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02 20:33 Hans Hagen
2002-11-04  9:26 ` Jens-Uwe Morawski
2002-11-05  8:43   ` Hans Hagen [this message]
2002-11-05 17:47     ` Jens-Uwe Morawski
2002-11-06 10:11       ` Hans Hagen
2002-11-06 20:33         ` Willi Egger
2002-11-06 21:09         ` Jens-Uwe Morawski
2002-11-06 22:37           ` Jens-Uwe Morawski
2002-11-07  9:51           ` Hans Hagen
2002-11-07 20:09             ` Jens-Uwe Morawski
2002-11-07 21:28             ` Willi Egger
2002-11-08  8:27               ` Hans Hagen
2002-11-08 10:10                 ` Jens-Uwe Morawski
2002-11-08 16:09                   ` Hans Hagen
2002-11-11 14:17                 ` Rob van Swol

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=5.1.0.14.1.20021105094122.03654ea8@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ref.ntg.nl \
    --cc=ntg-context@ref.vet.uu.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).