ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: Indexing
Date: Thu, 21 Feb 2002 10:33:47 +0100	[thread overview]
Message-ID: <20020221103347.5ee9536b.taco@elvenkind.com> (raw)
In-Reply-To: <02022212242401.27994@publish>

Hi John,

I know for a fact that Hans has been looking into xindy. IIRC,
makeindex just isn't powerful enough to be usable with Context,
and xindy was 'nearly there but not quite usable yet' (that was 
the situation about 2 years ago).

Context's registers pre-date xindy as well as the dos/win
port of makeindex by a couple of years, which is no doubt
the reason why Hans invented his own system.

The thing that is definately needed in a replacement program is 
the possibility to pass along 'piggyback' data together with the
actual index entry. Joachim was very understanding about that
request, but I don't know whether they did or did not implement
it in xindy (yet?).

Greetings, Taco

On Fri, 22 Feb 2002 12:24:24 -0500 "John Culleton" wrote:
> The indexing part of Context (called ``register'') seems to
> be limited in some respects when compared to makeindex and
> xindy. Has anyone tried to incorporate these other indexing 
> products in a Context document? 

-- 
groeten,

Taco


  reply	other threads:[~2002-02-21  9:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 17:24 Indexing John Culleton
2002-02-21  9:33 ` Taco Hoekwater [this message]
2002-02-22  0:22   ` Indexing John Culleton
2002-02-22  9:41     ` Indexing Taco Hoekwater
2002-02-22 11:38       ` Re[2]: Indexing Giuseppe Bilotta
2002-02-22 12:25         ` Taco Hoekwater
2002-02-22 13:37           ` Re[4]: Indexing Giuseppe Bilotta
2002-02-22 16:35             ` Taco Hoekwater
2002-02-25 14:00 ` Indexing Hans Hagen
2002-02-25 21:12   ` Indexing John Culleton
2002-02-26 10:01     ` Indexing Taco Hoekwater
2002-02-26 11:14     ` Indexing Hans Hagen

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=20020221103347.5ee9536b.taco@elvenkind.com \
    --to=taco@elvenkind.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).