/[texi2html]/texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html
ViewVC logotype

Diff of /texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.17 by pertusus, Tue Aug 9 17:19:22 2005 UTC revision 1.18 by pertusus, Tue Aug 23 23:51:14 2005 UTC
# Line 97  the concept index: Line 97  the concept index:
97  @cindex Specifying index entries  @cindex Specifying index entries
98  @cindex Creating index entries  @cindex Creating index entries
99  </pre></td></tr></table>  </pre></td></tr></table>
100  <p>Each predefined index has its own indexing command--<code>@cindex</code>  <p>Each predefined index has its own indexing command&mdash;<code>@cindex</code>
101  for the concept index, <code>@findex</code> for the function index, and so  for the concept index, <code>@findex</code> for the function index, and so
102  on.  on.
103  </p>  </p>
# Line 112  letters.)  This is the case convention w Line 112  letters.)  This is the case convention w
112  indices.  indices.
113  </p>  </p>
114  <p>If you don't see how to make an entry terse yet clear, make it longer  <p>If you don't see how to make an entry terse yet clear, make it longer
115  and clear--not terse and confusing.  If many of the entries are several  and clear&mdash;not terse and confusing.  If many of the entries are several
116  words long, the index may look better if you use a different convention:  words long, the index may look better if you use a different convention:
117  to capitalize the first word of each entry.  But do not capitalize a  to capitalize the first word of each entry.  But do not capitalize a
118  case-sensitive name such as a C or Lisp function name or a shell  case-sensitive name such as a C or Lisp function name or a shell
# Line 176  the entry itself confuses Info.  See sec Line 176  the entry itself confuses Info.  See sec
176  canonical purposes.  For example, suppose you wish to index some C  canonical purposes.  For example, suppose you wish to index some C
177  preprocessor macros.  You could put them in the function index along  preprocessor macros.  You could put them in the function index along
178  with actual functions, just by writing <code>@findex</code> commands for  with actual functions, just by writing <code>@findex</code> commands for
179  them; then, when you print the &quot;Function Index&quot; as an unnumbered  them; then, when you print the &ldquo;Function Index&rdquo; as an unnumbered
180  chapter, you could give it the title `Function and Macro Index' and  chapter, you could give it the title `Function and Macro Index' and
181  all will be consistent for the reader.  Or you could put the macros in  all will be consistent for the reader.  Or you could put the macros in
182  with the data types by writing <code>@tindex</code> commands for them, and  with the data types by writing <code>@tindex</code> commands for them, and

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.18

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26