From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: WolfgangZ <wollez@gmx.net>
Subject: Re: strange index behaviour with entries inside separatedlist
Date: Fri, 12 Apr 2013 14:07:26 +0200 [thread overview]
Message-ID: <5167F8FE.8030906@wxs.nl> (raw)
In-Reply-To: <kk8pek$uhs$1@ger.gmane.org>
On 4/12/2013 12:59 PM, WolfgangZ wrote:
> Am 12.04.2013 10:29, schrieb Wolfgang Schuster:
>>
>> Am 12.04.2013 um 08:10 schrieb WolfgangZ <wollez@gmx.net>:
>>
>>> Hello,
>>> I get wrong list entries when using my register entries inside
>>> separate lists. Example case included, even if it is a bit longer.
>>> For explanation, I have two lists, the correct index is in section
>>> 1.2 in the attached example and printed on page 3 (see test.pdf). The
>>> one that causes trouble is set in section 1.3 (green table) and
>>> printed on page 5. There the index links to page 4 instead of page 1,
>>> on which the entry is placed.
>>>
>>> The example gets more strange, as the wrong index entries only occurs
>>> if there is no regular text below the table in section 1.3. For
>>> testing you can uncomment line 70 in file test.tex.
>>
>> Put the text before the index entry in your definition in \Listwrong
>> the output is correct:
>>
>> \define[1]\Listwrong{#1\Wrongliste{#1}}
>>
>> Wolfgang
>
> Great, this solves the problem! Is it possible to explain the reason for
> the behavior of context to the order of the text entry and the command?
in order to track locations we need to inject a so called whatsit which
is an invivible but definitely present entity an din order to make this
work:
test
\index{xxx}
test
\index will bind to the next paragraph when it's a loner
otherwise we would get
test
<whitespace or at least valid breakpoint>
\index{xxx}
<whitespace or at least valid breakpoint>
test
which could show up as an unwanted extra whitespace and/or page break
with dislocated index entry
this kind of behaviour has always been part of context, as we want to be
able to do
\chapter{...}
\index{...}
\index{...}
\index{...}
\index{...}
\index{...}
some text ...
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:[~2013-04-12 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 6:10 WolfgangZ
2013-04-12 8:29 ` Wolfgang Schuster
2013-04-12 9:59 ` Hans Hagen
2013-04-12 10:59 ` WolfgangZ
2013-04-12 12:07 ` Hans Hagen [this message]
2013-04-15 6:54 ` Wolfgang
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=5167F8FE.8030906@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=wollez@gmx.net \
/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).