From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: trouble with indices
Date: Sun, 17 Feb 2008 20:39:02 +0100 [thread overview]
Message-ID: <20080217203902.13bba99c.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <m2skzrv1pl.fsf@DNab422469.Stanford.EDU>
On Sun, 17 Feb 2008 11:10:14 -0800
Jesse Alama <alama@stanford.edu> wrote:
> I've noticed that with the most recent ConTeXt release I'm unable to
> make indices. This example fails:
>
> \starttext
> Hello, this \index{copula}is an index.
> \completeindex
> \stoptext
Add the following path for the moment to your document.
\unprotect
\def\doplaceregister[#1][#2]%
{\iffirstargument
\begingroup
\edef\currentregister{#1}%
\setupregister[\currentregister][#2]%
\doifelse{\registerparameter\c!compress}\v!yes % new
{\chardef\collapseregisterpages\plusone}
{\chardef\collapseregisterpages\zerocount}%
% TH: disable next line
% \raggedright
% /TH
\startcolumns
[\c!n=\registerparameter\c!n,
\c!balance=\registerparameter\c!balance,
\c!align=\registerparameter\c!align,
tolerance=stretch]%
\dontcomplain
\startpacked[\v!blank]%
\mkloadregister\currentregister\dobeforeplaceregister\doafterplaceregister
\stoppacked
\stopcolumns
\endgroup
\fi}
\protect
> The error arises both with pdftex or xetex. I think that some recent
> change must be responsible for this, because I didn't notice any
> problems with indices, say, a couple months ago. What might be going
> on?
The values for the second and third argument for \mkloaddregister got lost
in the last beta, the responsible person could be found in the macro above ;-)
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-02-17 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 19:10 Jesse Alama
2008-02-17 19:39 ` Wolfgang Schuster [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=20080217203902.13bba99c.schuster.wolfgang@googlemail.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).