[Texi2html-cvs] Changes to texi2html/Tests/viper_res/viper_4.html

[Patrice Dumas]

Index: texi2html/Tests/viper_res/viper_4.html
diff -u texi2html/Tests/viper_res/viper_4.html:1.22 
texi2html/Tests/viper_res/viper_4.html:1.23
--- texi2html/Tests/viper_res/viper_4.html:1.22 Tue Aug  9 17:19:25 2005
+++ texi2html/Tests/viper_res/viper_4.html      Tue Aug 23 23:51:16 2005
@@ -132,7 +132,7 @@
 <p>An easy way to customize Viper is to change the values of constants used in
 Viper.  Here is the list of the constants used in Viper and their default
 values.  The corresponding :se command is also indicated.  (The symbols
-<code>t</code> and <code>nil</code> represent &quot;true&quot; and 
&quot;false&quot; in Lisp).
+<code>t</code> and <code>nil</code> represent &ldquo;true&rdquo; and 
&ldquo;false&rdquo; in Lisp).
 </p>
 <p>Viper supports both the abbreviated Vi variable names and their full
 names.  Variable completion is done on full names only.  <kbd>TAB</kbd> and
@@ -141,7 +141,7 @@
 a value, if applicable.  For instance, <kbd>:se au <kbd>SPC</kbd></kbd> will 
complete the
 command to <kbd>:set autoindent</kbd>; <kbd>:se ta <kbd>SPC</kbd></kbd> will 
complete the command
 and prompt further like this: <kbd>:set tabstop = </kbd>.
-However, typing <kbd>:se ts <kbd>SPC</kbd></kbd> will produce a &quot;No 
match&quot; message
+However, typing <kbd>:se ts <kbd>SPC</kbd></kbd> will produce a &ldquo;No 
match&rdquo; message
 because <kbd>ts</kbd> is an abbreviation for <kbd>tabstop</kbd> and Viper 
supports
 completion on full names only.  However, you can still hit <kbd>RET</kbd>
 or <kbd>=</kbd>, which will complete the command like this: <kbd>:set ts = 
</kbd> and
@@ -231,7 +231,7 @@
 <dt> <code>viper-search-scroll-threshold 2</code></dt>
 <dd><p>If search lands within this many lines of the window top or bottom, the
 window will be scrolled up or down by about 1/7-th of its size, to reveal
-the context.  If the value is negative--don't scroll.
+the context.  If the value is negative&mdash;don't scroll.
 </p></dd>
 <dt> <code>viper-tags-file-name &quot;TAGS&quot;</code></dt>
 <dd><p>The name of the file used as the tag table.
@@ -352,7 +352,7 @@
 </p></dd>
 <dt> <code>viper-want-emacs-keys-in-vi</code></dt>
 <dd><p>This is set to <code>nil</code> for user
-level 1 and to <code>t</code> for user levels 2-4.
+level 1 and to <code>t</code> for user levels 2&ndash;4.
 At level 5, users are allowed to set this variable as they please (the
 default for this level is <code>t</code>).
 If set to <code>nil</code>, complete Vi compatibility is provided
@@ -828,7 +828,7 @@
 packages.  Fortunately, these modes operate on read-only buffers and are
 designed not for editing files, but for special-purpose browsing, reading
 news, mail, etc., and Vi commands are meaningless in these situations.  For
-this reason, Viper doesn't force Vi state on such major modes--it
+this reason, Viper doesn't force Vi state on such major modes&mdash;it
 brings them in Emacs state.  You can switch to Vi state by typing 
<kbd>C-z</kbd>
 if, for instance, you want to do Vi-style search in a buffer (although,
 usually, incremental search, which is bound to <kbd>C-s</kbd>, is sufficient in
@@ -945,7 +945,7 @@
 If you hit something other than <kbd>/</kbd> after the first <kbd>/</kbd> or 
if the
 second <kbd>/</kbd> doesn't follow quickly enough, then Viper will issue the
 usual prompt <kbd>/</kbd> and will wait for input, as usual in Vi.
-If you don't like this behavior, you can &quot;unrecord&quot; these macros in 
your
+If you don't like this behavior, you can &ldquo;unrecord&rdquo; these macros 
in your
 <tt>`~/.viper'</tt> file.  For instance, if you don't like the above feature, 
put
 this in <tt>`~/.viper'</tt>:
 </p><table><tr><td>&nbsp;</td><td><pre 
class="example">(viper-set-searchstyle-toggling-macros 'undefine)
@@ -963,7 +963,7 @@
 above, `//' and `///' get bound to Vi-style macros that toggle
 case-insensitivity and regexp-search.
 </p>
-<p>If you don't like these features--which I don't really understand--you
+<p>If you don't like these features&mdash;which I don't really 
understand&mdash;you
 can unbind `/' and `:' in <code>viper-dired-modifier-map</code> (for Dired) or 
in
 <code>viper-slash-and-colon-map</code>, for other modes.
 <a name="IDX200"></a>
@@ -1185,7 +1185,7 @@
 </p>
 <p>The region that is chosen as a pattern to search for is determined as
 follows.  If search is invoked via a single click, Viper chooses the region
-that lies between the beginning of the &quot;word&quot; under the pointer 
(&quot;word&quot;
+that lies between the beginning of the &ldquo;word&rdquo; under the pointer 
(&ldquo;word&rdquo;
 is understood in Vi sense) and the end of that word.  The only difference
 with Vi's words is that in Lisp major modes `-' is considered an
 alphanumeric symbol.  This is done for the convenience of working with Lisp
@@ -1196,8 +1196,8 @@
 feature gives added control over the patterns selected by the mouse click.
 </p>
 <p>On a double-click, the region is determined by the beginning of the current
-Vi's &quot;Word&quot; (i.e., the largest non-separator chunk of text) and the 
End
-of that &quot;Word&quot; (as determined by the <kbd>E</kbd> command).
+Vi's &ldquo;Word&rdquo; (i.e., the largest non-separator chunk of text) and 
the End
+of that &ldquo;Word&rdquo; (as determined by the <kbd>E</kbd> command).
 </p>
 <p>On a triple-click, the region consists of the entire line where the click
 occurred with all leading and trailing spaces and tabs removed.
@@ -1254,7 +1254,7 @@
 B and click to invoke mouse search, search (or insertion) will be performed
 in frame A.  To perform search/insertion in frame B, you will first have to
 shift focus there, which doesn't happen until you type a character or
-perform some other action in frame B--mouse search doesn't shift focus.
+perform some other action in frame B&mdash;mouse search doesn't shift focus.
 </p>
 <p>If you decide that you don't like the above feature and always want
 search/insertion be performed in the frame where the click occurs, don't
@@ -1371,7 +1371,7 @@
 type <kbd>C-x q</kbd> (for confirmation) or <kbd>C-u C-x q</kbd> (for prompt).
 For details, see <a 
href="../emacs/Kbd-Macro-Query.html#Kbd-Macro-Query">(emacs)Kbd Macro Query</a> 
section `Customization' in <cite>The GNU Emacs Manual</cite> 
 </p>
-<p>When the user finishes defining a macro (which is done by typing 
<kbd>C-x)</kbd> --
+<p>When the user finishes defining a macro (which is done by typing 
<kbd>C-x)</kbd> &mdash;
 a departure from Vi), you will be asked whether you want this
 macro to be global, mode-specific, or buffer-specific.  You will also be
 given a chance to save the macro in your <tt>`~/.viper'</tt> file.