ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \seeindex
Date: Tue, 5 Oct 2010 17:17:11 +0200	[thread overview]
Message-ID: <201010051717.11356.alan.braslau@cea.fr> (raw)

Wishlist: add interaction to \seeindex


Explaination:

\seeindex{index_entry}{see_entry}
can be used to add entry to an index
that refers one to another entry.
Example: \seeindex{DNA}{deoxyribonucleic acid}

With \setupinteraction [state=start]
one gets active hyperlinks on the page numbers
of the index entries.
It would be nice if \seeindex entries to
the index would create an interaction hyperlink
to the corresponding real index entry.

This is pretty straight-forward, but probably
non-trivial to implement, as there is no guarantee
that the second entry of \seeindex indeed exists.
Of course, \seeindex could create this entry,
but it may not have an associated page number
or page numbers if \index{deoxyribonucleic acid}
was never called.

Even more sophisticated, but the bookkeeping on this
might get a bit complicated, \index{DNA} could
create an index entry under {deoxyribonucleic acid}
as \seeindex instructs to "hijack" this label.

(currently, it will put "see DNA" followed by a page number.)

Alan
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2010-10-05 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 15:17 Alan BRASLAU [this message]
2010-10-07  8:50 ` \seeindex 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=201010051717.11356.alan.braslau@cea.fr \
    --to=alan.braslau@cea.fr \
    --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).