From: Duncan Hothersall <dh@capdm.com>
Subject: Re: index page range bug
Date: Thu, 07 Sep 2006 10:18:00 +0100 [thread overview]
Message-ID: <44FFE3C8.3060303@capdm.com> (raw)
In-Reply-To: <mailman.680.1157523489.2039.ntg-context@ntg.nl>
Jason wrote:
> When using startregister/stopregister commands, if the range is only one
> one page, then while both a [f] and a [t] are written to the tui file,
> only one \registerfrom command is put in the tuo file. If there is only
> one range, it seems like the software deals with it nicely. However, if
> there are two ranges (like in the example below), then the index
> incorrectly assumes that the first \registerfrom command in the tuo file
> corresponds to the \registerto command.
Aha! Great work tracking this down Jason, I have been bitten by this bug
many times in the past but not been able to isolate it. It would be
really great if this could be fixed in the ruby script.
Duncan
next parent reply other threads:[~2006-09-07 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.680.1157523489.2039.ntg-context@ntg.nl>
2006-09-07 9:18 ` Duncan Hothersall [this message]
2006-09-06 0:12 Jason Grout
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=44FFE3C8.3060303@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).