Changes

Jump to navigation Jump to search
1,222 bytes added ,  18:11, 14 December 2005
Added note on vertical space problems
* Place a word in text ''and'' index: <tt>\def\Tindex#1{\index{#1}#1}</tt> -- Please someone enhance this to get space correction, [] sorting etc.!
==Coupled Registers==
This is a special feature for documents that are only used on screen: Make a word clickable to jump to the index, the first or last occurrence.
Enable it with <cmd>setupregister</cmd><tt>[index][coupling=yes]</tt>.
Substitute <cmd>index</cmd> with <cmd>coupledindex</cmd> and enjoy!
 
=Impact on vertical spacing=
 
In some situations, placing an <cmd>index</cmd> (or related command) might affect vertical spacing and the page-breaking mechanism. In those situations it is advisable to wrap the command in a <cmd>doflushatpar</cmd> as shown below (needs a ConTeXt version dated after 14th Dec 2005):
 
<texcode>
\starttext
\section{Tufte}
\dorecurse{4}{\input tufte \par}
\section{Knuth}
\doflushatpar{\index{Knuth}}
\input knuth \par
\stoptext
</texcode>
 
This will stop bad-page breaking between the section title and the following para, for example.
 
==Technical note==
 
The above command is defined as follows:
 
<texcode>
\long\def\doflushatpar#1%
% {\dogotopar{\dontleavehmode#1}} % this one can introduce empty lines
{\dogotopar{#1\ifvmode\nobreak\fi}} % while this one can mess up vertical space
</texcode>
 
Note the two possible definitions, and the pitfalls with each one. If you are still having trouble with specific <cmd>index</cmd> commands, try using the alternative definition. When they are used in the right context, these three possible ways of placing an index term (the plain <cmd>index</cmd>, or it wrapped in one of the two possible <cmd>doflushatpar</cmd>s, should solve any problem.
21

edits

Navigation menu