From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: Fundamental change in index mechanism ?
Date: Sun, 22 Oct 2006 19:31:31 +0200 [thread overview]
Message-ID: <D4645686-417A-4BAE-9553-9296B9618DDD@st.estfiles.de> (raw)
In-Reply-To: <453B56EB.7070201@elvenkind.com>
Am 22.10.2006 um 13:32 schrieb Taco Hoekwater:
> Steffen Wolfrum wrote:
>> Hi,
>>
>> because of a second edition I had to typeset a project from august
>> 2006 a second time (with very, very little text changes).
>>
>> Then, I experienced that the register had changed (a simple \index
>> [keyword] and \placeregister[index]).
>> And with a closer look I saw that in the first edition the index
>> entries also get listed in the index register when appearing also in
>> the TOC content! Now, it was impossible for me to reproduce this: The
>> first listed entries now came from the beginning of the actual text.
>>
>> Is this a know bug? (Is there already a fix for it?)
>
> IMO, the current behaviour (as I understand it) is a bugfix for the
> known bug of pointlessly indexing a lookup table.
>
> Ask yourself: why would anyone want to be pointed to the table of
> contents from within the register?
>
> Taco
Sure, you are absolutely right (it was not my decision to typeset the
first edition the way it actually was set).
As far as I could see – apart from temporary workarounds (I remember
troubles with columns) – all old ConTeXt files generate the same
output when typeset with a current ConTeXt version.
So I was just wondering that my 3 month old file generates a
different output today.
Steffen
next prev parent reply other threads:[~2006-10-22 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 9:06 Steffen Wolfrum
2006-10-22 11:32 ` Taco Hoekwater
2006-10-22 17:31 ` Steffen Wolfrum [this message]
2006-10-22 11:53 ` Hans Hagen
2006-10-22 13:05 ` Steffen Wolfrum
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=D4645686-417A-4BAE-9553-9296B9618DDD@st.estfiles.de \
--to=context@st.estfiles.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).