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

[Patrice Dumas]

Index: texi2html/Tests/nodes_texinfo_res/Tips.html
diff -u texi2html/Tests/nodes_texinfo_res/Tips.html:1.20 
texi2html/Tests/nodes_texinfo_res/Tips.html:1.21
--- texi2html/Tests/nodes_texinfo_res/Tips.html:1.20    Tue Aug  9 17:19:22 2005
+++ texi2html/Tests/nodes_texinfo_res/Tips.html Tue Aug 23 23:51:14 2005
@@ -90,8 +90,8 @@
 Write in the present tense, not in the past or the future.
 
 </li><li>
-Write actively!  For example, write &quot;We recommend that &hellip;&quot; 
rather
-than &quot;It is recommended that &hellip;&quot;.
+Write actively!  For example, write &ldquo;We recommend that &hellip;&rdquo; 
rather
+than &ldquo;It is recommended that &hellip;&rdquo;.
 
 </li><li>
 Use 70 or 72 as your fill column.  Longer lines are hard to read.
@@ -121,7 +121,7 @@
 
 </li><li>
 Write index entries only where a topic is discussed significantly.  For
-example, it is not useful to index &quot;debugging information&quot; in a
+example, it is not useful to index &ldquo;debugging information&rdquo; in a
 chapter on reporting bugs.  Someone who wants to know about debugging
 information will certainly not find it in that chapter.
 
@@ -144,7 +144,7 @@
 a paragraph before that paragraph.
 
 <p>In the example that follows, a blank line comes after the index
-entry for &quot;Leaping&quot;:
+entry for &ldquo;Leaping&rdquo;:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@section The Dog and the Fox
 @cindex Jumping, in general
@@ -158,7 +158,7 @@
 </pre></td></tr></table>
 
 <p>(Note that the example shows entries for the same concept that are
-written in different ways--<samp>`Lazy dog'</samp>, and <samp>`Dog, 
lazy'</samp>--so
+written in different ways&mdash;<samp>`Lazy dog'</samp>, and <samp>`Dog, 
lazy'</samp>&mdash;so
 readers can look up the concept in different ways.)
 </p></li></ul>
 
@@ -211,8 +211,8 @@
 
 </li><li>
 Write the prefatory sentence or phrase for a multi-item list or table as
-a complete expression.  Do not write &quot;You can set:&quot;; instead, write
-&quot;You can set these variables:&quot;.  The former expression sounds cut 
off.
+a complete expression.  Do not write &ldquo;You can set:&rdquo;; instead, write
+&ldquo;You can set these variables:&rdquo;.  The former expression sounds cut 
off.
 </li></ul>
 
 <a name="SEC282"></a>
@@ -252,11 +252,11 @@
 
 <ul>
 <li>
-Capitalize &quot;Texinfo&quot;; it is a name.  Do not write the 
<samp>`x'</samp> or
+Capitalize &ldquo;Texinfo&rdquo;; it is a name.  Do not write the 
<samp>`x'</samp> or
 <samp>`i'</samp> in upper case.
 
 </li><li>
-Capitalize &quot;Info&quot;; it is a name.
+Capitalize &ldquo;Info&rdquo;; it is a name.
 
 </li><li>
 Write TeX using the <code>@TeX{}</code> command.  Note the uppercase
@@ -340,8 +340,8 @@
 Introduce new terms so that a reader who does not know them can
 understand them from context; or write a definition for the term.
 
-<p>For example, in the following, the terms &quot;check in&quot;, 
&quot;register&quot; and
-&quot;delta&quot; are all appearing for the first time; the example sentence 
should be
+<p>For example, in the following, the terms &ldquo;check in&rdquo;, 
&ldquo;register&rdquo; and
+&ldquo;delta&rdquo; are all appearing for the first time; the example sentence 
should be
 rewritten so they are understandable.
 </p>
 <blockquote><p>The major function assists you in checking in a file to your
@@ -411,15 +411,15 @@
 
 <p>Here are several examples of bad writing to avoid:
 </p>
-<p>In this example, say, &quot; &hellip; you must <code>@dfn</code>{check
-in} the new version.&quot;  That flows better.
+<p>In this example, say, &ldquo; &hellip; you must <code>@dfn</code>{check
+in} the new version.&rdquo;  That flows better.
 </p>
 <blockquote><p>When you are done editing the file, you must perform a
 <code>@dfn</code>{check in}.
 </p></blockquote>
 
-<p>In the following example, say, &quot;&hellip; makes a unified interface 
such as VC
-mode possible.&quot;
+<p>In the following example, say, &ldquo;&hellip; makes a unified interface 
such as VC
+mode possible.&rdquo;
 </p>
 <blockquote><p>SCCS, RCS and other version-control systems all perform similar
 functions in broadly similar ways (it is this resemblance which makes
@@ -439,7 +439,7 @@
 <li>
 Pronounce TeX as if the <samp>`X'</samp> were a Greek `chi', as the last
 sound in the name `Bach'.  But pronounce Texinfo as in `speck':
-&quot;teckinfo&quot;.
+&ldquo;teckinfo&rdquo;.
 
 </li><li>
 Write notes for yourself at the very end of a Texinfo file after the