[Texi2html-cvs] Changes to texi2html/Tests/texinfo_res/texinfo_7.html

[Patrice Dumas]

Index: texi2html/Tests/texinfo_res/texinfo_7.html
diff -u texi2html/Tests/texinfo_res/texinfo_7.html:1.23 
texi2html/Tests/texinfo_res/texinfo_7.html:1.24
--- texi2html/Tests/texinfo_res/texinfo_7.html:1.23     Tue Aug  9 17:19:24 2005
+++ texi2html/Tests/texinfo_res/texinfo_7.html  Tue Aug 23 23:51:16 2005
@@ -131,7 +131,7 @@
 <li>
 In Info, node and menu commands provide structure.  The chapter
 structuring commands generate headings with different kinds of
-underlining--asterisks for chapters, hyphens for sections, and so on;
+underlining&mdash;asterisks for chapters, hyphens for sections, and so on;
 they do nothing else.
 
 </li><li>
@@ -177,7 +177,7 @@
 <p>Here is a copy of the diagram shown earlier that illustrates a Texinfo
 file with three chapters, each of which contains two sections.
 </p>
-<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
 bottom.  This is how such a diagram is drawn conventionally; it
 illustrates an upside-down tree.  For this reason, the root node is
 called the `Top' node, and `Up' node pointers carry you closer to the
@@ -200,17 +200,17 @@
 @comment  node-name,  next,      previous,  up
 </pre></td></tr></table>
 
-<p>This <code>@node</code> line says that the name of this node is 
&quot;Chapter
-2&quot;, the name of the `Next' node is &quot;Chapter 3&quot;, the name of the
-`Previous' node is &quot;Chapter 1&quot;, and the name of the `Up' node is
-&quot;Top&quot;.  You can omit writing out these node names if your document is
+<p>This <code>@node</code> line says that the name of this node is 
&ldquo;Chapter
+2&rdquo;, the name of the `Next' node is &ldquo;Chapter 3&rdquo;, the name of 
the
+`Previous' node is &ldquo;Chapter 1&rdquo;, and the name of the `Up' node is
+&ldquo;Top&rdquo;.  You can omit writing out these node names if your document 
is
 hierarchically organized (see section <a href="#SEC95">Creating Pointers with 
<code>makeinfo</code></a>), but the
 pointer relationships still obtain.
 </p>
 <blockquote><p><strong>Please Note:</strong> `Next' refers to the next node at 
the same
 hierarchical level in the manual, not necessarily to the next node
 within the Texinfo file.  In the Texinfo file, the subsequent node may
-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
 chapter-level node, for example.  `Next' and `Previous' refer to nodes
 at the <em>same</em> hierarchical level.  (The `Top' node contains the
 exception to this rule.  Since the `Top' node is the only node at that
@@ -233,7 +233,7 @@
     @comment  node-name, next,      previous,  up
 </pre></td></tr></table>
 <p>In Info format, the `Next' and `Previous' pointers of a node usually
-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
 section to section (sometimes, as shown, the `Previous' pointer points
 up); an `Up' pointer usually leads to a node at the level above (closer
 to the `Top' node); and a `Menu' leads to nodes at a level below (closer
@@ -245,8 +245,8 @@
 <code>@node</code> line with a comment line that reminds you which pointer is
 which.)
 </p>
-<p>Here is the beginning of the chapter in this manual called &quot;Ending a
-Texinfo File&quot;.  This shows an <code>@node</code> line followed by a 
comment
+<p>Here is the beginning of the chapter in this manual called &ldquo;Ending a
+Texinfo File&rdquo;.  This shows an <code>@node</code> line followed by a 
comment
 line, an <code>@chapter</code> line, and then by indexing lines.
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@node    Ending a File, 
Structuring, Beginning a File, Top
@@ -306,7 +306,7 @@
 about nodes in Info.)
 </p>
 <p>Usually, you write one of the chapter-structuring command lines
-immediately after an <code>@node</code> line--for example, an
+immediately after an <code>@node</code> line&mdash;for example, an
 <code>@section</code> or <code>@subsection</code> line.  (See section <a 
href="texinfo_6.html#SEC74">Structuring Command Types</a>.)
 </p>
 <blockquote><p><strong>Please note:</strong> The GNU Emacs Texinfo mode 
updating commands work
@@ -483,7 +483,7 @@
 
 </li><li>
 By convention, node names are capitalized just as they would be for
-section or chapter titles--initial and significant words are
+section or chapter titles&mdash;initial and significant words are
 capitalized; others are not.
 </li></ul>
 
@@ -520,9 +520,9 @@
 <p>Duplicates confuse the Info movement commands.  This means, for
 example, that if you end every chapter with a summary, you must name
 each summary node differently.  You cannot just call each one
-&quot;Summary&quot;.  You may, however, duplicate the titles of chapters, 
sections,
+&ldquo;Summary&rdquo;.  You may, however, duplicate the titles of chapters, 
sections,
 and the like.  Thus you can end each chapter in a book with a section
-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
 different.
 </p>
 </li><li>