ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: strange index behaviour with entries inside separatedlist
Date: Fri, 12 Apr 2013 11:59:56 +0200	[thread overview]
Message-ID: <5167DB1C.9080406@wxs.nl> (raw)
In-Reply-To: <5E2F8B83-6512-4582-9785-332E9FA092D6@gmail.com>

On 4/12/2013 10:29 AM, Wolfgang Schuster wrote:
>
> 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}}

indeed .. an entry needs to be bound to something and when in vmode it 
gets bound to the next paragraph (otherwise we get weird spacing 
interference) .. one of these tex-chicken-egg issues

wolfgangs solution is the most efficient and definitely the way to do in 
when wrapping in macros

in this case, the flush is delayed to the next valid paragraph ... 
anyway, i sort of fixed it for tables .. at some point i will revise the 
whole binding issue (but it's somewhat tricky as lots of mechanisms then 
need testing)

in the next beta this works :

\setupinteraction[state=start]

\starttext

     \bTABLE \bTR \bTD \index{test 1} entry 1 \eTD \eTR \eTABLE \page
     \bTABLE \bTR \bTD \index{test 2} entry 2 \eTD \eTR \eTABLE \page

     \placeregister[index][n=1]

\stoptext


-----------------------------------------------------------------
                                           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-04-12  9:59 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 [this message]
2013-04-12 10:59   ` WolfgangZ
2013-04-12 12:07     ` Hans Hagen
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=5167DB1C.9080406@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).