From: Alan BRASLAU <alan.braslau@cea.fr>
To: ntg-context@ntg.nl
Subject: Re: \index{…} causes space
Date: Sat, 25 Dec 2010 11:18:35 +0100 [thread overview]
Message-ID: <201012251118.35540.alan.braslau@cea.fr> (raw)
In-Reply-To: <E2B0D092-2B77-423E-A7BC-6EF9FC9B3D00@uni-koblenz.de>
On Friday 24 December 2010 12:57:26 Andreas Harder wrote:
> Am 24.12.2010 um 12:53 schrieb Alan BRASLAU:
> > On Friday 24 December 2010 11:54:17 Taco Hoekwater wrote:
> >>> On 12/24/2010 11:48 AM, Andreas Harder wrote:
> >>> \index{test}test
> >>
> >> \ignorespaces could be possibly be added to \index in your case,
> >> but that does not solve this conceptual problem: what is actually
> >> being indexed in that second line? Not the word on the left
> >> (as that could be on a different page), neither the word on the
> >> right (as that could also be on a different page).
> >
> > I have understood that the correct use of \index{}
> >
> > is immediately following the word to be indexed, as in:
> > test\index{test}
>
> The wiki (http://wiki.contextgarden.net/Registers#Example) suggests it the
> other way round …?
>
I don't know about the wiki. Maybe it is correct, maybe not.
I suppose that I should be able to figure this out looking at the source code.
As Taco points out (see below):
test \index{test}
is no good, as the page can possibly be broken before the index entry;
\index{test}test
is no good either, as "test" may appear on the page following the index entry.
I had always understood the correct usage to be:
test\index{test}
On Friday 24 December 2010 11:54:17 Taco Hoekwater wrote:
> On 12/24/2010 11:48 AM, Andreas Harder wrote:
> > \startTEXpage[offset=1ex]
> > test test\vl \crlf
> > test \index{test}test\vl \crlf % OK
> > test \index{test} test\vl % not OK
> > \stopTEXpage
>
> \ignorespaces could be possibly be added to \index in your case,
> but that does not solve this conceptual problem: what is actually
> being indexed in that second line? Not the word on the left
> (as that could be on a different page), neither the word on the
> right (as that could also be on a different page).
>
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-12-25 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 10:48 Andreas Harder
2010-12-24 10:54 ` Taco Hoekwater
2010-12-24 11:53 ` Alan BRASLAU
2010-12-24 11:57 ` Andreas Harder
2010-12-25 10:18 ` Alan BRASLAU [this message]
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=201012251118.35540.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--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).