Registers

From ConTeXt wiki
Jump to: navigation, search

< Structurals | References > (It's also in the manual at "Registers")

Contents

Basics

Use indexes as follows:

Note that the \completeindex command might not work correctly. In such situations you can use: \subject{Index} \placeindex

Example

My \index{dog}dog is a \index{dog+bullterrier}bullterrier named \seeindex{Dolly}{Underware}Dolly.
He doesn't like \index{cat}cats.
There are a lot of \index{cat+stray}stray cats, but only a few of them are \index{cat+Siamese}Siamese.

\placeindex

Styling the Index

Registers consist of three text elements that can be styled independently: the sections headings, the entry text, and a page number (reference). For formatting purposes each has its own key so it can be referred to consistently:

MkIV

General Setup

The appearance of a register can be configured with \setupregister. An example setup for the register entity could look like:

\defineregister [entity]
\setupregister  [entity] [
      style=sansbold,   %% headings
  textstyle=slanted,    %% entries
  pagestyle=bolditalic, %% page refs
          n=1,          %% columns
]

This typesets sections in bold face sans serif, entries with slant, and page references in italic. Also, the register will use a single column.

In MkIV \setupregister is consistent with the common interface to text style. Thus for every style there is a corresponding color option (color, textcolor, and pagecolor):

\setupregister  [entity] [
      color=red,
  textcolor=green,
  pagecolor=blue,
]

Naturally, self-defined alternatives are valid as well:

\definefontfeature [textfigures] [onum=yes]

\definealternativestyle [reg:bigbold]  [\bfc]                    []
\definealternativestyle [reg:tinybold] [\bfxx]                   []
\definealternativestyle [reg:bignum]   [\tfc\addff{textfigures}] []

\defineregister [entity]
\setupregister  [entity] [
      style=reg:bigbold,
  textstyle=reg:tinybold,
  pagestyle=reg:bignum,
]

Use with care!

Processors

The traditional approach to fine-tuning entries has not (yet?) been implemented in MkIV [1]. Instead, there is a new mechanism called processors available that has a similar effect [2].

Processors are created via \defineprocessor:

\defineprocessor [relevant] [style=italic]

To apply it to a register entry, we employ the -> operator:

Text \entity{foo}text.
Text \entity{relevant->bar}text.
Text \entity{baz}text.

This will render bar’s entry in the register entity in italic font, while the other two entries remain unchanged.

A processor is not local to a specific register (as it was in MkII). Once defined it can be applied to different registers, yielding the same effect:

\defineregister [first]
\defineregister [second]
\defineregister [third]
\defineprocessor [relevant] [style=italic,color=blue]
\starttext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
  \placefirst  \placesecond \placethird \page
  Text before.
  Text \first {foo} \first {relevant->bar 1} \first {baz}text.
  Text \second{foo} \second{relevant->bar 2} \second{baz}text.
  Text \third {foo} \third {relevant->bar 3} \third {baz}text.
  Text after.
\stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

The same processor can be applied to to both entries and page numbers. (Another difference from MkII.) For page numbers, apply the -> operator on the optional first argument:

\entity[relevant->]{foo}

Note that \entity[weird]{foo} is not enough. Without the ->, the first argument is interpreted as sort key. However, if in addition to the page number processor you wish to supply a custom sort key, then the sort key must follow the processor:

\entity[relevant->baz]{foo}

In this example, the page number will be displayed using the processor relevant and the entity foo will be treated like the string baz for sorting purposes. Of course, page number and text formatting can be combined:

\entity[relevant->]{relevant->foo}

Processors work well with multi-level indices:

\entity {relevant->foo}
\entity {relevant->foo+bar}
\entity {relevant->foo+bar+baz}

Applying multiple processors to a single entry has no effect. Context will ignore any other processor after the first. (This is probably a feature, as there is no need to repeat the processor with every entry.) However, different entries in the page reference list can be formatted differently:

\setupcolor[rgb]
\defineregister  [stuff] [style=sansbold,pagestyle=italic,n=1]
\defineprocessor [relevant]   [style=bold,color=red]
\defineprocessor [irrelevant] [color=darkgray]

\starttext
  \placestuff

  \page Text \stuff                {relevant->foo}   text.
  \page Text \stuff                {foo}             text.
  \page Text \stuff [relevant->]   {foo}             text.
  \page Text \stuff                {irrelevant->foo} text. %% no effect!
  \page Text \stuff [irrelevant->] {foo}             text.
\stoptext

Examples

Simple Setup

\defineregister [entity]
\setupregister  [entity] [
     style=sansbold,
 textstyle=slanted,
 pagestyle=bolditalic,
         n=1,
]

\starttext

  \placeentity \page

  Text before.
  Text \entity{foo} \entity{bar}   text.\page
  Text \entity{foo} \entity{baz}   text.\page
  Text \entity{foo} \entity{bar}   text.\page
  Text \entity{foo} \entity{xyzzy} text.\page
  Text after.
  
\stoptext

Colorful Setup

\defineregister [entity]
\setupregister  [entity] [
      color=red,
  textcolor=green,
  pagecolor=blue,
         n=1,
]

\starttext

  \placeentity \page

  Text before.
  Text \entity{foo} \entity{bar}   text.\page
  Text \entity{foo} \entity{baz}   text.\page
  Text \entity{foo} \entity{bar}   text.\page
  Text \entity{foo} \entity{xyzzy} text.\page
  Text after.
  
\stoptext

Setup with Alternatives

\definefontfeature [textfigures] [onum=yes]

\definealternativestyle [reg:bigbold]  [\bfc]                    []
\definealternativestyle [reg:tinybold] [\bfxx]                   []
\definealternativestyle [reg:bignum]   [\tfc\addff{textfigures}] []

\defineregister [entity]
\setupregister  [entity] [
      style=reg:bigbold,
  textstyle=reg:tinybold,
  pagestyle=reg:bignum,
]

\starttext

  \placeentity \page

  Text before.
  Text \entity{foo} \entity{bar}   text.\page
  Text \entity{foo} \entity{baz}   text.\page
  Text \entity{foo} \entity{bar}   text.\page
  Text \entity{foo} \entity{xyzzy} text.\page
  Text after.
  
\stoptext

Complex Setup

\definefontfeature [textfigures] [onum=yes]

\definealternativestyle [reg:heada]  [\WORD\ssa\bold]
\definealternativestyle [reg:headb]  [\word\tfb\sc]
\definealternativestyle [reg:pageno] [\addff{textfigures}\italic]

\defineregister [entity] [style=reg:heada,pagestyle=normal,n=3]
\defineregister [object] [style=reg:headb,pagestyle=reg:pageno,n=2]

\defineprocessor [relevant] [style=italic]
\defineprocessor [weird]    [style=italic,color=red]
\defineprocessor [striking] [style=bold,color=blue]

\starttext

  \placeentity \blank[3*big] \placeobject \page

  \dorecurse{3}{
    Text before.
    \page Text \entity             {foo}           text.
          Text \object             {striking->bar} text.
          Text \entity             {baz+foo}       text.
          Text \object             {foo+bar}       text.
    \page Text \entity[relevant->] {weird->foo}    text.
    \page Text \entity             {weird->bar}    text.
          Text \object[weird->]    {foo}           text.
          Text \object             {baz}           text.
    \page Text \entity[weird->foo] {foo}           text.
    \page Text \entity[weird->]    {baz}           text.
          Text \object             {baz}           text.
          Text \object             {bar+baz}       text.
          Text \entity[weird->]    {baz}           text.
          Text \entity             {baz+miranda}   text.
          Text \entity             {baz+xyzzy}     text.
          Text \object             {foo}           text.
    \page Text \entity             {weird->foo}    text.
          Text \object[striking->] {bar+baz}       text.
          Text \object             {foo}           text.
          Text \entity[relevant->] {baz+xyzzy}     text.
    \page Text \entity[weird->foo] {foo}           text.
          Text \object             {bar+xyzzy}     text.
          Text \object             {baz}           text.
          Text \object             {foo}           text.
          Text \entity[weird->]    {baz+xyzzy+meh} text.
    \page Text \entity[weird->]    {weird->foo}    text.
          Text \object[striking->] {foo}           text.
          Text \object             {xyzzy}         text.
          Text \entity             {baz+xyzzy}     text.
    Text after.
  }

\stoptext


MkII

General Setup

The interface for register styling is \setupregister. For settings that apply to the register as a whole use the two-argument version:

\defineregister[thing][stuff]
\setupregister[thing][
  style=boldslanted,  %% headings
  textstyle=bold,     %% items
  pagestyle=slanted,  %% page numbers
]

Here we first initialize a register thing. Then we assign a different style to each of the three elements: the option style refers to index section headings (letters), which will be typeset in bold slanted; textstyle means the item (indexed string, here bold); finally, pagestyle sets the page number references (slanted).

Individiual Entries

Better granularity regarding the formatting of individual entries can be achieved through the three-argument version of \setupregister. Its second argument is an identifier by means of which a sub-style can be applied later.

\setupregister[thing][important] [textstyle=bold,  pagestyle=boldslanted]
\setupregister[thing][nonsense]  [textstyle=\tfxx, pagestyle=\tfd]

This creates the substyles important and nonsense for the register thing. To apply a sub-style, it has to be specified when an entry is added to the register. If we wanted to highlight an entry as important, we would call the macro \thing as follows:

text before \thing{important::entry} text after

Note the double colon (::) that serves as delimiter between style directive (left hand side) and entry text (right). To highlight the page number instead:

text before \thing[important::]{entry} text after

Note that the :: is non-optional! If the double colon is omitted, important would instead refer to the string used for register sorting. Of course, both elements can be styled at once:

text before \thing[important::]{nonsense::entry} text after

This produces an entry whose text is highlighted according to the definition of nonsense with a pagenumber styled as important.

The syntax for an MkII-style register entry has the schematic:

\<registercmd> [<pagestyle>::<sortkey>] {<textstyle>::<category>+<entry>}

where only <entry> is mandatory.

Example

A complete working example demonstrating the highlighting capabilities:

\defineregister[thing][things]
%%% 2-arg
\setupregister[thing][
  style=boldslanted,
  textstyle=normal,
  pagestyle=slanted,
]

%%% 3-arg
\setupregister[thing][important] [textstyle=bold,  pagestyle=boldslanted]
\setupregister[thing][nonsense]  [textstyle=\tfxx, pagestyle=\tfd]


\starttext
  Ordinary entries: \thing{one}\thing{two}

  Just a                \thing               {important::three}test.  %% text -> “important”
  Yet another           \thing               {nonsense::four}test.    %% text -> “nonsense”
  Again, nothing but a  \thing [important::] {five}test.              %% page -> “important”
  Old story: this is a  \thing [important::] {important::five}test.   %% both -> “important”
  Get it? A             \thing [important::] {important::six}test.    %% both -> “important”
  Plain and simple:     \thing [nonsense::]  {nonsense::seven}test.   %% both -> “nonsense”

  \placething
\stoptext

category>+ /context>

Colorful Setup

More Registers

\index is only one special case of \register. You can define as much different registers as you like:

\defineregister[singular name][plural name], e.g.

\defineregister[mouse][mice]
\setupregister[mouse][style=\ss]

\mouse{rat}

\placemouse

(Don't know if the plural form is used anywhere...)

Tricks

Collapse Page Numbers

There are a few ways to collapse page numbers. The first way is to use the compress=yes parameter to the \setupregister command.

The second way is to mark several pages for the same entry using \startregister[index][mymouse]{mouse} ... \stopregister[index][mymouse]. This becomes e.g. "mouse 12--16". Note that if you have two or more of these ranges, you need them to have different [key] values to stop the system treating them as part of a great big range. So, use \startregister[index][mymouse1]{mouse} ... \stopregister[index][mymouse1] and then \startregister[index][mymouse2]{mouse} ... \stopregister[index][mymouse2] to get two independent ranges in the list. \startregister takes four arguments, of which two are mandatory: \startregister[NAME_OF_REGISTER]{ENTRY_NAME}. The other arguments are [KEY_FOR_RANGE] and [KEY_FOR_SORTING]. To give an example: \startregister[index][levi][Levi-Strauss]{Lévi|-|Strauss}. This will start a range with the key levi which will put the entry "Lévi-Strauss" in the register "index" (the "normal" register) and sort it under "Levi-Strauss." To mark the end of the range, you write \stopregister[index][levi].


Rename Register Heading

Change the \completeregister heading using the \setupheadtext command. For example:

\defineregister[photographer][]

\setupregister[photographer][
  indicator=no,
]

\setupheadtext[photographer=Credits]

\starttext 
  \photographer{Yousuf Karsh}

  \completephotographer
\stoptext 

Alphabetical Headers

The letters of the alphabet can be disabled by \setupregister[register][indicator=no].

The vertical spaces between the entry groups for subsequent letters is governed by the parameter before in the same command (default: \blank, change to before={} to get no additional space).


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 \setupregister[index][coupling=yes]. Substitute \index with \coupledindex and enjoy!

Impact on vertical spacing

In some situations, placing an \index (or related command) might affect vertical spacing and the page-breaking mechanism. In those situations it is advisable to wrap the command in a \doflushatpar as shown below (needs a ConTeXt version dated after 14th Dec 2005):

\starttext
\section{Tufte}
\dorecurse{4}{\input tufte \par}
\section{Knuth}
\doflushatpar{\index{Knuth}}
\input knuth \par
\stoptext

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:

\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

Note the two possible definitions, and the pitfalls with each one. If you are still having trouble with specific \index 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 \index, or it wrapped in one of the two possible \doflushatpars, should solve any problem.

C O N T E X T G A R D E N

Personal tools
Namespaces
Variants
Actions
Help
External Help
Installation
Navigation
Toolbox