[Texi2html-cvs] Changes to texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html

[Patrice Dumas]

Index: texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html
diff -u texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html:1.17 
texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html:1.18
--- texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html:1.17       Tue Aug 
 9 17:19:22 2005
+++ texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html    Tue Aug 23 
23:51:14 2005
@@ -97,7 +97,7 @@
 @cindex Specifying index entries
 @cindex Creating index entries
 </pre></td></tr></table>
-<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>
 for the concept index, <code>@findex</code> for the function index, and so
 on.
 </p>
@@ -112,7 +112,7 @@
 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
+and clear&mdash;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.  But do not capitalize a
 case-sensitive name such as a C or Lisp function name or a shell
@@ -176,7 +176,7 @@
 canonical purposes.  For example, suppose you wish to index some C
 preprocessor macros.  You could put them in the function index along
 with actual functions, just by writing <code>@findex</code> commands for
-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
 chapter, you could give it the title `Function and Macro Index' and
 all will be consistent for the reader.  Or you could put the macros in
 with the data types by writing <code>@tindex</code> commands for them, and