From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Sorting of abbreviations in index
Date: Fri, 6 Oct 2017 17:13:11 +0200 [thread overview]
Message-ID: <DD27277C-0566-4259-A567-44C3CEE1A88D@fiee.net> (raw)
In-Reply-To: <5ADE7C33-A542-4ED2-9F93-C2FA68ABD73E@fiee.net>
Sorry to insist, but this bug is blocking the publication of our latest book:
\def\Some#1{#1}
\def\Sindex#1{\index{\Some{#1}}#1}
\starttext
\index{Tufte}\index{Knuth}\index{Zapf}
\index{Sole}\index{Some}\index{Sone}
\input tufte \Sindex{Tufte}
\input knuth \Sindex{Knuth}
\input zapf \Sindex{Zapf}
\placeindex
\stoptext
The generated index sorts everything that is indexed via \Sindex{} after "Some".
In the book, I’m using ConTeXt’s abbreviations (synonyms) mechanism and resolve them with \infull, so that all the organizations are sorted after "infull".
I don’t understand what’s going on in strc-reg.mkiv or strc-reg.lua, but I guess the problem might be in local function filtercollected - or does some interpolation take place within \index (\register[something]) itself?
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
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:[~2017-10-06 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 10:40 abbreviations: \infull always in small caps Henning Hraban Ramm
2017-09-23 19:28 ` Thomas A. Schmitz
2017-09-23 22:12 ` Henning Hraban Ramm
2017-09-23 22:45 ` Sorting of abbreviations in index Henning Hraban Ramm
2017-09-25 17:50 ` Henning Hraban Ramm
2017-10-01 13:31 ` Henning Hraban Ramm
2017-10-06 15:13 ` Henning Hraban Ramm [this message]
2017-10-09 10:42 ` Jano Kula
2017-10-09 15:35 ` Henning Hraban Ramm
2017-10-09 16:55 ` Jano Kula
2017-10-09 17:03 ` Floris van Manen
2017-09-23 22:46 ` abbreviations: \infull always in small caps 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=DD27277C-0566-4259-A567-44C3CEE1A88D@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).