From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: latest beta and \seeindex
Date: Mon, 25 Jun 2018 14:22:32 +0200 [thread overview]
Message-ID: <62831C81-2E85-426F-AF45-DAB992CC44B9@fiee.net> (raw)
In-Reply-To: <dae2b336-9b1d-4ad4-5895-ae1f2b062110@xs4all.nl>
Am 2018-06-25 um 14:15 schrieb Hans Hagen <j.hagen@xs4all.nl>:
> On 6/24/2018 10:07 PM, Henning Hraban Ramm wrote:
>> Am 2018-06-24 um 21:57 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>>> as there is no index entry blah, humbug or bug ... so you would be fooling your reader
>> I understand the rationale, and it could be a nice feature, but we need to refer to entries in a different register, e.g. from an index of topics to an index of persons, e.g. \seeindex{Pragma}{Hagen, Hans} or to subentries like \seeindex{fun+games}{bah+humbug}. Since the latter doesn’t work (or does it now?), we use \seeindex{fun+games}{bah/humbug}.
> hm, sounds like a crappy index to mee (i actually hate these indexes that force you to 'see' somplace else .. extra lookup)
I hear you, but it wouldn’t make sense to double-index a lot of terms (it might increase usability, but also double the length of the index).
> anyway, i'll add check=no to placeregister so that one can bypass the check (but i cannot foresee side effects like missing references in interactiev documents so these have to be taken for granted)
Thank you, that fits my/our needs, I guess.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-06-25 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 15:10 Alan Bowen
2018-06-24 19:57 ` Hans Hagen
2018-06-24 20:07 ` Henning Hraban Ramm
2018-06-25 11:21 ` Alan Bowen
2018-06-25 14:43 ` Alan Braslau
2018-06-25 12:15 ` Hans Hagen
2018-06-25 12:22 ` Henning Hraban Ramm [this message]
2018-06-25 12:18 ` Hans Hagen
2018-06-25 14:01 ` Henning Hraban Ramm
2018-06-25 15:08 ` Hans Hagen
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=62831C81-2E85-426F-AF45-DAB992CC44B9@fiee.net \
--to=texml@fiee.net \
--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).