ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Joel via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: [NTG-context] Is there a way to centrally add a list of indexed items to a sub category?
Date: Mon, 15 May 2023 08:18:45 +0200	[thread overview]
Message-ID: <8c8a6f0b-9d9e-eb3f-0ae8-5f46f87fdb78@fiee.net> (raw)
In-Reply-To: <2106398154.1236276.1684114673761@mail.yahoo.com>

Am 15.05.23 um 03:37 schrieb Joel via ntg-context:
> 
> I have a document like this:
> 
>      \starttext
>          \index{dogs}
> 
>          \index{cats}
> 
>          \index{flowers}
> 
>          \index{snails}
> 
>          \index{trees}
> 
>          \placeindex
> 
>      \stoptext
> 
> As I understand, if you use \index{animals+dogs}, it will place dogs as 
> a sub-category of dogs.
> 
> Is there any way to control this centrally, for instance:
> 
> \addtosub[animals]{dogs, cats, snails}
> \addtosub[plants]{flowers, trees}
> 
> Such a way would make it so \index{dogs} places an entry for "dog" under 
> "d" and "animals --> dogs" under "a".

I’d suggest to cook your own macro, e.g. for a book with a lot of person 
index entries, I used a lookup table to unify different spellings or 
name changes (married, titles etc.) like this:

"""% environment:
\loadluafile[lookups] % Index lookups

\defineregister[Person][]
\defineprocessor[italics][style=italicface]
\define[1]\Passim{\emph{passim}}
\defineprocessor[passim][command=\Passim]

\define[1]\nPerson{%
   \expanded{\Person{\ctxlua{userdata.Lookup("#1")}}}%
}

\define[1]\TPerson{%
   \expanded{\Person[kursiv->]{\ctxlua{userdata.Lookup("#1")}}}%
}#1}
\define[1]\nCPerson{\expanded{\Person[italics->]{\ctxlua{userdata.Lookup("#1")}}}}%
\define[1]\TCPerson{\expanded{\Person[italics->]{\ctxlua{userdata.Lookup("#1")}}}#1}%
"""

"""lookups.lua:
userdata = userdata or { }

userdata.Lookups = {
…
   ["Pauline, geb. Fichtner Erdmannsdörfer"] = "Erdmannsdörfer, Pauline, 
geb. Fichtner",
   ["Pauline Erdmannsdörfer"] = "Erdmannsdörfer, Pauline, geb. Fichtner",
   ["Pauline Erdmannsdörfer-Fichtner"] = "Erdmannsdörfer, Pauline, geb. 
Fichtner",
…
}

function userdata.Lookup(name)
    context(userdata.Lookups[name] or name)
end
"""

In a similar way you could setup an \Animal macro to use a lookup table 
how the entry should get indexed.

Hraban


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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-05-15  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2106398154.1236276.1684114673761.ref@mail.yahoo.com>
2023-05-15  1:37 ` Joel via ntg-context
2023-05-15  6:18   ` Henning Hraban Ramm via ntg-context [this message]
2023-05-15  7:40   ` Hans Hagen via ntg-context
2023-05-15 16:18     ` Alan Braslau via ntg-context
2023-05-15 22:12   ` Alan Braslau via ntg-context

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=8c8a6f0b-9d9e-eb3f-0ae8-5f46f87fdb78@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).