snapshot of project "lynx", label v2-7-1ac_0-105

1 files changed, 28 insertions, 12 deletions

diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html
index 0237733d..154371e1 100644
--- a/lynx_help/lynx_url_support.html
+++ b/lynx_help/lynx_url_support.html
@@ -397,17 +397,17 @@ ENCTYPE="text/plain"<BR>
 <tab indent="14">...<BR>
 <tab indent="12">&lt;/FORM&gt;</em>
 
-<p>Note that a TITLE attribute for FORM has been proposed but not included
-in any HTML specifications or drafts, and should be considered a Lynxism
-until/unless it is.  Some clients use a SUBJECT attribute for this purpose
+<p>Note that a TITLE attribute for FORM is now included in the HTML
+specifications.  Some clients use a SUBJECT attribute for this purpose
 in FORM tags, and Lynx recognizes that as a synonym for TITLE.
 
-<p>Lynx also will process any <em>cc=someone@host</em> and/or
-<em>body=Blah</em> fields in <em>?searchpart</em> tack-ons to mailto
-URLs.  The <em>cc</em> values can be single addresses, or comma- or
-semi-colon-separated lists of addresses.  All addresses, and any
-<em>body</em> values, will be offered for approval by the user before
-proceeding with a mailing, and any other name=value pairs in the
+<p>Lynx also will process any <em>to=address(es)</em>,
+<em>cc=address(es)</em>, <em>keywords=word_list</em> and/or
+<em>body=message</em> fields in <em>?searchpart</em> tack-ons to mailto
+URLs.  The <em>to</em> and/or <em>cc</em> values can be single addresses,
+or comma- or semi-colon-separated lists of addresses.  All addresses,
+and any <em>body</em> values, will be offered for approval by the user
+before proceeding with a mailing.   Any other name=value pairs in the
 <em>?searchpart</em> will be ignored.  Also, if the mailto URL is the
 ACTION for a FORM, any <em>body</em> in a <em>?searchpart</em> tack-on
 will be ignored, because the body of the mailing must be constructed
@@ -415,9 +415,12 @@ solely from the the FORM's content.  Lynx expects multiple name=value
 pairs in a <em>?searchpart</em> tack-on to be separated by ampersands,
 as in the original Netscape implementation, and in an equally ill-advised
 IETF draft of that implementation (<a
-href="ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-00.txt"
->draft-hoffman-mailto-url-00.txt</a>).  These should be represented as
-entities (<em>&amp;amp;</em>) in the HTML markup.
+href="ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-03.txt"
+>draft-hoffman-mailto-url-03.txt</a>).  These should be represented as
+entities (<em>&amp;amp;</em>) in the HTML markup.  This functionality
+is generally desired, but the IETF backward compatibility principal
+normally would lead to a new scheme being used (e.g., <em>mail:</em>, or
+<em>smtp:</em>), rather than breaking <em>mailto:</em> implementations.
 
 <p>If <em>ENCTYPE="text/plain"</em> is specified for a FORM with a mailto
 ACTION, Lynx will not hex escape the name=value pairs of the FORM's content,
@@ -500,6 +503,19 @@ to the server.   Any strings in the reports returned for these requests
 converted into a link for accessing that URL.
 <HR WIDTH="100%">
 
+<H2><a name="chargen">The <em>chargen</em> URL:</a></H2>
+
+The chargen URL is intended to provide a gateway to the chargen service.
+The requests are made on port 19 (<em>:19</em>).  You can omit the port,
+and no other value is allowed.  The format is:<BR>
+<tab indent="12"><em>chargen://host</em><BR>
+
+<p>Lynx will accept approximately 55 lines of characters in the stream
+returned by the server, then close the connection and display the lines
+as PRE formatted text.  Note that if port 19 is used for a URL with a
+scheme other than chargen, the URL will be rejected by Lynx.
+<HR WIDTH="100%">
+
 <H2><a name="exec">The <em>lynxexec</em> and <em>lynxprog</em> URLs:</a></H2>
 
 If execution of spawned commands has been enabled in your Lynx image, the