On 4/10/2014 2:31 PM, jahei...@gmx.de wrote:
Try 1:
\starttext
\section{Hello}\index{Hello}
\page
\index{world}world
\page
\completeindex
\stoptext
Result 1:
hello 2 - must be 1!
world 2
Try 2:
\starttext
\section{Hello}\index{Hello}
some text - putting some text here
\page
\index{world}world
\page
\completeindex
\stoptext
Result 2:
hello 1 - ok
world 2
It is ok but I didn't want to put text some text there.
Try 3:
Workaround: I put a tilde ~ instead of some text:
\starttext
\section{Hello}\index{Hello}
~ - putting the tilde here
\page
\index{world}world
\page
\completeindex
\stoptext
Result 3:
hello 1 - ok, with the tilde as a workaround
world 2
I don't like such tricks - is there a ConTeXt-way?
An index is bound to something, in most cases the next node (often a
character) ... just try to imagine what happens when it it not bound:
text
index entry node
text
Where do you expect a page break? And how robust can that be
implemented? Normally you woudl expect the index to be bound to the
second text (think of broken lines/words). So .. the index commands
tries to bind to the following text.
\showstruts
\index{x}\strut
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
___
