On Monday 21 July 2008 02:16:04 am Wolfgang Schuster wrote:
> On Fri, Jul 18, 2008 at 7:38 PM, John Culleton 
<[EMAIL PROTECTED]> 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

your suggestion to use compress=yes works well.  Thanks. Such 
compression is essential in many works. Now I wonder if there is a 
Context command like eplain's range commands which occur in pairs:
\sidx[begin]{foo}
...
\sidx[end]{foo}

The same effect in LaTeX is a bit more cryptic:
\index{foo|(}
...
\index{foo|)}

Either form includes all the pages between the two commands as entries 
under foo, e.g.,
foo 24-68

This facility may exist but the Context manual is a bit hard to follow 
on indexing. 

-- 
John Culleton
Resources for every author and publisher:
http://wexfordpress.com/tex/shortlist.pdf
http://wexfordpress.com/tex/packagers.pdf
http://www.creativemindspress.com/newbiefaq.htm
http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm
___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to