ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Get rid of LuaTeX warning on duplicate destination identifier
Date: Thu, 29 Aug 2013 10:15:48 +0200	[thread overview]
Message-ID: <521F0334.3090607@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.03.1308282138270.11258@hzvpu.rqh>

On 8/29/2013 4:06 AM, Aditya Mahajan wrote:
> Hi,
>
> I am trying to pick up on an old thread of creating an overview page
> [1]. Basically, the idea is to create an overvew slide at the end of a
> presentation that shows the first page of different sections in a
> presentation. Based on Wolfgang's answer in that old thread, I save the
> relevant pages in a box, and then display them again at the end of the
> presentation.
>
> This works, except that I get a series of warnings:
>
> l.86 \placeoverviewpage
>                       LuaTeX warning (ext4): destination with the same
> identifier (name{aut:10}) has been already used, duplicate ignored
>
> How do I get rid of these?

Tricky. The problem is that you flush a box (copy) so the message comes 
from deep inside the backend (for good reason) and so we cannot 
intercept it as "hey user, you use the same dest twice" simply because 
it's a copy and not re-rendered.

There are two solutions:

(1) strip the box before copying (i can make a helper for that - later 
as i have to go now): destinations, references, writes-to-lists etc

(2) you copy the old file before processing and use that one

  \def\placeoverviewpage
    {\startstandardmakeup[\c!align=\v!middle]
        \getfiguredimensions[temp.pdf]%
 
\dorecurse{\noffigurepages}{\externalfigure[temp.pdf][\c!page=##1,\c!width=\overviewwidth]\relax\space}
     \stopstandardmakeup}

> I am afraid that I cannot create a small example illustrating this
> warning, so I am attaching the complete test file.
>
> [1]: http://thread.gmane.org/gmane.comp.tex.context/72556/focus=72571

[2] It has always been a wish of mine to have it as option in the engine 
(pdfetex) but in luatex it's not that hard to do it myself now (i 
already have a stripper so I can extend that one a bit).

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2013-08-29  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  2:06 Aditya Mahajan
2013-08-29  8:15 ` Hans Hagen [this message]
2013-08-29 18:53   ` Hans Hagen
2013-08-31 15:36     ` Aditya Mahajan
2013-08-31 21:42       ` Hans Hagen

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=521F0334.3090607@wxs.nl \
    --to=pragma@wxs.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).