/[texi2html]/texi2html/Tests/texinfo_res/texinfo_7.html
ViewVC logotype

Diff of /texi2html/Tests/texinfo_res/texinfo_7.html

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

revision 1.23 by pertusus, Tue Aug 9 17:19:24 2005 UTC revision 1.24 by pertusus, Tue Aug 23 23:51:16 2005 UTC
# Line 131  technically independent of each other: Line 131  technically independent of each other:
131  <li>  <li>
132  In Info, node and menu commands provide structure.  The chapter  In Info, node and menu commands provide structure.  The chapter
133  structuring commands generate headings with different kinds of  structuring commands generate headings with different kinds of
134  underlining--asterisks for chapters, hyphens for sections, and so on;  underlining&mdash;asterisks for chapters, hyphens for sections, and so on;
135  they do nothing else.  they do nothing else.
136    
137  </li><li>  </li><li>
# Line 177  matching structure in the Info output. Line 177  matching structure in the Info output.
177  <p>Here is a copy of the diagram shown earlier that illustrates a Texinfo  <p>Here is a copy of the diagram shown earlier that illustrates a Texinfo
178  file with three chapters, each of which contains two sections.  file with three chapters, each of which contains two sections.
179  </p>  </p>
180  <p>The &quot;root&quot; is at the top of the diagram and the &quot;leaves&quot; are at the  <p>The &ldquo;root&rdquo; is at the top of the diagram and the &ldquo;leaves&rdquo; are at the
181  bottom.  This is how such a diagram is drawn conventionally; it  bottom.  This is how such a diagram is drawn conventionally; it
182  illustrates an upside-down tree.  For this reason, the root node is  illustrates an upside-down tree.  For this reason, the root node is
183  called the `Top' node, and `Up' node pointers carry you closer to the  called the `Top' node, and `Up' node pointers carry you closer to the
# Line 200  root. Line 200  root.
200  @comment  node-name,  next,      previous,  up  @comment  node-name,  next,      previous,  up
201  </pre></td></tr></table>  </pre></td></tr></table>
202    
203  <p>This <code>@node</code> line says that the name of this node is &quot;Chapter  <p>This <code>@node</code> line says that the name of this node is &ldquo;Chapter
204  2&quot;, the name of the `Next' node is &quot;Chapter 3&quot;, the name of the  2&rdquo;, the name of the `Next' node is &ldquo;Chapter 3&rdquo;, the name of the
205  `Previous' node is &quot;Chapter 1&quot;, and the name of the `Up' node is  `Previous' node is &ldquo;Chapter 1&rdquo;, and the name of the `Up' node is
206  &quot;Top&quot;.  You can omit writing out these node names if your document is  &ldquo;Top&rdquo;.  You can omit writing out these node names if your document is
207  hierarchically organized (see section <a href="#SEC95">Creating Pointers with <code>makeinfo</code></a>), but the  hierarchically organized (see section <a href="#SEC95">Creating Pointers with <code>makeinfo</code></a>), but the
208  pointer relationships still obtain.  pointer relationships still obtain.
209  </p>  </p>
210  <blockquote><p><strong>Please Note:</strong> `Next' refers to the next node at the same  <blockquote><p><strong>Please Note:</strong> `Next' refers to the next node at the same
211  hierarchical level in the manual, not necessarily to the next node  hierarchical level in the manual, not necessarily to the next node
212  within the Texinfo file.  In the Texinfo file, the subsequent node may  within the Texinfo file.  In the Texinfo file, the subsequent node may
213  be at a lower level--a section-level node most often follows a  be at a lower level&mdash;a section-level node most often follows a
214  chapter-level node, for example.  `Next' and `Previous' refer to nodes  chapter-level node, for example.  `Next' and `Previous' refer to nodes
215  at the <em>same</em> hierarchical level.  (The `Top' node contains the  at the <em>same</em> hierarchical level.  (The `Top' node contains the
216  exception to this rule.  Since the `Top' node is the only node at that  exception to this rule.  Since the `Top' node is the only node at that
# Line 233  before the beginning of Section 2.1, lik Line 233  before the beginning of Section 2.1, lik
233      @comment  node-name, next,      previous,  up      @comment  node-name, next,      previous,  up
234  </pre></td></tr></table>  </pre></td></tr></table>
235  <p>In Info format, the `Next' and `Previous' pointers of a node usually  <p>In Info format, the `Next' and `Previous' pointers of a node usually
236  lead to other nodes at the same level--from chapter to chapter or from  lead to other nodes at the same level&mdash;from chapter to chapter or from
237  section to section (sometimes, as shown, the `Previous' pointer points  section to section (sometimes, as shown, the `Previous' pointer points
238  up); an `Up' pointer usually leads to a node at the level above (closer  up); an `Up' pointer usually leads to a node at the level above (closer
239  to the `Top' node); and a `Menu' leads to nodes at a level below (closer  to the `Top' node); and a `Menu' leads to nodes at a level below (closer
# Line 245  used in sequence, along with indexing co Line 245  used in sequence, along with indexing co
245  <code>@node</code> line with a comment line that reminds you which pointer is  <code>@node</code> line with a comment line that reminds you which pointer is
246  which.)  which.)
247  </p>  </p>
248  <p>Here is the beginning of the chapter in this manual called &quot;Ending a  <p>Here is the beginning of the chapter in this manual called &ldquo;Ending a
249  Texinfo File&quot;.  This shows an <code>@node</code> line followed by a comment  Texinfo File&rdquo;.  This shows an <code>@node</code> line followed by a comment
250  line, an <code>@chapter</code> line, and then by indexing lines.  line, an <code>@chapter</code> line, and then by indexing lines.
251  </p>  </p>
252  <table><tr><td>&nbsp;</td><td><pre class="example">@node    Ending a File, Structuring, Beginning a File, Top  <table><tr><td>&nbsp;</td><td><pre class="example">@node    Ending a File, Structuring, Beginning a File, Top
# Line 306  the formatters fail.  (See <a href="../i Line 306  the formatters fail.  (See <a href="../i
306  about nodes in Info.)  about nodes in Info.)
307  </p>  </p>
308  <p>Usually, you write one of the chapter-structuring command lines  <p>Usually, you write one of the chapter-structuring command lines
309  immediately after an <code>@node</code> line--for example, an  immediately after an <code>@node</code> line&mdash;for example, an
310  <code>@section</code> or <code>@subsection</code> line.  (See section <a href="texinfo_6.html#SEC74">Structuring Command Types</a>.)  <code>@section</code> or <code>@subsection</code> line.  (See section <a href="texinfo_6.html#SEC74">Structuring Command Types</a>.)
311  </p>  </p>
312  <blockquote><p><strong>Please note:</strong> The GNU Emacs Texinfo mode updating commands work  <blockquote><p><strong>Please note:</strong> The GNU Emacs Texinfo mode updating commands work
# Line 483  Info. Line 483  Info.
483    
484  </li><li>  </li><li>
485  By convention, node names are capitalized just as they would be for  By convention, node names are capitalized just as they would be for
486  section or chapter titles--initial and significant words are  section or chapter titles&mdash;initial and significant words are
487  capitalized; others are not.  capitalized; others are not.
488  </li></ul>  </li></ul>
489    
# Line 520  All the node names for a single Info fil Line 520  All the node names for a single Info fil
520  <p>Duplicates confuse the Info movement commands.  This means, for  <p>Duplicates confuse the Info movement commands.  This means, for
521  example, that if you end every chapter with a summary, you must name  example, that if you end every chapter with a summary, you must name
522  each summary node differently.  You cannot just call each one  each summary node differently.  You cannot just call each one
523  &quot;Summary&quot;.  You may, however, duplicate the titles of chapters, sections,  &ldquo;Summary&rdquo;.  You may, however, duplicate the titles of chapters, sections,
524  and the like.  Thus you can end each chapter in a book with a section  and the like.  Thus you can end each chapter in a book with a section
525  called &quot;Summary&quot;, so long as the node names for those sections are all  called &ldquo;Summary&rdquo;, so long as the node names for those sections are all
526  different.  different.
527  </p>  </p>
528  </li><li>  </li><li>

Legend:
Removed from v.1.23  
changed lines
  Added in v.1.24

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