From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: [Index] Indenting long primaries after secondaries
Date: Sun, 16 Mar 2014 16:34:40 +0100 [thread overview]
Message-ID: <9207.12295123867$1394984101@news.gmane.org> (raw)
In-Reply-To: <5325A8BB.4090104@wxs.nl>
On 2014-03-16 Hans Hagen wrote:
> On 3/7/2014 6:54 PM, Jan Tosovsky wrote:
> > On 2014-02-26 Jan Tosovsky wrote:
> >>
> >> when a long primary is preceded with the secondary or tertiary
> >> index entry, the second line is not indented as usual, see
> >> the following example:
> >>
> >> \setupregister[balance=no]
> >> \starttext
> >> \index{primary+secondary+tertiary}
> >> \index[primary long]{\dorecurse{5}{primary long }}
> >> \index[primary longer]{\dorecurse{5}{primary longer }} % Ok
> >> \input{tufte}
> >> \completeindex
> >> \stoptext
> >>
>
> how is a \dorecurse supposed to get sorted ...
>
That \dorecurse is used in this MWE only to make it shorter. Indeed, this
command confuses the letter grouping procedure so this is the reason why I
specified the sorting key via the bracket syntax [].
I think there is no need to fix this grouping issue (not enough ROI), but if
so, I would expect to resolve the \dorecurse command first and then apply
the grouping/sorting etc.
My main wish is fixing that indentation (or offering any workaround).
Thanks, Jan
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-03-16 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <019201cf331d$8bf5be80$a3e13b80$@tosovsky@email.cz>
2014-03-07 17:54 ` Jan Tosovsky
[not found] ` <00f801cf3a2e$4f722120$ee566360$@tosovsky@email.cz>
2014-03-16 13:35 ` Hans Hagen
2014-03-16 15:34 ` Jan Tosovsky [this message]
[not found] ` <003001cf412d$3f2692a0$bd73b7e0$@tosovsky@email.cz>
2014-03-16 16:09 ` Hans Hagen
2014-03-16 17:31 ` Jan Tosovsky
[not found] ` <003b01cf413d$98624020$c926c060$@tosovsky@email.cz>
2014-03-16 18:06 ` Hans Hagen
2014-03-16 16:14 ` Hans Hagen
2014-02-26 18:07 Jan Tosovsky
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='9207.12295123867$1394984101@news.gmane.org' \
--to=j.tosovsky@email.cz \
--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).