From: Duncan Hothersall <dh@capdm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Fine tuning an index
Date: Thu, 8 Oct 2020 16:58:16 +0100 [thread overview]
Message-ID: <CAN8fp9XL7CCzCYcmz8Qdz8WdpDTsCWwWwd7c-ZvPFTH-_16pnQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1503 bytes --]
I'm doing my first mkiv index (it took me a long time to upgrade from
mkii!) and I really like the processor feature to format elements
differently. But there are a couple of things I would really like to
achieve that I'm struggling with:
1. Elided numbers in an index range entry. For example if I have a
\startregister - \stopregister pair resulting in an index entry like
entry 354--356
I would like to be able to make this read
entry 354--6
There are different conventions for number span elision but usually
teens aren't elided so
entry 314--316
would become
entry 314-16.
It strikes me that if I could set up a processor specifically for page
number ranges I could possibly write a macro to do elision; but I don't
think that's currently possible? Maybe it's possible in lua to write code
which both identifies range page numbers and carries out the elision. I'm
not quite sure where to start.
2. Fine tuning column and page breaking in an index. This is tricky,
because there are usually very few "good" places to break an index, and
automatic breaking seems to alter slightly depending on whether
interactions are set up or not, but is there a way to manually insert a
column or page break into the register before or after a certain entry, the
way there is for a table of contents?
Sorry for no MWE, for obvious reasons. Any pointers to what might be able
to be done on these would be much appreciated.
Thanks.
Duncan
[-- Attachment #1.2: Type: text/html, Size: 1916 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2020-10-08 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:58 Duncan Hothersall [this message]
2020-10-08 20:36 ` jbf
2020-10-09 6:25 ` Duncan Hothersall
2020-10-09 7:31 ` Duncan Hothersall
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=CAN8fp9XL7CCzCYcmz8Qdz8WdpDTsCWwWwd7c-ZvPFTH-_16pnQ@mail.gmail.com \
--to=dh@capdm.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).