ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Trouble with index
Date: Tue, 13 May 2008 08:45:14 +0200	[thread overview]
Message-ID: <115224fb0805122345u56f5234as6c51738c81c4823d@mail.gmail.com> (raw)
In-Reply-To: <20080510183600.57sb0te48w4sgsg4@w13.mail.sapo.pt>

On Sat, May 10, 2008 at 7:36 PM,  <cidadaum@sapo.pt> wrote:
>
> In the fileOn Wed, Apr 30, 2008 at 1:00 PM,  <cidadaum at sapo.pt> wrote:
> >
> > So far I have not succeded to make an index in a book I am typesetting.
> > I write something like:
> > \starttext
> > \defineregister[index][indices]
>
> Predefined, can be omitted.
>
> > \index[Tantrum]Tantrums can be normal for
>
> \index{Tantrum}
>
> > \index[tantrum][tantrum+toddlers]toddlers. Young children have them for
>
> \index{tantrum+toodlers}
>
> > many reasons like being tired, feeling out of control, over-stimulated,
> > or wanting something they can't have.
> > General hints: Toddlers and preschoolers cannot regulate themselves
> > because they don't yet know their own limits.
> > \completeindex
> > \stoptext
>
> Wolfgang
>
> I have made a file with this post and I have managed to do an index.
> But with another file I got this message:
> system          : index not found/processed
> ! Extra \endgroup.
> \doplaceregister ...packed \stopcolumns \endgroup
>                                                   \fi
> \docompleteregister ...ter [\currentregister ][#2]
>                                                   \page [\v!yes ]\endgroup \fi
> <to be read again>
>                    \par
> l.2984
>
> ?
> [42.42]
> ! Extra \endgroup.
> \docompleteregister ...2]\page [\v!yes ]\endgroup
>                                                   \fi
> <to be read again>
>                    \par
>
> Is there something wrong I am doing.
> At the beginning I put this:
> \defineregister[index][indices]

This did not harm but "\index" is already defined in core-reg.tex and you need
\defineregister only if you want to use more indices.

> and \completeindex at the end.

Make a example where we can reproduce the error.

> Armando

Wolfgang
___________________________________________________________________________________
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	other threads:[~2008-05-13  6:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10 17:36 cidadaum
2008-05-13  6:45 ` Wolfgang Schuster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-30 11:00 Trouble with Index cidadaum
2008-04-30 11:08 ` Wolfgang Schuster
2008-04-30 12:35   ` Thomas A. Schmitz
2008-05-01  2:22     ` cidadaum
2008-05-01  8:58       ` Wolfgang Schuster

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=115224fb0805122345u56f5234as6c51738c81c4823d@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.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).