From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Hans Hagen: "an index entry needs an anchor" (Mail Archive 3/19/2014)
Date: Fri, 14 Nov 2014 11:54:18 +0100 [thread overview]
Message-ID: <5465DF5A.6000806@wxs.nl> (raw)
In-Reply-To: <20141114092402.GA22219@nan>
On 11/14/2014 10:24 AM, Rudolf Bahr wrote:
> Hi,
>
> LaTeX "index" command doesn't need an anchor in order to print the page number.
>
> Sometimes you can't give the ConTeXt-Command "index" any anchor. Think of an
> external figure on a page and nothing else, without any text. When I say, for instance:
>
> \index{Brigitte Bardot}\strut
>
> I get a correct index, but an unsolicited extra empty page, too. What could be a solution?
> My ConTeXt version is: "ConTeXt ver: 2014.11.12 21:46 MKIV beta fmt: 2014.11.14"
i'm pretty sure that any index mechanism that is supposed to provide the
right page does a delayed write, so some kind of anchoring is there
(you could try \index{...}\null or maybe \setregisterentry)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-11-14 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 9:24 Rudolf Bahr
2014-11-14 10:54 ` Hans Hagen [this message]
2014-11-15 8:59 ` Rudolf Bahr
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=5465DF5A.6000806@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).