From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: bug in \seeindex
Date: Wed, 28 Sep 2005 09:01:51 +0200 [thread overview]
Message-ID: <E7A21E9C-4BF7-4A12-A6F2-0BCB5A442E3E@uni-bonn.de> (raw)
In-Reply-To: <44D4D34B-589B-44B9-A99C-224268C1FEB7@uni-bonn.de>
And I don't have a solution, but another bug in registers: if you
modify my example like so:
\starttext
This \index{This} and \index{And} that \index{That}.
\placeindex
\stoptext
you'll see one interesting detail in the pdf: This and That are in
the index under "h," And under "n" ==> capital letters are not taken
into account in index generation, which is a trifle inconvenient.
Best
Thomas
On Sep 27, 2005, at 11:58 PM, Thomas A. Schmitz wrote:
> The code in \seeindex has a bug. There was something in the mailing
> list about a year ago (2004-06-21), but as far as I can see, the
> patch Hans proposed then has been integrated into core-reg.tex.
> Here's a minimal test file:
>
> \starttext
>
> This \index{this} and \index{and} that \seeindex{this}.
>
> \placeindex
>
> \stoptext
>
> And the error log:
>
> ! Argument of \@@filterlevelpart has an extra }.
> <inserted text>
> \par
> <to be read again>
> }
> \doifprevlevelelse ...tor \@@filterlevelpart [#1]}
> \edef
> \@@tocsectiontype {\...
>
> \dosetpageregisterpage ...->\doifreglevelelse [#5]
>
> {\dodosetpageregisterpage ...
> l.46 ...isterpage{index}{,}{3}{2::0:0:0:0:0:0:0}{}
>
> Unfortunately, the bug messes up the .tui file, so even if you
> delete the \seeindex command, the file will not compile unless you
> delete the .tui manually. Ideas, anybody?
>
> Best
>
> Thomas
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-09-28 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 21:58 Thomas A. Schmitz
2005-09-28 7:01 ` Thomas A. Schmitz [this message]
2005-09-28 7:40 ` luigi.scarso
2005-09-28 7:51 ` Thomas A. Schmitz
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=E7A21E9C-4BF7-4A12-A6F2-0BCB5A442E3E@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).