about summary refs log tree commit diff stats
path: root/lynx_help
diff options
context:
space:
mode:
authorThomas E. Dickey <dickey@invisible-island.net>2013-05-22 00:57:45 -0400
committerThomas E. Dickey <dickey@invisible-island.net>2013-05-22 00:57:45 -0400
commitf7f5657f1e38597bf3b301d56aa5368c12979524 (patch)
treefbf19ded0515323932f397676e33637117071f48 /lynx_help
parente294ae2634858bab2dccda56a4a205a979eab96a (diff)
downloadlynx-snapshots-f7f5657f1e38597bf3b301d56aa5368c12979524.tar.gz
snapshot of project "lynx", label v2-8-7dev_15f
Diffstat (limited to 'lynx_help')
-rw-r--r--lynx_help/Lynx_users_guide.html236
-rw-r--r--lynx_help/about_lynx.html31
-rw-r--r--lynx_help/keystrokes/alt_edit_help.html8
-rw-r--r--lynx_help/keystrokes/bashlike_edit_help.html13
-rw-r--r--lynx_help/keystrokes/bookmark_help.html6
-rw-r--r--lynx_help/keystrokes/cookie_help.html6
-rw-r--r--lynx_help/keystrokes/dired_help.html6
-rw-r--r--lynx_help/keystrokes/edit_help.html8
-rw-r--r--lynx_help/keystrokes/environments.html18
-rw-r--r--lynx_help/keystrokes/follow_help.html4
-rw-r--r--lynx_help/keystrokes/gopher_types_help.html8
-rw-r--r--lynx_help/keystrokes/history_help.html6
-rw-r--r--lynx_help/keystrokes/keystroke_help.html6
-rw-r--r--lynx_help/keystrokes/movement_help.html6
-rw-r--r--lynx_help/keystrokes/option_help.html91
-rw-r--r--lynx_help/keystrokes/other_help.html6
-rw-r--r--lynx_help/keystrokes/print_help.html6
-rw-r--r--lynx_help/keystrokes/scrolling_help.html6
-rw-r--r--lynx_help/keystrokes/test_display.html84
-rw-r--r--lynx_help/keystrokes/visited_help.html6
-rw-r--r--lynx_help/keystrokes/xterm_help.html6
-rw-r--r--lynx_help/lynx-dev.html10
-rw-r--r--lynx_help/lynx_help_main.html9
-rw-r--r--lynx_help/lynx_url_support.html250
24 files changed, 474 insertions, 362 deletions
diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html
index b7fba2dc..b703bfaa 100644
--- a/lynx_help/Lynx_users_guide.html
+++ b/lynx_help/Lynx_users_guide.html
@@ -1,10 +1,10 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!-- $LynxId: Lynx_users_guide.html,v 1.116 2012/01/31 23:55:11 tom Exp $ -->
+<!-- $LynxId: Lynx_users_guide.html,v 1.118 2013/05/22 00:56:39 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Users Guide v2.8.7</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -318,12 +318,14 @@
 
     <dd>is a scheme-specific field which for some schemes may
     correspond to a directory path and/or filename.</dd>
-  </dl>Here are some sample URLs.
+  </dl>
+
+  <p>Here are some sample URLs.</p>
 
   <dl>
     <dt>HTTP (HyperText Transfer Protocol)</dt>
 
-    <dd><code>http://www.subir.com/lynx.html</code></dd>
+    <dd><code>http://lynx.isc.org</code></dd>
 
     <dt>Gopher</dt>
 
@@ -342,17 +344,21 @@
 
     <dd><code>lynx
     http://kufacts.cc.ukans.edu/cwis/kufacts_start.html</code></dd>
-  </dl>Lynx also will attempt to create a complete URL if you
-  include adequate portions of it in the startfile argument. For
-  example:<br>
+  </dl>
+
+  <p>Lynx also will attempt to create a complete URL if you include
+  adequate portions of it in the startfile argument. For
+  example:<br></p>
   <pre>
 1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789
                  <em>wfbr</em>          will be expanded to:
       <em>http://www.wfbr.edu/</em>     and:
              <em>ftp.more.net/pub</em>  will be expanded to:
        <em>ftp://ftp.more.net/pub</em>
-</pre>See <a href="lynx_url_support.html">URL Schemes Supported by
-Lynx</a> for more detailed information.
+</pre>
+
+  <p>See <a href="lynx_url_support.html">URL Schemes Supported by
+  Lynx</a> for more detailed information.</p>
 
   <p>[<a href="#ToC-Remote">ToC</a>]</p>
 
@@ -385,8 +391,10 @@ Lynx</a> for more detailed information.
 
     <dd><code>WWW_HOME=http://www.w3.org/ [or in
     registry]</code></dd>
-  </dl>Note that on VMS the double-quoting <em>must</em> be
-  included to preserve casing.
+  </dl>
+
+  <p>Note that on VMS the double-quoting <em>must</em> be included
+  to preserve casing.</p>
 
   <p>[<a href="#ToC-EnVar">ToC</a>]</p>
 
@@ -412,29 +420,32 @@ Lynx</a> for more detailed information.
     |&lt;-- prev | next  | | sel. --&gt;|    | of    |   |   | DOWN  |
     |    doc. | link \|/| link    |    | text 1|  \|/ 2|      3|
     +---------+---------+---------+    +-------+-------+-------+
-</pre>There are also a few other keyboard commands to aid in
-navigation. The Control and Function keys used for navigation
-within the current document are described in <a href=
-"#MiscKeys"><em>Scrolling and Other useful commands</em></a>. Some
-additional commands depend on the fact that Lynx keeps a list of
-each link you visited to reach the current document, called the
-<a href="keystrokes/history_help.html">History Page</a>, and a list
-of all links visited during the current Lynx session, called the
-<a href="keystrokes/visited_help.html">Visited Links Page</a>. The
-HISTORY keystroke command, normally mapped to <em>Backspace</em> or
-<em>Delete</em>, will show you the <em>History Page</em> of links
-leading to your access of the current document. Any of the previous
-documents shown in the list may be revisited by selecting them from
-the history screen. The VLINKS keystroke command, normally mapped
-to uppercase '<em>V</em>', will show the <em>Visited Links
-Page</em>, and you similarly can select links in that list. The
-MAIN_MENU keystroke command, normally mapped to '<em>m</em>' and
-'<em>M</em>', will take you back to the starting document unless
-you specified the <em>-homepage=URL</em> option at the command
-line. Also, the LIST and ADDRLIST keystroke commands, normally
-mapped to '<em>l</em>' and <em>A</em>' respectively, will create a
-compact lists of all the links in the current document, and they
-can be selected via those lists.
+</pre>
+
+  <p>There are also a few other keyboard commands to aid in
+  navigation. The Control and Function keys used for navigation
+  within the current document are described in <a href=
+  "#MiscKeys"><em>Scrolling and Other useful commands</em></a>.
+  Some additional commands depend on the fact that Lynx keeps a
+  list of each link you visited to reach the current document,
+  called the <a href="keystrokes/history_help.html">History
+  Page</a>, and a list of all links visited during the current Lynx
+  session, called the <a href=
+  "keystrokes/visited_help.html">Visited Links Page</a>. The
+  HISTORY keystroke command, normally mapped to <em>Backspace</em>
+  or <em>Delete</em>, will show you the <em>History Page</em> of
+  links leading to your access of the current document. Any of the
+  previous documents shown in the list may be revisited by
+  selecting them from the history screen. The VLINKS keystroke
+  command, normally mapped to uppercase '<em>V</em>', will show the
+  <em>Visited Links Page</em>, and you similarly can select links
+  in that list. The MAIN_MENU keystroke command, normally mapped to
+  '<em>m</em>' and '<em>M</em>', will take you back to the starting
+  document unless you specified the <em>-homepage=URL</em> option
+  at the command line. Also, the LIST and ADDRLIST keystroke
+  commands, normally mapped to '<em>l</em>' and <em>A</em>'
+  respectively, will create a compact lists of all the links in the
+  current document, and they can be selected via those lists.</p>
 
   <p>The '<em>i</em>' key presents an index of documents. The
   default index offered contains many useful links, but can be
@@ -521,14 +532,16 @@ can be selected via those lists.
     <dd><code>lynx file://localhost/FULL/PATH/FILENAME</code></dd>
 
     <dd><code>lynx path/filename.html</code></dd>
-  </dl>In addition, the user must also specify an editor in the
+  </dl>
+
+  <p>In addition, the user must also specify an editor in the
   <em>Options Menu</em> so that Lynx knows which editor to use. If
   the file is specified correctly and an editor is defined, then
   you may edit documents by using the '<em>e</em>' command. When
   the '<em>e</em>' command is entered your specified editor is
   spawned to edit the file. After changes are completed, exit your
   editor and you will return to Lynx. Lynx will reload and render
-  the file so that changes can be immediately examined.
+  the file so that changes can be immediately examined.</p>
 
   <p>[<a href="#ToC-LocalSource">ToC</a>]</p>
 
@@ -556,11 +569,14 @@ can be selected via those lists.
   will be that Lynx optionally puts</p>
 
   <blockquote>
-    &lt;!--X-URL: http://www.site.foo/path/to/file.html --&gt;<br>
-    &lt;BASE href="http://www.site.foo/path/to/file.html"&gt;
-  </blockquote>at the start of the file so that relative URLs in
-  the document will still work. Even this modification can be
-  prevented by setting PREPEND_BASE_TO_SOURCE:FALSE in lynx.cfg.
+    <p>&lt;!--X-URL: http://www.site.foo/path/to/file.html
+    --&gt;<br>
+    &lt;BASE href="http://www.site.foo/path/to/file.html"&gt;</p>
+  </blockquote>
+
+  <p>at the start of the file so that relative URLs in the document
+  will still work. Even this modification can be prevented by
+  setting PREPEND_BASE_TO_SOURCE:FALSE in lynx.cfg.</p>
 
   <p>Some options, such as <em>Save to disk</em>, involve prompting
   for an output filename. All output filename entries are saved in
@@ -643,8 +659,10 @@ can be selected via those lists.
   <pre>
       <em>&lt;ISINDEX PROMPT="Enter WAIS query:"
                HREF="wais://net.bio.net/biologists-addresses"&gt;</em>
-</pre>for submitting a search of the Biologist's Addresses database
-directly to the net.bio.net WAIS server.
+</pre>
+
+  <p>for submitting a search of the Biologist's Addresses database
+  directly to the net.bio.net WAIS server.</p>
 
   <p>[<a href="#ToC-Search">ToC</a>]</p>
 
@@ -663,7 +681,6 @@ directly to the net.bio.net WAIS server.
   generated at runtime, in which the user fills in choices as in
   any ordinary HTML form.</p>
   <pre>
-
                     Options Menu (Lynx Version 2.8.7rel.1)
 
       Accept Changes - Reset Changes Left Arrow cancels changes <a href="keystrokes/option_help.html">HELP!</a>
@@ -746,7 +763,6 @@ directly to the net.bio.net WAIS server.
   accessed by setting FORMS_OPTIONS to TRUE in <a href=
   "#lynx.cfg">lynx.cfg</a>.</p>
   <pre>
-
              Options Menu (Lynx Version 2.8.7rel.1)
 
      (E)ditor                     : emacs
@@ -767,15 +783,18 @@ directly to the net.bio.net WAIS server.
      (U)ser mode                  : Advanced      verbose images (!) : ON
      user (A)gent                 : [User-Agent header]
      local e(X)ecution links      : FOR LOCAL FILES ONLY
-</pre>An option can be changed by entering the capital letter or
-character in parentheses for the option you wish to change (e.g.,
-'<em>E</em>' for Editor or '<em>@</em>' for show cursor). For
-fields where text must be entered, simply enter the text by typing
-on the keyboard. The <a href="keystrokes/edit_help.html">Line
-Editor</a> can be used to correct mistakes, and <em>Control-U</em>
-can be used to erase the line. When you are done entering a change
-press the <em>Return</em> key to get back to the <em>Command?</em>
-prompt.
+</pre>
+
+  <p>An option can be changed by entering the capital letter or
+  character in parentheses for the option you wish to change (e.g.,
+  '<em>E</em>' for Editor or '<em>@</em>' for show cursor). For
+  fields where text must be entered, simply enter the text by
+  typing on the keyboard. The <a href=
+  "keystrokes/edit_help.html">Line Editor</a> can be used to
+  correct mistakes, and <em>Control-U</em> can be used to erase the
+  line. When you are done entering a change press the
+  <em>Return</em> key to get back to the <em>Command?</em>
+  prompt.</p>
 
   <p>For fields where you must choose one of two choices, press any
   key to toggle the choices and press the <em>Return</em> key to
@@ -1470,12 +1489,14 @@ prompt.
     &lt;LINK REV="made" HREF="mailto:user@somedomain.com"&gt;
     &hellip;
 &lt;/HEAD&gt;
-</pre>You may also add a TITLE attribute with, for example, the
-name of your page) If no ownership is specified then comments are
-disabled. Certain links called <a href=
-"lynx_url_support.html#mailto_url">mailto:</a> links will also
-allow you to send mail to other people. Using the mail features
-within Lynx is straightforward.
+</pre>
+
+  <p>You may also add a TITLE attribute with, for example, the name
+  of your page) If no ownership is specified then comments are
+  disabled. Certain links called <a href=
+  "lynx_url_support.html#mailto_url">mailto:</a> links will also
+  allow you to send mail to other people. Using the mail features
+  within Lynx is straightforward.</p>
 
   <p>Once you have decided to send a comment or have selected a
   <em>mailto:</em> link a new screen will appear showing you to
@@ -1536,8 +1557,10 @@ within Lynx is straightforward.
     information about the URL schemes for posting or sending
     followups (replies) to nntp servers with Lynx. [<a href=
     "#ToC-News">ToC</a>]</dd>
-  </dl>See also <a href=
-  "http://www.w3.org/Protocols/rfc977/rfc977">RFC 977</a>.
+  </dl>
+
+  <p>See also <a href=
+  "http://www.w3.org/Protocols/rfc977/rfc977">RFC 977</a>.</p>
 
   <h2 id="id-Bookmarks"><a name="Bookmarks" id="Bookmarks"><em>Lynx
   bookmarks</em></a></h2>
@@ -1554,11 +1577,14 @@ within Lynx is straightforward.
   asked:</p>
 
   <blockquote>
-    Save D)ocument or L)ink to bookmark file or C)ancel? (d,l,c):
-  </blockquote>Answer '<em>d</em>' to save a link to the document
-  you are currently viewing or '<em>l</em>' to save the link that
-  is currently selected on the page. Selecting '<em>c</em>' will
-  cancel without saving anything to your bookmark file.
+    <p>Save D)ocument or L)ink to bookmark file or C)ancel?
+    (d,l,c):</p>
+  </blockquote>
+
+  <p>Answer '<em>d</em>' to save a link to the document you are
+  currently viewing or '<em>l</em>' to save the link that is
+  currently selected on the page. Selecting '<em>c</em>' will
+  cancel without saving anything to your bookmark file.</p>
 
   <p>A bookmark file will be created in conjunction with acting on
   the '<em>a</em>'dd command if it does not already exist.
@@ -2096,9 +2122,11 @@ within Lynx is straightforward.
       to use, it might for example say
       <pre>
           <strong>(Textarea) Enter text. </strong>[ ..... ]<strong> (^Xe for editor).</strong>
-</pre>An external editor has to be defined, for example in the
-<a href="#InteractiveOptions">Options Menu</a>, before you can
-start using this function.
+</pre>
+
+      <p>An external editor has to be defined, for example in the
+      <a href="#InteractiveOptions">Options Menu</a>, before you
+      can start using this function.</p>
 
       <p>A key to invoke external TEXTAREA editing is normally
       provided by the <a href=
@@ -2156,11 +2184,13 @@ start using this function.
       which libraries are used, and behavior of the connection and
       terminal type).</p>
     </dd>
-  </dl>In general, you can move around the form using the standard
+  </dl>
+
+  <p>In general, you can move around the form using the standard
   Lynx navigation keys. The <em>up-arrow</em> and
   <em>down-arrow</em> keys, respectively, select the previous or
   next field, box, or button. The <em>TAB</em> key selects the next
-  field, box, or button.
+  field, box, or button.</p>
 
   <p>To <a name="submit" id="submit"><em>submit</em></a> the form
   press <em>right-arrow</em> or <em>Return</em> when positioned on
@@ -2177,8 +2207,10 @@ start using this function.
   <pre>
       <em>&lt;META HTTP-EQUIV="Pragma" CONTENT="no-cache"&gt;</em>
       <em>&lt;META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"&gt;</em>
-</pre>or the server sent a "Pragma" or "Cache-Control" MIME header
-with a no-cache directive.
+</pre>
+
+  <p>or the server sent a "Pragma" or "Cache-Control" MIME header
+  with a no-cache directive.</p>
 
   <p>You also can use the DOWNLOAD ('<em>d</em>') keystroke command
   when positioned on a form submit button if you wish to download
@@ -2417,7 +2449,9 @@ the other two cannot be saved between sessions.
 
       <li>Most attributes are ignored, including borders,
       <code>WIDTH</code>, vertical alignment.</li>
-    </ul>Horizontal alignments (<code>LEFT</code>,
+    </ul>
+
+    <p>Horizontal alignments (<code>LEFT</code>,
     <code>CENTER</code>, <code>RIGHT</code>), <code>COLSPAN</code>,
     and <code>ROWSPAN</code> are interpreted according to HTML
     4.01. (<code>ROWSPAN</code> can only reserve empty space in
@@ -2431,7 +2465,7 @@ the other two cannot be saved between sessions.
     within table cells) and not essential for understanding the
     textual contents, it remains basically ignored. Some more
     information on details is available in the file
-    <kbd>README.TRST</kbd> of the source distribution.
+    <kbd>README.TRST</kbd> of the source distribution.</p>
   </div>
 
   <p>For tabular display of more complex tables, Lynx users can
@@ -2601,8 +2635,10 @@ the other two cannot be saved between sessions.
   <pre>
         See the <em>&lt;A HREF="#fn1"&gt;</em><a href=
 "#an1">footnote</a><em>&lt;/A&gt;</em>.
-</pre>activating that link will take you to the labeled rendering
-of:
+</pre>
+
+  <p>activating that link will take you to the labeled rendering
+  of:</p>
   <pre>
         <em>&lt;FN ID="fn1"&gt;</em>&lt;p&gt;<a name="an1" id=
 "an1">Lynx does not use popups for FN blocks.</a>&lt;/p&gt;<em>&lt;/FN&gt;</em>
@@ -2640,9 +2676,11 @@ of:
       <em>&lt;NOTE CLASS="warning" ID="too-bad"&gt;
         &lt;p&gt;The W3C vendors did not retain NOTE in the HTML 3.2 draft.&lt;/p&gt;
       &lt;/NOTE&gt;</em>
-</pre>It will <em>degrade gracefully</em> for WWW browsers which do
-not support NOTE, except for recognition of the ID attribute as a
-named <em>A</em>nchor.
+</pre>
+
+  <p>It will <em>degrade gracefully</em> for WWW browsers which do
+  not support NOTE, except for recognition of the ID attribute as a
+  named <em>A</em>nchor.</p>
 
   <p>[<a href="#ToC-Notes">ToC</a>]</p>
 
@@ -2854,11 +2892,13 @@ named <em>A</em>nchor.
   <em>client-side-pull</em>. An example of such an element is:</p>
   <pre>
       <em>&lt;META HTTP-EQUIV="Refresh" CONTENT="3; URL=http://host/path"&gt;</em>
-</pre>which instructs a client to fetch the indicated URL in 3
-seconds after receiving the current document. If the <em>URL=</em>
-field is omitted, the URL defaults to that of the current document.
-A <em>no-cache</em> directive is implied when the <em>Refresh</em>
-if for the same URL.
+</pre>
+
+  <p>which instructs a client to fetch the indicated URL in 3
+  seconds after receiving the current document. If the
+  <em>URL=</em> field is omitted, the URL defaults to that of the
+  current document. A <em>no-cache</em> directive is implied when
+  the <em>Refresh</em> if for the same URL.</p>
 
   <p>Lynx recognizes and processes <em>Refresh</em> directives in
   META elements, but puts up a labeled link, typically in the upper
@@ -3079,7 +3119,9 @@ if for the same URL.
     <dd><code>lynx [options]</code></dd>
 
     <dd><code>lynx [options] startfile</code></dd>
-  </dl>where
+  </dl>
+
+  <p>where</p>
 
   <dl>
     <dt><code>startfile</code></dt>
@@ -3129,9 +3171,11 @@ if for the same URL.
               -center:off
               -center=off
               -center-</code>
-</pre>Lynx recognizes "1", "+", "on" and "true" for true values,
-and "0", "-", "off" and "false" for false values. Other
-option-values are ignored.
+</pre>
+
+      <p>Lynx recognizes "1", "+", "on" and "true" for true values,
+      and "0", "-", "off" and "false" for false values. Other
+      option-values are ignored.</p>
 
       <p>The default boolean, number and string option values that
       are compiled into lynx are displayed in the help-message
@@ -4006,10 +4050,12 @@ option-values are ignored.
 <tt>
                     lynx -source . &gt;foo.html
                     </tt>
-</pre>generates HTML source listing the files in the current
-directory. Each file is marked by an HREF relative to the parent
-directory. Add a trailing slash to make the HREF's relative to the
-current directory:
+</pre>
+
+          <p>generates HTML source listing the files in the current
+          directory. Each file is marked by an HREF relative to the
+          parent directory. Add a trailing slash to make the HREF's
+          relative to the current directory:</p>
           <pre>
 <tt>
                     lynx -source ./ &gt;foo.html
diff --git a/lynx_help/about_lynx.html b/lynx_help/about_lynx.html
index 4243bb43..e740aca2 100644
--- a/lynx_help/about_lynx.html
+++ b/lynx_help/about_lynx.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: about_lynx.html,v 1.16 2012/01/31 10:51:52 tom Exp $ -->
+<!-- $LynxId: about_lynx.html,v 1.18 2013/05/22 00:57:45 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>About Lynx</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -14,9 +14,9 @@
 
 <body>
   <blockquote>
-    [ <a href="lynx-dev.html">About Lynx-Dev</a> | <a href=
+    <p>[ <a href="lynx-dev.html">About Lynx-Dev</a> | <a href=
     "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Lynx-Dev
-    Archives</a> ]
+    Archives</a> ]</p>
   </blockquote>
 
   <h1><em>About Lynx</em></h1>
@@ -70,11 +70,12 @@
   are copyrighted by other institutions or individuals. The Lynx
   copyright does not override or invalidate those copyrights.</p>
 
-  <p>Thanks to <a name="13" href=
-  "http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a> and
-  the other <a name="14" href="http://www.w3.org/People.html">CERN
-  World Wide Web wizards</a> for the WWW client library code and
-  all of their other work on the WWW project, NCSA and the <a href=
+  <p>Thanks to <a name="note13" href=
+  "http://www.w3.org/People/Berners-Lee/" id="note13">Tim
+  Berners-Lee</a> and the other <a name="note14" href=
+  "http://www.w3.org/People.html" id="note14">CERN World Wide Web
+  wizards</a> for the WWW client library code and all of their
+  other work on the WWW project, NCSA and the <a href=
   "http://archive.ncsa.uiuc.edu/SDG/Software/Mosaic/NCSAMosaicHome.html">
   Mosaic</a> developers, and to everyone out in netland who has
   contributed to Lynx's development either directly (through
@@ -91,13 +92,15 @@
   which did not use the WWW libraries and had their own hypertext
   format.</p>
 
-  <h2><a name="availability"><em>Availability</em></a></h2>
+  <h2><a name="availability" id=
+  "availability"><em>Availability</em></a></h2>
 
   <p>Information on obtaining the most current version of Lynx is
-  available via <a href="http://www.subir.com/lynx.html">Lynx
-  links</a>.</p>
+  available via the <a href="http://lynx.isc.org">Lynx
+  homepage</a>.</p>
 
-  <h2><a name="lynx-dev_list"><em>Mailing List</em></a></h2>
+  <h2><a name="lynx-dev_list" id="lynx-dev_list"><em>Mailing
+  List</em></a></h2>
 
   <p>We have a mailing list for lynx development discussion. If you
   are interested in joining the list, follow this <a href=
diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html
index 690537a0..5eed64e5 100644
--- a/lynx_help/keystrokes/alt_edit_help.html
+++ b/lynx_help/keystrokes/alt_edit_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: alt_edit_help.html,v 1.9 2012/01/31 23:22:53 tom Exp $ -->
+<!-- $LynxId: alt_edit_help.html,v 1.10 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Line Editor Alternative Key Binding</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -56,7 +56,7 @@
 
      LKCMD  Invoke cmd prompt     -  Ctrl-V (in form text fields, only) [2]
 
-<a name=
+<a name="TASpecial" id=
 "TASpecial">Special commands for use only in textarea fields</a>[3]:
 
           Textarea external edit  - Ctrl-X e
diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html
index 14a3a4ff..bb175990 100644
--- a/lynx_help/keystrokes/bashlike_edit_help.html
+++ b/lynx_help/keystrokes/bashlike_edit_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: bashlike_edit_help.html,v 1.8 2012/01/31 23:21:55 tom Exp $ -->
+<!-- $LynxId: bashlike_edit_help.html,v 1.9 2013/05/22 00:25:19 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Line Editor Bash-Like Key Binding</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -60,7 +60,7 @@
      LKCMD  Invoke cmd prompt     -  C-v [FORM]
      SWMAP  Switch input keymap   -  C-^ (if compiled in)
 
-<a name=
+<a name="TASpecial" id=
 "TASpecial">Special commands for use in textarea fields</a> [FORM]:
 
      PASS!  Textarea external edit  - C-e C-e [4], C-x e
@@ -68,15 +68,16 @@
      PASS!  Grow textarea           - C-x g
 </pre>
 
-  <p>Here is a little textarea for practice:<br></p>
+  <p>Here is a little textarea for practice:</p>
 
   <form action="">
+    <p>
     <textarea name="practice" cols="40" rows="5">
 This text cannot be submitted.  Normally lines like
 these would be part of a form that is filled out and
 then submitted.  You can move around here and delete
 or add text as you like, using the Line-Editor keys.
-</textarea><input type="reset" value="[reset content]">
+</textarea><input type="reset" value="[reset content]"></p>
   </form>
   <pre>
 
diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html
index df5adad1..66eafbf6 100644
--- a/lynx_help/keystrokes/bookmark_help.html
+++ b/lynx_help/keystrokes/bookmark_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: bookmark_help.html,v 1.6 2012/01/31 11:00:10 tom Exp $ -->
+<!-- $LynxId: bookmark_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Bookmark Help</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html
index ad4c4240..60920128 100644
--- a/lynx_help/keystrokes/cookie_help.html
+++ b/lynx_help/keystrokes/cookie_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: cookie_help.html,v 1.7 2012/01/31 23:19:37 tom Exp $ -->
+<!-- $LynxId: cookie_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on the Cookie Jar Page</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html
index a692c1b9..c5cb3dbc 100644
--- a/lynx_help/keystrokes/dired_help.html
+++ b/lynx_help/keystrokes/dired_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: dired_help.html,v 1.7 2012/01/31 23:19:02 tom Exp $ -->
+<!-- $LynxId: dired_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Dired Help</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/edit_help.html b/lynx_help/keystrokes/edit_help.html
index d18eb255..7fa146d8 100644
--- a/lynx_help/keystrokes/edit_help.html
+++ b/lynx_help/keystrokes/edit_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: edit_help.html,v 1.13 2012/01/31 23:17:33 tom Exp $ -->
+<!-- $LynxId: edit_help.html,v 1.14 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Line Editor Default Key Binding</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -57,7 +57,7 @@
      LKCMD  Invoke cmd prompt     -  Ctrl-V (in form text fields, only) [2]
      SWMAP  Switch input keymap   -  Ctrl-^ (if compiled in)
 
-<a name=
+<a name="TASpecial" id=
 "TASpecial">Special commands for use only in textarea fields</a>[3]:
 
           Textarea external edit  - Ctrl-X e
diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html
index c6988b0c..e898ef47 100644
--- a/lynx_help/keystrokes/environments.html
+++ b/lynx_help/keystrokes/environments.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: environments.html,v 1.14 2012/01/31 23:25:10 tom Exp $ -->
+<!-- $LynxId: environments.html,v 1.15 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on Environment variables</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -35,7 +35,7 @@
 "#dos">win32/dos</a> specific
        variables.
 
-<a name="env"><em>
+<a name="env" id="env"><em>
 Environment Variables Used By Lynx:
 </em></a>
        COLORTERM
@@ -162,7 +162,7 @@ Environment Variables Used By Lynx:
                            the default startup URL  specified  in
                            any of the Lynx configuration files.
 
-<a name="setenv"><em>
+<a name="setenv" id="setenv"><em>
 Environment Variables Set or Modified By Lynx:
 </em></a>
 
@@ -237,7 +237,7 @@ Environment Variables Set or Modified By Lynx:
                            variables may also be changed.
 
 
-<a name="cgi"><em>
+<a name="cgi" id="cgi"><em>
 SIMULATED CGI SUPPORT
 </em></a>
        If built with the cgi-links option  enabled,  Lynx  allows
@@ -284,7 +284,7 @@ SIMULATED CGI SUPPORT
        should be consulted for general information on CGI  script
        programming.
 
-<a name="language"><em>
+<a name="language" id="language"><em>
 NATIVE LANGUAGE SUPPORT
 </em></a>
        If  configured and installed with Native Language Support,
@@ -323,7 +323,7 @@ NATIVE LANGUAGE SUPPORT
        NLSPATH             This variable, if set, is used as  the
                            path prefix for message catalogs.
 
-<a name="proxy"><em>
+<a name="proxy" id="proxy"><em>
 Proxy details and examples:
 </em></a>
 
@@ -430,7 +430,7 @@ Proxy details and examples:
     you can set them at run time via the configuration file lynx.cfg
     (this will not override external settings).
 
-<a name="dos"><em>
+<a name="dos" id="dos"><em>
 Win32 (95/NT) and 386 DOS
 </em></a>
   (adapted from "readme.txt" by Wayne Buttles
diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html
index 394b3553..ff3b8a66 100644
--- a/lynx_help/keystrokes/follow_help.html
+++ b/lynx_help/keystrokes/follow_help.html
@@ -1,10 +1,10 @@
+<!-- $LynxId: follow_help.html,v 1.11 2013/05/21 10:51:27 tom Exp $ -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<!-- $LynxId: follow_help.html,v 1.10 2012/01/31 23:16:38 tom Exp $ -->
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on the Follow link (or page) number feature</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/gopher_types_help.html b/lynx_help/keystrokes/gopher_types_help.html
index 5af38dbd..f524dd1d 100644
--- a/lynx_help/keystrokes/gopher_types_help.html
+++ b/lynx_help/keystrokes/gopher_types_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: gopher_types_help.html,v 1.7 2012/01/31 23:15:38 tom Exp $ -->
+<!-- $LynxId: gopher_types_help.html,v 1.8 2013/05/21 10:59:47 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Listing of Gopher types</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -15,7 +15,7 @@
 <body>
   <h1>Gopher Types</h1>
 
-  <dl compact>
+  <dl>
     <dt>(FILE)</dt>
 
     <dd>An ASCII file</dd>
diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html
index f8f4566a..f3728502 100644
--- a/lynx_help/keystrokes/history_help.html
+++ b/lynx_help/keystrokes/history_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: history_help.html,v 1.5 2012/01/31 23:14:48 tom Exp $ -->
+<!-- $LynxId: history_help.html,v 1.6 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on the History Page</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html
index 01855e3d..05c94246 100644
--- a/lynx_help/keystrokes/keystroke_help.html
+++ b/lynx_help/keystrokes/keystroke_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: keystroke_help.html,v 1.17 2012/01/31 23:25:43 tom Exp $ -->
+<!-- $LynxId: keystroke_help.html,v 1.18 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on Lynx Keystroke Commands</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html
index a08534b9..7e7f7247 100644
--- a/lynx_help/keystrokes/movement_help.html
+++ b/lynx_help/keystrokes/movement_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: movement_help.html,v 1.6 2012/01/31 23:24:18 tom Exp $ -->
+<!-- $LynxId: movement_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on Lynx Movement commands</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html
index 7854b8af..b9baf83d 100644
--- a/lynx_help/keystrokes/option_help.html
+++ b/lynx_help/keystrokes/option_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: option_help.html,v 1.24 2012/01/31 23:12:34 tom Exp $ -->
+<!-- $LynxId: option_help.html,v 1.25 2013/05/21 10:58:35 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Form-based Options Menu : Help</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -116,13 +116,13 @@
     </li>
   </ul>
 
-  <h1><a name="CK">Cookies</a></h1>
+  <h1><a name="CK" id="CK">Cookies</a></h1>
 
   <p>This can be set to accept or reject all cookies or to ask each
   time. See the Users Guide for details of <a href=
   "../Lynx_users_guide.html#Cookies">cookie usage</a>.</p>
 
-  <h1><a name="ED">Editor</a></h1>
+  <h1><a name="ED" id="ED">Editor</a></h1>
 
   <p>This is the editor to be invoked when editing browsable files,
   sending mail or comments, or filling form's textarea (multiline
@@ -131,7 +131,7 @@
   the same character set you have for "display character set" in
   Lynx.</p>
 
-  <h1><a name="EM">Emacs keys</a></h1>
+  <h1><a name="EM" id="EM">Emacs keys</a></h1>
 
   <p>If set to 'ON' then the CTRL-P, CTRL-N, CTRL-F and CTRL-B keys
   will be mapped to up-arrow, down-arrow, right-arrow and
@@ -142,14 +142,14 @@
   <p>Note: setting emacs keys does not affect the line-editor
   bindings.</p>
 
-  <h1><a name="LL">Execution links</a></h1>
+  <h1><a name="LL" id="LL">Execution links</a></h1>
 
   <p>If set to 'ALWAYS ON', Lynx will locally execute commands
   contained inside any links. This can be HIGHLY DANGEROUS, so it
   is recommended that they remain 'ALWAYS OFF' or 'FOR LOCAL FILES
   ONLY'.</p>
 
-  <h1><a name="KM">Keypad mode</a></h1>
+  <h1><a name="KM" id="KM">Keypad mode</a></h1>
 
   <p>This gives the choice between navigating with the keypad (as
   arrows; see Lynx Navigation) and having every link numbered
@@ -157,21 +157,21 @@
   instead of moving to them with the arrow keys. You can also
   number form fields.</p>
 
-  <h1><a name="LE">Line edit style</a></h1>
+  <h1><a name="LE" id="LE">Line edit style</a></h1>
 
   <p>This allows you to set alternate key bindings for the built-in
   line editor, if <a href="alt_edit_help.html">Alternate
   Bindings</a> have been installed. Otherwise, Lynx uses the
   <a href="edit_help.html">Default Binding</a>.</p>
 
-  <h1><a name="PM">Personal Mail Address</a></h1>
+  <h1><a name="PM" id="PM">Personal Mail Address</a></h1>
 
   <p>You may set your mail address here so that when mailing
   messages to other people or mailing files to yourself, your email
   address can be automatically filled in. Your email address will
   also be sent to HTTP servers in a `from:' field.</p>
 
-  <h1><a name="PU">Pop-ups for select fields</a></h1>
+  <h1><a name="PU" id="PU">Pop-ups for select fields</a></h1>
 
   <p>Lynx normally uses a pop-up window for the OPTIONs in form
   SELECT fields when the field does not have the MULTIPLE attribute
@@ -182,13 +182,13 @@
   attribute specified, the OPTIONs always are rendered as a list of
   checkboxes.</p>
 
-  <h1><a name="ST">Searching type</a></h1>
+  <h1><a name="ST" id="ST">Searching type</a></h1>
 
   <p>If set to 'case sensitive', user searches invoked by '/' will
   be case-sensitive substring searches. Default is 'Case
   Insensitive'.</p>
 
-  <h1><a name="SC">Show color</a></h1>
+  <h1><a name="SC" id="SC">Show color</a></h1>
 
   <p>This will be present if color support is available.</p>
 
@@ -204,13 +204,16 @@
     saved to a '.lynxrc' file in non-anonymous accounts, ALWAYS
     will cause Lynx to set color mode on at startup if
     supported.</li>
-  </ul>If Lynx is built with slang, this is equivalent to having
+  </ul>
+
+  <p>If Lynx is built with slang, this is equivalent to having
   included the -color command line switch or having the COLORTERM
   environment variable set. If color support is provided by curses
   or ncurses, this is equivalent to the default behavior of using
   color when the terminal type supports it. If (n)curses color
   support is available but cannot be used for the current terminal
-  type, the preference can still be saved but will have no effect.
+  type, the preference can still be saved but will have no
+  effect.</p>
 
   <p>A saved value of NEVER will cause Lynx to assume a monochrome
   terminal at start-up. It is similar to the -nocolor switch, but
@@ -226,7 +229,8 @@
   color mode is incorrect for your terminal, set it appropriately
   on or off via this option.</p>
 
-  <h1><a name="CL">Show cursor for current link or option</a></h1>
+  <h1><a name="CL" id="CL">Show cursor for current link or
+  option</a></h1>
 
   <p>Lynx normally hides the cursor by positioning it to the right
   and if possible the very bottom of the screen, so that the
@@ -238,7 +242,7 @@
   character attributes used to distinguish the current link or
   OPTION from the others in the display.</p>
 
-  <h1><a name="UM">User Mode</a></h1>
+  <h1><a name="UM" id="UM">User Mode</a></h1>
 
   <dl>
     <dt><em>Novice</em>: Shows 2 extra lines of help at the bottom
@@ -251,7 +255,7 @@
     line.</dt>
   </dl>
 
-  <h1><a name="AD">Assumed document character set</a></h1>
+  <h1><a name="AD" id="AD">Assumed document character set</a></h1>
 
   <p>This changes the handling of documents which do not explicitly
   specify a charset. Normally Lynx assumes that 8-bit characters in
@@ -264,7 +268,7 @@
   they were encoded accordingly. Option is active when 'Raw 8-bit
   or CJK Mode' is OFF.</p>
 
-  <h1><a name="JK">Raw 8-bit or CJK mode</a></h1>
+  <h1><a name="JK" id="JK">Raw 8-bit or CJK mode</a></h1>
 
   <p>This is set automatically, but can be toggled manually in
   certain cases: it toggles whether 8-bit characters are assumed to
@@ -283,7 +287,7 @@
   setting can also be toggled via the RAW_TOGGLE command, normally
   mapped to '@', and at startup via the -raw switch.</p>
 
-  <h1><a name="tagsoup">HTML error recovery</a></h1>
+  <h1><a name="tagsoup" id="tagsoup">HTML error recovery</a></h1>
 
   <p>Lynx often has to deal with invalid HTML markup. It always
   tries to recover from errors, but there is no universally correct
@@ -329,7 +333,7 @@ Default recovery mode can also be switched with CTRL-V key,
 from lynx.cfg or command line switch.
 --></p>
 
-  <h1><a name="SI">Show Images</a></h1>
+  <h1><a name="SI" id="SI">Show Images</a></h1>
 
   <p>This option combines the effects of the `*' &amp; `[' keys as
   follows:</p>
@@ -343,16 +347,17 @@ from lynx.cfg or command line switch.
   <a href="../Lynx_users_guide.html#Images">Users Guide</a> &amp;
   <em>lynx.cfg</em> for more details.</p>
 
-  <h1><a name="VB">Verbose Images</a></h1>
+  <h1><a name="VB" id="VB">Verbose Images</a></h1>
 
-  <p>This allows you to replace [LINK], [INLINE] and [IMAGE] &mdash; for
-  images without ALT &mdash; with filenames: this can be helpful by
-  revealing which images are important &amp; which are merely
-  decoration, e.g. <em>button.gif</em>, <em>line.gif</em>. See
-  <a href="../Lynx_users_guide.html#Images">Users Guide</a> &amp;
+  <p>This allows you to replace [LINK], [INLINE] and [IMAGE]
+  &mdash; for images without ALT &mdash; with filenames: this can
+  be helpful by revealing which images are important &amp; which
+  are merely decoration, e.g. <em>button.gif</em>,
+  <em>line.gif</em>. See <a href=
+  "../Lynx_users_guide.html#Images">Users Guide</a> &amp;
   <em>lynx.cfg</em> for more details.</p>
 
-  <h1><a name="VI">VI keys</a></h1>
+  <h1><a name="VI" id="VI">VI keys</a></h1>
 
   <p>If set to 'ON' then the lowercase h, j, k and l keys will be
   mapped to left-arrow, down-arrow, up-arrow and right-arrow
@@ -365,7 +370,7 @@ from lynx.cfg or command line switch.
   <p>Note: setting vi keys does not affect the line-editor
   bindings.</p>
 
-  <h1><a name="DC">Display Character set</a></h1>
+  <h1><a name="DC" id="DC">Display Character set</a></h1>
 
   <p>This allows you to set up the default character set for your
   specific terminal. The display character set provides a mapping
@@ -379,14 +384,14 @@ from lynx.cfg or command line switch.
   computers, and windows-xxxx within native MS-Windows
   applications.</p>
 
-  <h1><a name="DV">X DISPLAY variable</a></h1>
+  <h1><a name="DV" id="DV">X DISPLAY variable</a></h1>
 
   <p>This option is only relevant to X Window users. It specifies
   the DISPLAY (Unix) or DECW$DISPLAY (VMS) variable. It is picked
   up automatically from the environment if it has been previously
   set.</p>
 
-  <h1><a name="MB">Multi-bookmarks</a></h1>
+  <h1><a name="MB" id="MB">Multi-bookmarks</a></h1>
 
   <p>Manage multiple bookmark files:</p>
 
@@ -405,7 +410,7 @@ from lynx.cfg or command line switch.
     file.</li>
   </ul>
 
-  <h1><a name="BF">Bookmark file</a></h1>
+  <h1><a name="BF" id="BF">Bookmark file</a></h1>
 
   <p>Manage the default bookmark file:</p>
 
@@ -416,14 +421,16 @@ from lynx.cfg or command line switch.
     <li>If multi-bookmarks is STANDARD or ADVANCED, entering 'B'
     will invoke a menu in which you can specify filepaths and
     descriptions of up to 26 bookmark files.</li>
-  </ul>The filepaths must be from your home directory and begin
-  with './' if subdirectories are included (e.g.,
-  './BM/lynx_bookmarks.html').
+  </ul>
+
+  <p>The filepaths must be from your home directory and begin with
+  './' if subdirectories are included (e.g.,
+  './BM/lynx_bookmarks.html').</p>
 
   <p>Lynx will create bookmark files when you first 'a'dd a link,
   but any subdirectories in the filepath must already exist.</p>
 
-  <h1><a name="VP">Visited Pages</a></h1>
+  <h1><a name="VP" id="VP">Visited Pages</a></h1>
 
   <p>This allows you to change the appearance of the <a href=
   "visited_help.html">Visited Links Page</a> Normally it shows a
@@ -459,13 +466,13 @@ from lynx.cfg or command line switch.
     bottom of the list.</dt>
   </dl>
 
-  <h1><a name="FT">FTP sort criteria</a></h1>
+  <h1><a name="FT" id="FT">FTP sort criteria</a></h1>
 
   <p>This allows you to specify how files will be sorted within FTP
   listings. The current options include `By&nbsp;Filename',
   `By&nbsp;Size', `By&nbsp;Type', `By&nbsp;Date'.</p>
 
-  <h1><a name="LD">List directory style</a></h1>
+  <h1><a name="LD" id="LD">List directory style</a></h1>
 
   <p>Applies to Directory Editing. Files and directories can be
   presented in the following ways:</p>
@@ -482,12 +489,12 @@ from lynx.cfg or command line switch.
     into 2 alphabetical lists: files are listed first.</dt>
   </dl>
 
-  <h1><a name="DF">Show dot files</a></h1>
+  <h1><a name="DF" id="DF">Show dot files</a></h1>
 
   <p>If display/creation of hidden (dot) files/directories is
   enabled, you can turn the feature on or off via this setting.</p>
 
-  <h1><a name="PC">Preferred Document Charset</a></h1>
+  <h1><a name="PC" id="PC">Preferred Document Charset</a></h1>
 
   <p>The character set you prefer if sets in addition to ISO-8859-1
   and US-ASCII are available from servers. Use MIME notation (e.g.,
@@ -499,7 +506,7 @@ from lynx.cfg or command line switch.
   protocol, for servers which understand it: e.g., <kbd>iso-8859-5,
   utf-8;q=0.8</kbd>.</p>
 
-  <h1><a name="PL">Preferred Document Language</a></h1>
+  <h1><a name="PL" id="PL">Preferred Document Language</a></h1>
 
   <p>The language you prefer if multi-language files are available
   from servers. Use RFC 1766 tags, e.g., `en' English, `fr' French.
@@ -507,7 +514,7 @@ from lynx.cfg or command line switch.
   previous help item): e.g., <kbd>da, en-gb;q=0.8, en;q=0.7</kbd>
   .</p>
 
-  <h1><a name="UA">User Agent</a></h1>
+  <h1><a name="UA" id="UA">User Agent</a></h1>
 
   <p>The header string which Lynx sends to servers to indicate the
   User-Agent is displayed here. Changes may be disallowed via the
diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html
index 866c4d9a..c43be74d 100644
--- a/lynx_help/keystrokes/other_help.html
+++ b/lynx_help/keystrokes/other_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: other_help.html,v 1.12 2012/01/31 23:23:40 tom Exp $ -->
+<!-- $LynxId: other_help.html,v 1.13 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on Misc. Lynx Commands</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html
index b6f14003..2e1b7c05 100644
--- a/lynx_help/keystrokes/print_help.html
+++ b/lynx_help/keystrokes/print_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: print_help.html,v 1.6 2012/01/31 11:56:00 tom Exp $ -->
+<!-- $LynxId: print_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Print Help</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html
index 872991c5..ffa121fb 100644
--- a/lynx_help/keystrokes/scrolling_help.html
+++ b/lynx_help/keystrokes/scrolling_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: scrolling_help.html,v 1.8 2012/01/31 11:53:58 tom Exp $ -->
+<!-- $LynxId: scrolling_help.html,v 1.9 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx Scrolling Help</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html
index 51dbbedb..34d66e61 100644
--- a/lynx_help/keystrokes/test_display.html
+++ b/lynx_help/keystrokes/test_display.html
@@ -1,58 +1,64 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN">
-<!-- $LynxId: test_display.html,v 1.7 2012/01/31 11:53:11 tom Exp $ -->
+<!-- $LynxId: test_display.html,v 1.8 2013/05/21 10:56:48 tom Exp $ -->
 <!-- do not use tidy for this page -->
-<HTML>
-<HEAD>
-<TITLE>Quick test for identifying display character set</TITLE>
-<LINK rev="made" href="mailto:lynx-dev@nongnu.org">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<h1 ALIGN=LEFT>Try this page with Lynx 2.7.2 or above:</h1>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
-If you see several letters instead of a single - your promised display charset
-does not support this character so "7 bit approximation" is in effect.
-If you see any single letter which definitely far from being supposed
-you have a wrong lynx settings.
-<em>Press 'o' for Options menu and change "Display character set"</em>.
-Try again if necessary.<br>
-When you are satisfied save your changes in Options menu, thanks.
-<PRE>
+<html>
+<head>
+  <meta name="generator" content=
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
+  <title>Quick test for identifying display character set</title>
+  <link rev="made" href="mailto:lynx-dev@nongnu.org">
+  <meta http-equiv="Content-Type" content=
+  "text/html; charset=us-ascii">
+</head>
 
-0x00A9    &#x00A9;           # COPYRIGHT SIGN
+<body>
+  <h1>Try this page with Lynx 2.7.2 or above:</h1>
 
-0x00C7    &#x00C7;           # LATIN CAPITAL LETTER C WITH CEDILLA
+  <p>If you see several letters instead of a single - your promised
+  display charset does not support this character so "7 bit
+  approximation" is in effect. If you see any single letter which
+  definitely far from being supposed you have a wrong lynx
+  settings. <em>Press 'o' for Options menu and change "Display
+  character set"</em>. Try again if necessary.<br>
+  When you are satisfied save your changes in Options menu,
+  thanks.</p>
+  <pre>
 
-0x00DC    &#x00DC;           # LATIN CAPITAL LETTER U WITH DIAERESIS
 
-0x00D1    &#x00D1;           # LATIN CAPITAL LETTER N WITH TILDE
+0x00A9    &copy;           # COPYRIGHT SIGN
 
-0x0107    &#x0107;           # LATIN SMALL LETTER C WITH ACUTE
-0x0108    &#x0108;           # LATIN CAPITAL LETTER C WITH CIRCUMFLEX
-0x010C    &#x010C;           # LATIN CAPITAL LETTER C WITH CARON
+0x00C7    &Ccedil;           # LATIN CAPITAL LETTER C WITH CEDILLA
 
+0x00DC    &Uuml;           # LATIN CAPITAL LETTER U WITH DIAERESIS
 
-0x03BB    &#x03BB;           # GREEK SMALL LETTER LAMDA
+0x00D1    &Ntilde;           # LATIN CAPITAL LETTER N WITH TILDE
 
-0x041B    &#x041B;           # CYRILLIC CAPITAL LETTER EL
-0x042E    &#x042E;           # CYRILLIC CAPITAL LETTER YU
-0x043B    &#x043B;           # CYRILLIC SMALL LETTER EL
-0x044E    &#x044E;           # CYRILLIC SMALL LETTER YU
+0x0107    &#263;           # LATIN SMALL LETTER C WITH ACUTE
+0x0108    &#264;           # LATIN CAPITAL LETTER C WITH CIRCUMFLEX
+0x010C    &#268;           # LATIN CAPITAL LETTER C WITH CARON
 
-0x2026    &#x2026;           # HORIZONTAL ELLIPSIS
-0x2122    &#x2122;           # TRADE MARK SIGN
 
-0x255D    &#x255D;           # BOX DRAWINGS DOUBLE UP AND LEFT
-0x255E    &#x255E;           # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE
+0x03BB    &lambda;           # GREEK SMALL LETTER LAMDA
 
-0xFB01    &#xFB01;           # LATIN SMALL LIGATURE FI
+0x041B    &#1051;           # CYRILLIC CAPITAL LETTER EL
+0x042E    &#1070;           # CYRILLIC CAPITAL LETTER YU
+0x043B    &#1083;           # CYRILLIC SMALL LETTER EL
+0x044E    &#1102;           # CYRILLIC SMALL LETTER YU
 
+0x2026    &hellip;           # HORIZONTAL ELLIPSIS
+0x2122    &trade;           # TRADE MARK SIGN
 
+0x255D    &#9565;           # BOX DRAWINGS DOUBLE UP AND LEFT
+0x255E    &#9566;           # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE
 
-</PRE>
-This is only a quick test to see obvious problems.
+0xFB01    &#64257;           # LATIN SMALL LIGATURE FI
 
 
-</BODY>
-</HTML>
+
+</pre>
+
+  <p>This is only a quick test to see obvious problems.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html
index 891845ea..197eb498 100644
--- a/lynx_help/keystrokes/visited_help.html
+++ b/lynx_help/keystrokes/visited_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: visited_help.html,v 1.7 2012/01/31 11:50:47 tom Exp $ -->
+<!-- $LynxId: visited_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Help on the Visited Links Page</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/keystrokes/xterm_help.html b/lynx_help/keystrokes/xterm_help.html
index e76674ca..4b65016d 100644
--- a/lynx_help/keystrokes/xterm_help.html
+++ b/lynx_help/keystrokes/xterm_help.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: xterm_help.html,v 1.6 2012/01/31 11:49:45 tom Exp $ -->
+<!-- $LynxId: xterm_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>X Terminal Help</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
diff --git a/lynx_help/lynx-dev.html b/lynx_help/lynx-dev.html
index b3cf4670..6db2e8f1 100644
--- a/lynx_help/lynx-dev.html
+++ b/lynx_help/lynx-dev.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!-- $LynxId: lynx-dev.html,v 1.13 2012/01/31 10:51:43 tom Exp $ -->
+<!-- $LynxId: lynx-dev.html,v 1.14 2013/05/21 10:45:03 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>Lynx-Dev Discussion List</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -14,9 +14,9 @@
 
 <body>
   <blockquote>
-    [ <a href=
+    <p>[ <a href=
     "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Lynx-Dev
-    Archive</a> | <a href="about_lynx.html">About Lynx</a> ]
+    Archive</a> | <a href="about_lynx.html">About Lynx</a> ]</p>
   </blockquote>
 
   <h1><em>The Lynx Development Process</em></h1>
diff --git a/lynx_help/lynx_help_main.html b/lynx_help/lynx_help_main.html
index 4e601b03..b8494de8 100644
--- a/lynx_help/lynx_help_main.html
+++ b/lynx_help/lynx_help_main.html
@@ -1,10 +1,10 @@
+<!-- $LynxId: lynx_help_main.html,v 1.40 2013/05/22 00:56:39 tom Exp $ -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<!-- $LynxId: lynx_help_main.html,v 1.38 2012/01/31 10:50:33 tom Exp $ -->
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>The Lynx Help Page</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -51,11 +51,6 @@
     for Beginners</a> &mdash; quick help on many common problems 
     <!-- {li}{a href="http://lynx.isc.org/cgi-bin/fom"}The Lynx FAQ-O-Matic{/a} .. many common queries, some more advanced; users may add answers. --></li>
 
-    <li><a href="http://www.subir.com/lynx.html">Lynx Links</a>
-    &mdash; source &amp; binaries, FAQs, developers &amp;
-    archives,<br>
-    SSL &amp; security, and more</li>
-
     <li><a href="http://leb.net/blinux/blynx/">Blynx</a> &mdash;
     Speech-Friendly Help for the visually impaired</li>
   </ul>
diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html
index 390c0153..cc5a65bb 100644
--- a/lynx_help/lynx_url_support.html
+++ b/lynx_help/lynx_url_support.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<!-- $LynxId: lynx_url_support.html,v 1.30 2012/01/31 10:52:00 tom Exp $ -->
+<!-- $LynxId: lynx_url_support.html,v 1.31 2013/05/21 10:50:42 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
 <html>
 <head>
   <meta name="generator" content=
-  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
+  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
 
   <title>URL Schemes Supported in Lynx</title>
   <link rev="made" href="mailto:lynx-dev@nongnu.org">
@@ -14,7 +14,7 @@
 
 <body>
   <blockquote>
-    <em>[</em><a href="#http_url">http, https</a> <em>|</em>
+    <p><em>[</em><a href="#http_url">http, https</a> <em>|</em>
     <a href="#telnet_url">telnet, tn3270, rlogin</a> <em>|</em>
     <a href="#gopher_url">gopher</a> <em>|</em> <a href=
     "#file_url">file</a> <em>|</em> <a href="#ftp_url">ftp</a>
@@ -26,7 +26,7 @@
     <em>|</em> <a href="#bibp_url">bibp</a> <em>|</em> <a href=
     "#exec_url">lynxexec, lynxprog</a> <em>|</em> <a href=
     "#cgi_url">lynxcgi</a><em>|</em> <a href="#ncftp_url">NcFTP</a>
-    <em>|</em> <a href="#internal_url">internal</a><em>]</em>
+    <em>|</em> <a href="#internal_url">internal</a><em>]</em></p>
   </blockquote>
 
   <h1><em>URL Schemes Supported in Lynx</em></h1>
@@ -54,7 +54,9 @@
 
     <li><a href=
     "ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt</a></li>
-  </ul>and in subsequent drafts of the <em>IETF</em>:
+  </ul>
+
+  <p>and in subsequent drafts of the <em>IETF</em>:</p>
 
   <ul>
     <li><a href="http://www.ics.uci.edu/pub/ietf/uri/">Uniform
@@ -93,31 +95,32 @@
   RFC1808 and subsequent IETF drafts.</p>
   <hr>
 
-  <h2><a name="http_url">The <em>http</em> and <em>https</em>
-  URLs:</a></h2>
+  <h2><a name="http_url" id="http_url">The <em>http</em> and
+  <em>https</em> URLs:</a></h2>
 
   <p>Lynx handles http URLs exactly as specified in RFC1738. The
   format is:</p>
   <pre>
       <em>http://host:port/path?searchpart#fragment</em>
-</pre>where <em>:port</em> is optional and defaults to
-<em>:80</em>, <em>/path</em> if present is a slash-separated series
-of symbolic elements, and <em>?searchpart</em> if present is the
-query for an ISINDEX search or the content of a FORM with
-METHOD="GET". The <em>#fragment</em> field if present indicates a
-location in the document to seek for display, based on a NAME-ed
-anchor or an ID attribute within the document, and is technically
-an instruction rather than part of the URL. Lynx will treat ID
-attributes as NAME-ed anchors for all tags in the BODY of a
-document which can correspond to positions in the rendering of the
-document.
+</pre>
+
+  <p>where <em>:port</em> is optional and defaults to <em>:80</em>,
+  <em>/path</em> if present is a slash-separated series of symbolic
+  elements, and <em>?searchpart</em> if present is the query for an
+  ISINDEX search or the content of a FORM with METHOD="GET". The
+  <em>#fragment</em> field if present indicates a location in the
+  document to seek for display, based on a NAME-ed anchor or an ID
+  attribute within the document, and is technically an instruction
+  rather than part of the URL. Lynx will treat ID attributes as
+  NAME-ed anchors for all tags in the BODY of a document which can
+  correspond to positions in the rendering of the document.</p>
 
   <p>The https URL has the same format, but the default port is
   <em>:443</em>.</p>
   <hr>
 
-  <h2><a name="telnet_url">The <em>telnet</em>, <em>tn3270</em>,
-  and <em>rlogin</em> URLs:</a></h2>
+  <h2><a name="telnet_url" id="telnet_url">The <em>telnet</em>,
+  <em>tn3270</em>, and <em>rlogin</em> URLs:</a></h2>
 
   <p>A <em>telnet</em> URL generally results in Lynx spawning a
   telnet session. Lynx implements the complete telnet URL scheme,
@@ -142,23 +145,27 @@ document.
   password whether or not one was included in the URL.</p>
   <hr>
 
-  <h2><a name="gopher_url">The <em>gopher</em> URL:</a></h2>
+  <h2><a name="gopher_url" id="gopher_url">The <em>gopher</em>
+  URL:</a></h2>
 
   <p>The gopher URL takes the form:</p>
   <pre>
       <em>gopher://host:port/gopher-path</em>
-</pre>where <em>:port</em> is optional and defaults to
-<em>:70</em>, and the <em>/gopher-path</em> is opaque (not fully
-equivalent to the slash-separated series of symbolic elements of
-http paths) as explained in RFC1738. Typically, the gopher-path
-consists of a <a href=
-"keystrokes/gopher_types_help.html"><em>gophertype</em></a>
-indicating the file or service type (e.g., <em>0</em> or <em>I</em>
-for plain text or an image, respectively, <em>7</em> for a search,
-or <em>1</em> for a directory), followed by a platform-specific
-<em>selector</em>. Any reserved characters in the selector should
-be hex escaped (<em>%hh</em>), including slashes, although hex
-escaping of slashes is not required by Lynx in gopher URLs.
+</pre>
+
+  <p>where <em>:port</em> is optional and defaults to <em>:70</em>,
+  and the <em>/gopher-path</em> is opaque (not fully equivalent to
+  the slash-separated series of symbolic elements of http paths) as
+  explained in RFC1738. Typically, the gopher-path consists of a
+  <a href=
+  "keystrokes/gopher_types_help.html"><em>gophertype</em></a>
+  indicating the file or service type (e.g., <em>0</em> or
+  <em>I</em> for plain text or an image, respectively, <em>7</em>
+  for a search, or <em>1</em> for a directory), followed by a
+  platform-specific <em>selector</em>. Any reserved characters in
+  the selector should be hex escaped (<em>%hh</em>), including
+  slashes, although hex escaping of slashes is not required by Lynx
+  in gopher URLs.</p>
 
   <p>Lynx does not overtly support the gopher+ protocol, and does
   not represent itself as gopher+ capable when communicating with
@@ -179,51 +186,63 @@ escaping of slashes is not required by Lynx in gopher URLs.
   convert the gopher URL to an http URL, e.g.:<br></p>
   <pre>
 <em>gopher://www.wfbr.edu:80/hGET%20/</em>
-</pre>will become:<br>
+</pre>
+
+  <p>will become:<br></p>
   <pre>
 <em>http://www.wfbr.edu/</em>
-</pre>The port field will be retained if it is not <em>:80</em>,
-and will default to <em>:70</em> if it was defaulted originally.
-These conventions were adopted during development of the University
-of Minnesota gopher software to facilitate the offering of links to
-MIME-capable http servers in the listings returned by gopher
-servers, but should be considered Lynxisms and UMN Gopherisms.
+</pre>
+
+  <p>The port field will be retained if it is not <em>:80</em>, and
+  will default to <em>:70</em> if it was defaulted originally.
+  These conventions were adopted during development of the
+  University of Minnesota gopher software to facilitate the
+  offering of links to MIME-capable http servers in the listings
+  returned by gopher servers, but should be considered Lynxisms and
+  UMN Gopherisms.</p>
   <hr>
 
-  <h2><a name="file_url">The <em>file</em> URL:</a></h2>
+  <h2><a name="file_url" id="file_url">The <em>file</em>
+  URL:</a></h2>
 
   <p>The file URL is used to retrieve files or generate a directory
   listing on the local host. The host field can be
   <em>localhost</em> or a domain name for the local host:<br></p>
   <pre>
 <em>file://localhost/path</em>
-</pre>If you do not use <em>localhost</em> or a domain name for the
-local host, Lynx will substitute <em>ftp://</em> for
-<em>file://</em> and treat it as an ftp URL.
+</pre>
+
+  <p>If you do not use <em>localhost</em> or a domain name for the
+  local host, Lynx will substitute <em>ftp://</em> for
+  <em>file://</em> and treat it as an ftp URL.</p>
 
   <p>The <em>/path</em> is treated as originating at the root,
   unless you include a tilde (<em>~</em>), e.g.:</p>
   <pre>
       <em>file://localhost/~/foo</em>   will be converted to:
       <em>file://localhost/your/login/directory/foo</em>
-</pre>The latter feature is a Lynxism, is done homologously on Unix
-and VMS, and should be used ONLY in local documents intended for
-Lynx.
+</pre>
+
+  <p>The latter feature is a Lynxism, is done homologously on Unix
+  and VMS, and should be used ONLY in local documents intended for
+  Lynx.</p>
 
   <p>On VMS, the first element of the path, if not a tilde, is
   assumed to be a device, e.g.:</p>
   <pre>
       <em>file://localhost/www_root/directory/filename.suffix</em>
-</pre>should be used for:
-<em>www_root:[directory]filename.suffix</em><br>
+</pre>
+
+  <p>should be used for:
+  <em>www_root:[directory]filename.suffix</em><br>
   If you are unsure how to specify a file URL in local documents on
   VMS, invoke Lynx with the desired file or directory as the
   <em>startfile</em> using any spec acceptable to DCL, and then use
   the <em>showinfo</em> command (<em>=</em>) to see the file URL
-  which Lynx created for it.
+  which Lynx created for it.</p>
   <hr>
 
-  <h2><a name="ftp_url">The <em>ftp</em> URL:</a></h2>
+  <h2><a name="ftp_url" id="ftp_url">The <em>ftp</em> URL:</a></h2>
 
   <p>The ftp URL has the general format:</p>
   <pre>
@@ -264,10 +283,12 @@ Lynx.
   (<em>%2f</em>), e.g.:</p>
   <pre>
       <em>ftp://user@myhost/%2fsys$common/syshlp</em>
-</pre>can be used for a listing of sys$common:[syshlp]<br>
+</pre>
+
+  <p>can be used for a listing of sys$common:[syshlp]<br>
   Also, on VM/CMS ftp servers, if the <em>path</em> string begins
   with <em>vmsysu%3a</em> it receives special handling as an SFS
-  path, e.g.:
+  path, e.g.:</p>
   <pre>
       <em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em>
 </pre>
@@ -286,7 +307,8 @@ Lynx.
 </pre>
   <hr>
 
-  <h2><a name="wais_url">The <em>wais</em> URL:</a></h2>
+  <h2><a name="wais_url" id="wais_url">The <em>wais</em>
+  URL:</a></h2>
 
   <p>The wais URL is used to retrieve resources using the Wide Area
   Information System protocol. The format is:</p>
@@ -294,7 +316,9 @@ Lynx.
       <em>wais://host:port/database</em>
       <em>wais://host:port/database?wais_query</em>
       <em>wais://host:port/database/wais_type/wais_path</em>
-</pre>where <em>:port</em> defaults to <em>:210</em>
+</pre>
+
+  <p>where <em>:port</em> defaults to <em>:210</em></p>
 
   <p>Direct wais support is built into Lynx for VMS, and can be
   compiled into Lynx on Unix.</p>
@@ -308,8 +332,8 @@ Lynx.
   from the hit list.</p>
   <hr>
 
-  <h2><a name="news_url">The <em>news</em>, <em>nntp</em>, and
-  <em>snews</em> URLs:</a></h2>
+  <h2><a name="news_url" id="news_url">The <em>news</em>,
+  <em>nntp</em>, and <em>snews</em> URLs:</a></h2>
 
   <p>The news and nntp URLs are handled by Lynx as specified in
   RFC1738, but for compatibility with other clients, Lynx allows
@@ -336,7 +360,10 @@ Lynx.
       <em>nntp://host:port/newsgroup</em>
       <em>nntp://host:port/messageID</em>
       <em>nntp://host:port/*</em>
-</pre>(snews same as nntp, but the default port is <em>:563</em>)
+</pre>
+
+  <p>(snews same as nntp, but the default port is
+  <em>:563</em>)</p>
 
   <p>The <em>messageID</em> is the message's unique identifier,
   consisting of an identification string and the host of origin for
@@ -347,10 +374,12 @@ Lynx.
   <pre>
       <em>news:comp.infosystems.*</em>
       <em>nntp://host:port/comp.infosystems.*</em>
-</pre>(snews same as nntp, but the default port is
-<em>:563</em>)<br>
+</pre>
+
+  <p>(snews same as nntp, but the default port is
+  <em>:563</em>)<br>
   This is not in RFC1738 and may not be supported by all other
-  clients.
+  clients.</p>
 
   <p>Lynx allows you both to <em>reply</em> to the author of a news
   message via email, and, if news posting has been enabled, to send
@@ -369,16 +398,18 @@ Lynx.
       <em>news:newsgroup/messageNo</em>     (retrieves the message by number)
       <em>nntp://host:port/newsgroup/startNo-endNo</em>
       <em>nntp://host:port/newsgroup/messageNo</em>
-</pre>(snews same as nntp, but the default port is
-<em>:563</em>)<br>
+</pre>
+
+  <p>(snews same as nntp, but the default port is
+  <em>:563</em>)<br>
   Use of this scheme is not recommended, because the message
   numbers are specific to each nntp server, unlike the unique
-  identifiers for news messages.
+  identifiers for news messages.</p>
   <hr>
 
-  <h2><a name="newspost_url">The <em>newspost</em>,
-  <em>newsreply</em>, <em>snewspost</em>, and <em>snewsreply</em>
-  URLs:</a></h2>
+  <h2><a name="newspost_url" id="newspost_url">The
+  <em>newspost</em>, <em>newsreply</em>, <em>snewspost</em>, and
+  <em>snewsreply</em> URLs:</a></h2>
 
   <p>When Lynx receives group listings or articles via
   <em>news</em>, <em>nntp</em> or <em>snews</em> URLs, it also
@@ -397,8 +428,10 @@ Lynx.
   <pre>
       <em>newspost://host:port/newsgroup(s)</em>  (post a new message)
       <em>newsreply://host:port/newsgroup(s)</em> (post a followup message)
-</pre>(snewspost and snewsreply have the same formats, but the
-default port is <em>:563</em>)
+</pre>
+
+  <p>(snewspost and snewsreply have the same formats, but the
+  default port is <em>:563</em>)</p>
 
   <p>If the host field is omitted, it defaults to that pointed to
   by the NNTPSERVER configuration or environmental variable.
@@ -423,7 +456,8 @@ default port is <em>:563</em>)
   presently are supported only by Lynx.</p>
   <hr>
 
-  <h2><a name="mailto_url">The <em>mailto</em> URL:</a></h2>
+  <h2><a name="mailto_url" id="mailto_url">The <em>mailto</em>
+  URL:</a></h2>
 
   <p>The mailto URL is used to provide links that when activated
   can be used to send a comment or the content of a FORM to an
@@ -495,10 +529,14 @@ default port is <em>:563</em>)
   the content with the default:</p>
   <pre>
       <em>ENCTYPE="application/x-www-form-urlencoded"</em> ('<em>&amp;</em>' separates pairs)
-</pre>or:
+</pre>
+
+  <p>or:</p>
   <pre>
       <em>ENCTYPE="application/sgml-form-urlencoded"</em> ('<em>;</em>' separates pairs)
-</pre>if the latter was indicated.
+</pre>
+
+  <p>if the latter was indicated.</p>
 
   <p>Note that when mailing FORM content Lynx wraps any lines
   longer than 78 characters, to avoid buffer overflows in mail
@@ -517,7 +555,8 @@ default port is <em>:563</em>)
   relevant to the message which will be sent.</p>
   <hr>
 
-  <h2><a name="finger_url">The <em>finger</em> URL:</a></h2>
+  <h2><a name="finger_url" id="finger_url">The <em>finger</em>
+  URL:</a></h2>
 
   <p>Lynx has full support for the finger protocol, but a format
   for finger URLs has not yet been adopted by the IETF. The formats
@@ -553,7 +592,7 @@ default port is <em>:563</em>)
   supported URLs.</p>
   <hr>
 
-  <h2><a name="cso_url">The <em>cso</em> URL:</a></h2>
+  <h2><a name="cso_url" id="cso_url">The <em>cso</em> URL:</a></h2>
 
   <p>The cso URL is intended to provide a gateway to CSO/PH (QI)
   servers. The requests are made on port 105 by default
@@ -576,7 +615,8 @@ default port is <em>:563</em>)
   URL.</p>
   <hr>
 
-  <h2><a name="bibp_url">The <em>bibp</em> URL:</a></h2>
+  <h2><a name="bibp_url" id="bibp_url">The <em>bibp</em>
+  URL:</a></h2>
 
   <p>Lynx provides built-in support for bibliographic protocol
   (BibP). BibP links are links to published works such as books or
@@ -586,7 +626,7 @@ default port is <em>:563</em>)
   performed by a document-specified server or a known global
   server.</p>
 
-  <h2><a name="exec_url">The <em>lynxexec</em> and
+  <h2><a name="exec_url" id="exec_url">The <em>lynxexec</em> and
   <em>lynxprog</em> URLs:</a></h2>
 
   <p>If execution of spawned commands has been enabled in your Lynx
@@ -599,8 +639,10 @@ default port is <em>:563</em>)
       <em>lynxexec:dir/date/size foo:[blah]</em> (VMS)
       <em>lynxexec:ls -l /foo/blah</em>          (Unix)
       <em>lynxprog:news</em>
-</pre>(Note, however, that restrictions on acceptable commands or
-utilities may be imposed by the system administrator.)
+</pre>
+
+  <p>(Note, however, that restrictions on acceptable commands or
+  utilities may be imposed by the system administrator.)</p>
 
   <p>You optionally can include <em>//localhost/</em> in the URL,
   between the scheme field and the command, but that is always
@@ -615,32 +657,38 @@ utilities may be imposed by the system administrator.)
   intended solely for Lynx.</p>
   <hr>
 
-  <h2><a name="cgi_url">The <em>lynxcgi</em> URL:</a></h2>
+  <h2><a name="cgi_url" id="cgi_url">The <em>lynxcgi</em>
+  URL:</a></h2>
 
   <p>The lynxcgi URL is implemented only on Unix, can be used as
   the ACTION for a FORM, and if enabled in your Lynx image has the
   format:</p>
   <pre>
       <em>lynxcgi://localhost/path_to_CGI_script</em>
-</pre>where <em>//localhost</em> is optional and always implied;
-the full path should be specified, as `~' is not recognized; if the
-script is in the directory Lynx was started from, the simple file
-name is adequate. The output of the script should be text/html and
-is rendered and displayed by Lynx. Restrictions on use of lynxcgi
-and on acceptable paths can be imposed in <em>userdefs.h</em> and
-<em>lynx.cfg</em>, qv.
+</pre>
+
+  <p>where <em>//localhost</em> is optional and always implied; the
+  full path should be specified, as `~' is not recognized; if the
+  script is in the directory Lynx was started from, the simple file
+  name is adequate. The output of the script should be text/html
+  and is rendered and displayed by Lynx. Restrictions on use of
+  lynxcgi and on acceptable paths can be imposed in
+  <em>userdefs.h</em> and <em>lynx.cfg</em>, qv.</p>
 
   <p>This is a Lynxism and should be used only in local documents
   intended solely for Lynx, or for limited local testing of CGI
   scripts without an http server.</p>
   <hr>
 
-  <h2><a name="ncftp_url">The <em>NcFTP</em> URL:</a></h2>
+  <h2><a name="ncftp_url" id="ncftp_url">The <em>NcFTP</em>
+  URL:</a></h2>
 
   <p>Lynx recognizes the NcFTP-style ftp URL, e.g.,</p>
   <pre>
         <cite>ftpHost</cite>:<cite>fileSpecification</cite>
-</pre>for example
+</pre>
+
+  <p>for example</p>
   <pre>
 <code>
         ftp.gnu.org:/pub/gnu
@@ -648,8 +696,8 @@ and on acceptable paths can be imposed in <em>userdefs.h</em> and
 </pre>
   <hr>
 
-  <h2><a name="internal_url">The <em>LYNXfoo</em> internal
-  URLs:</a></h2>
+  <h2><a name="internal_url" id="internal_url">The <em>LYNXfoo</em>
+  internal URLs:</a></h2>
 
   <p>Lynx uses a variety of private URL schemes for communication
   among its internal modules. They start with uppercase letters
@@ -680,21 +728,27 @@ and on acceptable paths can be imposed in <em>userdefs.h</em> and
   <pre>
       <em>Return to your &lt;A HREF="LYNXHIST:0"&gt;Startfile&lt;/A&gt;</em>
       <em>Review your &lt;A HREF="LYNXKEYMAP:"&gt;Keymap&lt;/A&gt;</em>
-</pre>(No, they won't do any harm. Yes, they work. But don't rely
-on it.)
+</pre>
+
+  <p>(No, they won't do any harm. Yes, they work. But don't rely on
+  it.)</p>
 
   <p>If you must try one, the second is OK from the command
   line:<br></p>
   <pre>
       <em>lynx LYNXKEYMAP:</em>
-</pre>But within Lynx, use the '<em>K</em>' keystroke command.
-Sometimes it may be convenient to use a private scheme with
-'<em>g</em>'oto, as in:
+</pre>
+
+  <p>But within Lynx, use the '<em>K</em>' keystroke command.
+  Sometimes it may be convenient to use a private scheme with
+  '<em>g</em>'oto, as in:</p>
   <pre>
       <em>g LYNXMESSAGES:</em>
       <em>g LYNXCOMPILEOPTS:</em>
       <em>g LYNXCFG:</em>
-</pre>But again, there usually is a way in which those special
-pages are meant to be reached that is more convenient.
+</pre>
+
+  <p>But again, there usually is a way in which those special pages
+  are meant to be reached that is more convenient.</p>
 </body>
 </html>