From: Duncan Hothersall <dh@capdm.com>
Subject: Re: Urgent index problem
Date: Tue, 29 Mar 2005 08:20:58 +0100 [thread overview]
Message-ID: <424901DA.6070400@capdm.com> (raw)
In-Reply-To: <20050328194852.C549A12863@ronja.ntg.nl>
I wrote:
> --
> \starttext
> \startregister[index]{this term+in+particular} This term is discussed
> from the start of this page.\page[yes]
> Some more text about the term, and another page.\page[yes]
> And the end of the info about that term. \stopregister[index]{this
> term+in+particular}\page[yes]
> A page unrelated to that term.\page[yes]
> \index{this term+in+particular} And then another page on exactly the
> same term.\page[yes]
> \placeindex\page[yes]
> Disaster! The entry on page 5 has been eaten!
> \stoptext
> --
I realise that there is a workaround for the sample above, using the
literal ASCII string in [] which makes this specific example work.
Unfortunately this doesn't make everything work correctly in a larger
document. I'm now seeing two other specific behaviours as well:
1. When there is a range and a single entry, the range is sometimes
listed first in the index, even if the single entry is many pages before
it - i.e. 282-283, 170
2. On other occasions where a range and a single entry exist, I end up
having a strange three-way range in the index - like 282-283-349. The
last reference should be just a single one on its own.
It's really difficult to post a minimal file for these because they only
occur when the whole text is processed (several hundred pages). I have
just synchronised my tree this morning and no difference is made.
Any help, especially today, VERY gratefully received.
Duncan
next parent reply other threads:[~2005-03-29 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050328194852.C549A12863@ronja.ntg.nl>
2005-03-29 7:20 ` Duncan Hothersall [this message]
2005-03-28 16:20 Duncan Hothersall
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=424901DA.6070400@capdm.com \
--to=dh@capdm.com \
--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).