ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Culleton <john@wexfordpress.com>
Subject: Re: Indexing macros
Date: Tue, 3 Dec 2002 13:33:47 +0000	[thread overview]
Message-ID: <200212031333.47102.john@wexfordpress.com> (raw)
In-Reply-To: <20021202174112.58784a93.taco@elvenkind.com>

On Monday 02 December 2002 16:41, Taco Hoekwater wrote:
> On Mon, 2 Dec 2002 16:20:52 +0000, John wrote:
> > The "register" macros in Context only provide for a single level
> > index AFAIK so I have been looking at the use of either makeindex
> > or Xindy in a Context project. I have slightly modified the
> > index.tex file
>
> Unless I misunderstand your intentions, you were looking this ConTeXt
> command:
>
> \index{main+sub+subsub}
Thanks for your correction! It is even in the manual :-] But there are
other features found in Makeindex and especially Xindy that are
useful. For example attributes attached to the page reference # can be
passed through the system. An entry, subentry etc. can be sorted out
of order. This also handles elegantly the situation where one needs to
put a font change in with the item, e.g.:
\index{sortitem@\it Sortitem\rm}

The Context manual mentions the "see" form of entry but not
the "see also" form, although there is passing reference to another
form (not described fully) that allows one to input a "pure ASCII
string." 

Makeindex will automatically collapse a page reference string. If
three or more successive pages have the identical index item then
"1,2,3" becomes "1-3" etc. Perhaps Context does this also.

Xindy will handle appendix references like "A-3" although these are
becoming rarer.

Both Makeindex and Xindy have style files that allow for customizing
of the output. For example the letter headers might be centered in the
column, or left justified, in bold or not, capital or lower case,
surrounded by em dashes etc. 

Xindy goes well beyond this, allowing for special headers for e.g.
Hungarian which has the letter combination Ly sorted separately. 

Perhaps as is so often the case, the features are there but not yet
described in Context. A Context-only solution would be nice, but in
the meantime the power of the existing packages are available. 
-- 
John Culleton
Able Indexers and Typesetters 
Rowse Reviews
Culleton Editorial Services
http://wexfordpress.com

  reply	other threads:[~2002-12-03 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 16:20 John Culleton
2002-12-02 16:41 ` Taco Hoekwater
2002-12-03 13:33   ` John Culleton [this message]
2002-12-03 16:57     ` Hans Hagen
2002-12-03 16:59     ` Hans Hagen
2002-12-04 14:30     ` Gour
2002-12-02 16:51 ` Hans Hagen
2002-12-03 14:18   ` John Culleton
2008-09-11 20:58 width of cell in TABLE Peter Münster
2008-09-12  8:27 ` span ROWS in \starttables? Alan BRASLAU
2008-09-12 13:37   ` Aditya Mahajan
2008-09-15 12:49     ` Indexing macros Alan BRASLAU

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=200212031333.47102.john@wexfordpress.com \
    --to=john@wexfordpress.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).