ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: "see also"
Date: Sun, 7 Sep 2025 08:47:52 -0400	[thread overview]
Message-ID: <70797926-a71b-4379-859e-ba727f1b047a@rik.users.panix.com> (raw)
In-Reply-To: <ddaefa4b-9338-4b2e-8fca-86a9517f2cee@fiee.net>


[-- Attachment #1.1: Type: text/plain, Size: 2001 bytes --]


On 2025-09-07 06:50, Henning Hraban Ramm wrote:
> Hi,
> for cross references in an index, I can use \seeindex{cow}{cattle}.
> That gives an index entry "cow see cattle" if I never used 
> \index{cow}, otherwise "cow 123, see cattle".
>
> In these cases, I’d prefer "cow 123, see _also_ cattle".
> How can I do that?
>
> Hraban
>
I have a convoluted way of doing it.

First, I define a topic index and a parallel topic seeindex which 
gobbles the page number:

    \defineregister[Tindex]
    \setupregister [Tindex][n=2,
                             command={\Word},
                             balance=no,
                             method=default, % or New follows Newton!
                             compress=yes,
                             check=no,% allows seeindex to plussed entries
                             expansion=yes,
                             pagecommand=\IndexPageCommand,
                           ]
    \defineregister[SeeTindex]% see also index for Topics
    \setupregister [SeeTindex][n=2,
                                command=,
                                balance=no,
                                method=default, % or New follows Newton!
                                compress=,
                                maxwidth=2.3in,
                                expansion=yes,
                                pagecommand=\gobbleoneargument,
                              ]

Then I can index normally

         \TIndex{quotation+direct}%
         \TIndex{quotation+indirect}%
         \TIndex{marking}%

except for the see also entry, which requires:

      \setregisterentry[SeeTindex][keys:2=zzz,entries:1=punctuation,entries:2={{\em
    See also} marking}]%

and then I can get

-- 
Rik

[-- Attachment #1.2.1: Type: text/html, Size: 3019 bytes --]

[-- Attachment #1.2.2: O0nH5Z4JMMSivDRQ.png --]
[-- Type: image/png, Size: 11151 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2025-09-07 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 10:50 [NTG-context] "see also" Henning Hraban Ramm
2025-09-07 11:27 ` [NTG-context] " Mikael Sundqvist
2025-09-07 11:36   ` Henning Hraban Ramm
2025-09-07 12:47 ` Rik Kabel [this message]
2025-09-07 16:36   ` Henning Hraban Ramm
2025-09-11 13:47     ` Henning Hraban Ramm

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=70797926-a71b-4379-859e-ba727f1b047a@rik.users.panix.com \
    --to=context@rik.users.panix.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).