From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Orphans/Widows in the Index
Date: Wed, 25 Jun 2014 22:38:15 +0200 [thread overview]
Message-ID: <5720.52742722935$1403728721@news.gmane.org> (raw)
In-Reply-To: <009301cf8f15$97925ab0$c6b71010$@tosovsky@email.cz>
On 2014-06-23 Jan Tosovsky wrote:
> On 2014-04-23 Jan Tosovsky wrote:
> >
> > in my auto-generated two column index (registry) there are
> > several cases of widows - it is the last item of the given
> > letter which overflows to next column/page:
> >
> > --------------- (start page) -------
> > Usti 29 (! alone !)
> >
> > V
> > Vamberk 18
> > ...
> > ...
> >
> >
> > There are also few cases of orphans, but this is not so strange:
> > ...
> > ...
> > Josef 29
> >
> > K
> > Karel 69 (! alone !)
> > ---------------- (end page) ---------
> >
>
> I think both cases could be eliminated by establishing a new constraint
> to the 'key letter':
> (1) There must be 0 or at least 3 lines at the beginning of the
> page/column before the Key letter.
> (2) There must be at least 2 lines after the Key letter.
>
> Can this be somehow set in my source file?
>
I've found the corresponding code in strc-reg.mkiv:
\setvalue{\??registerindicator a}#1%
{\registerparameter\c!before
% bugged, why does leftskip gets set:
\vskip\lineheight\goodbreak\vskip-\lineheight
\begingroup
\useregisterstyleandcolor\c!style\c!color
\dontleavehmode
\strut
\iflocation
\dosetdirectpagereference{\currentregister:\v!section:#1}%
\fi
\registerparameter\c!command{#1}%
\endgroup
\blank[\v!samepage]%
\registerparameter\c!after
\par
\nobreak}
That (2) case can be fixed by a small change:
\testcolumn[3]\registerparameter\c!command{#1}%
But when tested on this MWE, you can see a drawback - the first letter (p)
starts always on the second line (not on the first one):
\setupregister[balance=yes]
\starttext
\index{primary+secondary+tertiary}
\index[primary long]{\dorecurse{5}{primary long }}
\index[primary longer]{\dorecurse{5}{primary longer }}
\input{tufte}
\completeindex
\stoptext
Can this issue somehow be eliminated? Tested on the last beta (with my
patch).
That (1) case is still open. I have no idea how to accomplish something like
this using (Con)TeX(t) syntax :-(
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-06-25 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001901cf5f26$3e1a2310$ba4e6930$@tosovsky@email.cz>
2014-06-23 19:01 ` Jan Tosovsky
[not found] ` <009301cf8f15$97925ab0$c6b71010$@tosovsky@email.cz>
2014-06-25 20:38 ` Jan Tosovsky [this message]
[not found] ` <00ba01cf90b5$6471be90$2d553bb0$@tosovsky@email.cz>
2014-07-05 10:42 ` Jan Tosovsky
2014-04-23 19:00 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='5720.52742722935$1403728721@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).