From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: jbf <roma83537@gmail.com>
Cc: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>,
Adam Reviczky <reviczky@gmail.com>
Subject: Re: registers, how to ignore quote marks
Date: Sun, 30 Jan 2022 10:59:53 +0100 [thread overview]
Message-ID: <7eced3d3-604f-35f9-a85b-bef9e5345b47@xs4all.nl> (raw)
In-Reply-To: <5600368b-ae9c-c0be-f9d8-f2490ab1b3c1@gmail.com>
On 1/30/2022 1:30 AM, jbf wrote:
> The several responses to my floundering with the register have been very
> helpful, though I would have to confess that I have ended up 'messing
> with' things (suggested by Hans re the [key]) and getting a satisfactory
> result in almost every case without always understanding why. But I can
> say that I have the 'sorting' issue resolved if it is a main entry,
> including if that entry is surrounded by quote marks or has one part of
> that entry formatted differently (e.g. italics).
>
> But I don't seem able to apply this to subentries! I cannot solve the
> sorting of subentries that have special features (e.g. I might have
> needed italics for part of a subentry, or the subentry is surrounded by
> quote marks).
>
> Here are my two situations (and in each case they appear out of
> alphabetical order in the subentry list):
>
> 1. \index{animals+‘special kinds’}: in this case ‘special kinds’ appears
> in the subentry list at the bottom of the list, after one that starts
> with 'v'. I 'messed with' this by adding keys, e.g., \index[Animals]
> etc. but the item disappeared from the index altogether.
>
> 2. \index{Plenary Council+{\it periti} (experts)}: in this case it is
> the italicised /periti/ that appears out of place, after the letter 'i'
> rather than after 'p'. Again I tried putting various keys but this did
> not help.
>
> I guess my confusion is this: I assumed that the [key] establishes the
> literal string which determines sort order. That seems to be the case
> for a main entry. How do I get it to work for a subentry?
just provide an extra key:
key+subkey
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2022-01-30 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 5:23 jbf via ntg-context
2022-01-29 9:43 ` Henning Hraban Ramm via ntg-context
2022-01-29 10:02 ` jbf via ntg-context
2022-01-29 10:39 ` Hans Hagen via ntg-context
2022-01-30 0:30 ` jbf via ntg-context
2022-01-30 9:59 ` Hans Hagen via ntg-context [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-30 20:55 jbf via ntg-context
2022-01-29 2:40 jbf via ntg-context
2022-01-29 4:49 ` Adam Reviczky 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=7eced3d3-604f-35f9-a85b-bef9e5345b47@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=reviczky@gmail.com \
--cc=roma83537@gmail.com \
/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).