Re: [NTG-context] Eliminating orpans in the Index
On 11/26/2013 10:09 PM, Jan Tosovsky wrote:
On 2013-11-23 Jan Tosovsky wrote:
in my two-column index there are several cases when the last entry in the given letter group overflows to the next column/page. In the extreme case it is just the last page reference. ... Additionaly, columns are not balanced properly in all cases. When the first is longer, it is not a big problem. But the opposite case looks weird.
As the registers are rendered programatically, I cannot intervene into this process. But can I influence it e.g. using 'processors' applied to problematic index entries?
Processors can be used for setting the font-weight or color of particular entry. Can the same method used for manual setting of 'keep-with-previous/next' ?
I can think of a hack but it will always be for last minute work. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 2013-11-27 Hans Hagen wrote:
On 11/26/2013 10:09 PM, Jan Tosovsky wrote:
On 2013-11-23 Jan Tosovsky wrote:
in my two-column index there are several cases when the last entry in the given letter group overflows to the next column/page. In the extreme case it is just the last page reference. ... Additionaly, columns are not balanced properly in all cases. When the first is longer, it is not a big problem. But the opposite case looks weird.
As the registers are rendered programatically, I cannot intervene into this process. But can I influence it e.g. using 'processors' applied to problematic index entries?
Processors can be used for setting the font-weight or color of particular entry. Can the same method used for manual setting of 'keep-with-previous/next' ?
I can think of a hack but it will always be for last minute work.
I am also investigating grids. Switching this feature on has introduced orphan/widows in the standard body text. I've applied setups according to: http://www.mail-archive.com/ntg-context@ntg.nl/msg66393.html and it now fixes also problematic index entries :-) Like orphan/widow settings weren't specified by default... But I suspect the correct result to be rather coincidence... Some higher number of lines kept together still produce orphans... But it is overall much better now. One extra observation. Regardless the number of lines in the setups max. two lines seem to be kept together in the index... Jan
participants (2)
-
Hans Hagen -
Jan Tosovsky