From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: \index versus makeindex.
Date: Mon, 21 Jul 2008 08:16:04 +0200 [thread overview]
Message-ID: <115224fb0807202316r2de3d5c4ia8c1f85831c54b70@mail.gmail.com> (raw)
In-Reply-To: <200807181338.13462.john@wexfordpress.com>
On Fri, Jul 18, 2008 at 7:38 PM, John Culleton <john@wexfordpress.com> wrote:
> Usually I use makeindex for indexing but for my current job I thought
> the Context \index command would be convenient. However I discovered
> that the \index command does not provide for page ranges. If I index
> the same item on pages 46, 47, 48, and 49 makeindex will collapse
> this into a range of 46-49. Context won't.
>
> I looked at the book.tuo file but it does not look like something I
> can hand-modify.
>
> Is there a work-around I have missed or must I revert to makeindex to
> get a proper index?
>
> I am ccing Hans because my posts don't seem to make their way to the
> list for some reason. Perhaps Comcast has torpedoed me once again.
\placeindex[compress=yes]
Regards,
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-07-21 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 17:38 John Culleton
2008-07-21 6:16 ` Wolfgang Schuster [this message]
2008-07-23 12:50 ` John Culleton
2008-07-23 13:03 ` Wolfgang Schuster
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=115224fb0807202316r2de3d5c4ia8c1f85831c54b70@mail.gmail.com \
--to=schuster.wolfgang@googlemail.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).