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: Fri, 22 Feb 2002 10:41:22 +0100	[thread overview]
Message-ID: <20020222104122.38736dc9.taco@elvenkind.com> (raw)
In-Reply-To: <02022119225801.01387@publish>

On Thu, 21 Feb 2002 19:22:58 -0500
"John Culleton" <john@wexfordpress.com> wrote:

> I recognize that makeindex lacks the hyperref features that may be 
> useful
> for online documents, as well as the extensions that Xindy hopes to
> bring to the indexing process. But it suits my needs. So can I 
> include eplain.tex and use its indexing commands without messing 
> something
> else up? AFAIK its macros (\idx, \sidx etc.) do not have name 
> conflicts with the corresponding ConText commands.

At least the indexing part should be safe. I'm not sure about the
rest eplain. It *used to* work but that was a very long time ago.
You 'll just have to try and see. 

I used to have a small set of indexing macros for plain, these
probably would also work. Most plain macro packages work out of the 
box, or with only trivial changes.

The thing is: I like the ConTeXt registers a lot. I don't want
to go back to makeindex anymore (even though getting the sort order
right in texutil can be a pain). 

-- 
groeten,

Taco


  reply	other threads:[~2002-02-22  9:41 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 ` Indexing Taco Hoekwater
2002-02-22  0:22   ` Indexing John Culleton
2002-02-22  9:41     ` Taco Hoekwater [this message]
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=20020222104122.38736dc9.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).