/usr/share/doc/texinfo/html/Indexing-Commands.html is in texinfo-doc-nonfree 5.2.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- This manual is for GNU Texinfo (version 5.2, 26 September 2013),
a documentation system that can produce both online information and a
printed manual from a single source using semantic markup.
Copyright (C) 1988, 1990, 1991, 1992, 1993, 1995, 1996, 1997,
1998, 1999, 2001, 2001, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
2010, 2011, 2012, 2013 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with the Front-Cover Texts being "A GNU Manual",
and with the Back-Cover Texts as in (a) below. A copy of the license
is included in the section entitled "GNU Free Documentation
License".
(a) The FSF's Back-Cover Text is: "You have the freedom to copy and
modify this GNU manual. Buying copies from the FSF supports it in
developing GNU and promoting software freedom." -->
<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Texinfo 5.2: Indexing Commands</title>
<meta name="description" content="GNU Texinfo 5.2: Indexing Commands">
<meta name="keywords" content="GNU Texinfo 5.2: Indexing Commands">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Command-and-Variable-Index.html#Command-and-Variable-Index" rel="index" title="Command and Variable Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Indices.html#Indices" rel="up" title="Indices">
<link href="Combining-Indices.html#Combining-Indices" rel="next" title="Combining Indices">
<link href="Predefined-Indices.html#Predefined-Indices" rel="previous" title="Predefined Indices">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Indexing-Commands"></a>
<div class="header">
<p>
Next: <a href="Combining-Indices.html#Combining-Indices" accesskey="n" rel="next">Combining Indices</a>, Previous: <a href="Predefined-Indices.html#Predefined-Indices" accesskey="p" rel="previous">Predefined Indices</a>, Up: <a href="Indices.html#Indices" accesskey="u" rel="up">Indices</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Command-and-Variable-Index.html#Command-and-Variable-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Defining-the-Entries-of-an-Index"></a>
<h3 class="section">13.3 Defining the Entries of an Index</h3>
<a name="index-Defining-indexing-entries"></a>
<a name="index-Index-entries"></a>
<a name="index-Entries-for-an-index"></a>
<a name="index-Specifying-index-entries"></a>
<a name="index-Creating-index-entries"></a>
<p>The data to make an index come from many individual indexing commands
scattered throughout the Texinfo source file. Each command says to add
one entry to a particular index; after formatting, the index will give
the current page number or node name as the reference.
</p>
<p>An index entry consists of an indexing command at the beginning of a
line followed, on the rest of the line, by the entry.
</p>
<p>For example, this section begins with the following five entries for
the concept index:
</p>
<div class="example">
<pre class="example">@cindex Defining indexing entries
@cindex Index entries, defining
@cindex Entries for an index
@cindex Specifying index entries
@cindex Creating index entries
</pre></div>
<p>Each predefined index has its own indexing command—<code>@cindex</code>
for the concept index, <code>@findex</code> for the function index, and so
on, as listed in the previous section.
</p>
<a name="index-Writing-index-entries"></a>
<a name="index-Index-entries_002c-advice-on-writing"></a>
<a name="index-Advice-on-writing-entries"></a>
<a name="index-Capitalization-of-index-entries"></a>
<p>Concept index entries consist of text. The best way to write an index
is to devise entries which are terse yet clear. If you can do this,
the index usually looks better if the entries are written just as they
would appear in the middle of a sentence, that is, capitalizing only
proper names and acronyms that always call for uppercase letters.
This is the case convention we use in most GNU manuals’ indices.
</p>
<p>If you don’t see how to make an entry terse yet clear, make it longer
and clear—not terse and confusing. If many of the entries are
several words long, the index may look better if you use a different
convention: to capitalize the first word of each entry. Whichever
case convention you use, use it consistently.
</p>
<p>In any event, do not ever capitalize a case-sensitive name such as a C
or Lisp function name or a shell command; that would be a spelling
error. Entries in indices other than the concept index are symbol
names in programming languages, or program names; these names are
usually case-sensitive, so likewise use upper- and lowercase as
required.
</p>
<a name="index-Unique-index-entries"></a>
<p>It is a good idea to make index entries unique wherever feasible.
That way, people using the printed output or online completion of
index entries don’t see undifferentiated lists. Consider this an
opportunity to make otherwise-identical index entries be more
specific, so readers can more easily find the exact place they are
looking for.
</p>
<p>Index entries should precede the visible material that is being
indexed. For instance:
</p>
<div class="example">
<pre class="example">@cindex hello
Hello, there!
</pre></div>
<p>Among other reasons, that way following indexing links (in
whatever context) ends up before the material, where readers want to
be, instead of after.
</p>
<a name="index-Index-font-types"></a>
<p>By default, entries for a concept index are printed in a small roman
font and entries for the other indices are printed in a small
<code>@code</code> font. You may change the way part of an entry is
printed with the usual Texinfo commands, such as <code>@file</code> for
file names (see <a href="Marking-Text.html#Marking-Text">Marking Text</a>), and <code>@r</code> for the normal roman
font (see <a href="Fonts.html#Fonts">Fonts</a>).
</p>
<blockquote>
<p><b>Caution:</b> Do not use a colon in an index entry. In Info, a colon separates the
menu entry name from the node name, so a colon in the entry itself
confuses Info. See <a href="Menu-Parts.html#Menu-Parts">Menu Parts</a>, for more information about the
structure of a menu entry.
</p></blockquote>
<hr>
<div class="header">
<p>
Next: <a href="Combining-Indices.html#Combining-Indices" accesskey="n" rel="next">Combining Indices</a>, Previous: <a href="Predefined-Indices.html#Predefined-Indices" accesskey="p" rel="previous">Predefined Indices</a>, Up: <a href="Indices.html#Indices" accesskey="u" rel="up">Indices</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Command-and-Variable-Index.html#Command-and-Variable-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|