/usr/share/doc/texinfo/html/Contents.html is in texinfo-doc-nonfree 4.13a-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 | <html lang="en">
<head>
<title>Contents - GNU Texinfo 4.13</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Texinfo 4.13">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Beginning-a-File.html#Beginning-a-File" title="Beginning a File">
<link rel="prev" href="Titlepage-_0026-Copyright-Page.html#Titlepage-_0026-Copyright-Page" title="Titlepage & Copyright Page">
<link rel="next" href="The-Top-Node.html#The-Top-Node" title="The Top Node">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This manual is for GNU Texinfo (version 4.13, 18 September 2008),
a documentation system that can produce both online information and a
printed manual from a single source.
Copyright (C) 1988, 1990, 1991, 1992, 1993, 1995, 1996, 1997,
1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008
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.2 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 are free to copy and modify
this GNU Manual. Buying copies from GNU Press supports the FSF in
developing GNU and promoting software freedom.''
-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
</head>
<body>
<div class="node">
<a name="Contents"></a>
<p>
Next: <a rel="next" accesskey="n" href="The-Top-Node.html#The-Top-Node">The Top Node</a>,
Previous: <a rel="previous" accesskey="p" href="Titlepage-_0026-Copyright-Page.html#Titlepage-_0026-Copyright-Page">Titlepage & Copyright Page</a>,
Up: <a rel="up" accesskey="u" href="Beginning-a-File.html#Beginning-a-File">Beginning a File</a>
<hr>
</div>
<h3 class="section">3.5 Generating a Table of Contents</h3>
<p><a name="index-Table-of-contents-213"></a><a name="index-Contents_002c-Table-of-214"></a><a name="index-Short-table-of-contents-215"></a><a name="index-contents-216"></a><a name="index-summarycontents-217"></a><a name="index-shortcontents-218"></a>
The <code>@chapter</code>, <code>@section</code>, and other structuring commands
(see <a href="Structuring.html#Structuring">Structuring</a>) supply the information to make up a
table of contents, but they do not cause an actual table to appear in
the manual. To do this, you must use the <code>@contents</code> and/or
<code>@summarycontents</code> command(s).
<dl>
<dt><code>@contents</code><dd>Generates a table of contents in a printed manual, including all
chapters, sections, subsections, etc., as well as appendices and
unnumbered chapters. Headings generated by <code>@majorheading</code>,
<code>@chapheading</code>, and the other <code>@...heading</code> commands
do not appear in the table of contents (see <a href="Structuring-Command-Types.html#Structuring-Command-Types">Structuring Command Types</a>).
<br><dt><code>@shortcontents</code><dt><code>@summarycontents</code><dd>(<code>@summarycontents</code> is a synonym for <code>@shortcontents</code>.)
<p>Generates a short or summary table of contents that lists only the
chapters, appendices, and unnumbered chapters. Sections, subsections
and subsubsections are omitted. Only a long manual needs a short
table of contents in addition to the full table of contents.
</dl>
<p>Both contents commands should be written on a line by themselves, and
are best placed near the beginning of the file, after the <code>@end
titlepage</code> (see <a href="titlepage.html#titlepage">titlepage</a>). The contents commands automatically
generate a chapter-like heading at the top of the first table of
contents page, so don't include any sectioning command such as
<code>@unnumbered</code> before them.
<p>Since an Info file uses menus instead of tables of contents, the Info
formatting commands ignore the contents commands. But the contents are
included in plain text output (generated by <code>makeinfo
--no-headers</code>), unless <code>makeinfo</code> is writing its output to standard
output.
<p>When <code>makeinfo</code> writes a short table of contents while producing
HTML output, the links in the short table of contents point to
corresponding entries in the full table of contents rather than the text
of the document. The links in the full table of contents point to the
main text of the document.
<p>In the past, the contents commands were sometimes placed at the end of
the file, after any indices and just before the <code>@bye</code>, but we
no longer recommend this.
<p><a name="index-setcontentsaftertitlepage-219"></a><a name="index-setshortcontentsaftertitlepage-220"></a><a name="index-Contents_002c-after-title-page-221"></a><a name="index-Table-of-contents_002c-after-title-page-222"></a>However, since many existing Texinfo documents still do have the
<code>@contents</code> at the end of the manual, if you are a user printing
a manual, you may wish to force the contents to be printed after the
title page. You can do this by specifying
<code>@setcontentsaftertitlepage</code> and/or
<code>@setshortcontentsaftertitlepage</code>. The first prints only the
main contents after the <code>@end titlepage</code>; the second prints both
the short contents and the main contents. In either case, any
subsequent <code>@contents</code> or <code>@shortcontents</code> is ignored
(unless, erroneously, no <code>@end titlepage</code> is ever encountered).
<p>You need to include the <code>@set...contentsaftertitlepage</code>
commands early in the document (just after <code>@setfilename</code>, for
example). We recommend using <samp><span class="command">texi2dvi</span></samp> (see <a href="Format-with-texi2dvi.html#Format-with-texi2dvi">Format with texi2dvi</a>) to specify this without altering the source file at all. For
example:
<pre class="example"> texi2dvi --texinfo=@setcontentsaftertitlepage foo.texi
</pre>
</body></html>
|