ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: \index or \register
Date: Mon, 15 May 2000 09:28:47 +0200	[thread overview]
Message-ID: <3.0.6.32.20000515092847.019be880@pop.wxs.nl> (raw)
In-Reply-To: <391D3D60.36D18511@gmx.net>

At 01:32 PM 5/13/2000 +0200, Hraban wrote:

>- Is there a significant difference in ConTeXt between \index and
>\register ?

There is no \register. You can say: 

  \defineregister [whatever] [whatevers] 

and use 

  \whatever{entry} 

afterwards. So, \index is a predefined \defineregister [index] [indices]

>- Is there a equivalent to LaTeX's
>  \index{something|(} (much text) \index{something|)}
>  that produces index entries for the whole range of text between the
brackets

Maybe you mean: 

\startindex{something} much text \stopindex{something} ? 

So, you may try: 

\starttekst

test \startregister[index][oeps]{oeps}Some pretty long
text\stopregister[index][oeps] test

\plaatsregister[index]

\stoptekst

>- Is ConTeXt \seeregister equivalent to LaTeX
>\index{something|see{that}} ?
>  Which text must/may go in which bracket of \seeregister[1]{2}{3}?

\seeindex{something}{that}
\seeregister[index]{something}{that}

>- Is there a macro for several index entries at once? (In LaTeX there isn't)
>  e.g. \register{one;two;three}

It would make \index pretty complicated. There is however a system of
tagged index entries (for special typesetting); see beta manual. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


      parent reply	other threads:[~2000-05-15  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13 11:32 Hraban
2000-05-13 15:48 ` Tobias Burnus
2000-05-15  7:28 ` Hans Hagen [this message]

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=3.0.6.32.20000515092847.019be880@pop.wxs.nl \
    --to=pragma@wxs.nl \
    --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).