[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
LYNX-DEV upgrade lynx_help files to html 3.2
|
From: |
Larry W. Virden, x2487 |
|
Subject: |
LYNX-DEV upgrade lynx_help files to html 3.2 |
|
Date: |
Fri, 2 May 1997 10:18:35 -0400 |
I went thru and made some minor changes to make the lynx_help high level
html files HTML 3.2 compatible.
*** Lynx_users_guide.html-dist Fri May 2 10:05:27 1997
--- Lynx_users_guide.html Fri May 2 10:16:19 1997
***************
*** 1,4 ****
! <!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">
<html>
<head>
<title>Lynx Users Guide v2.7.1</title>
--- 1,4 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<title>Lynx Users Guide v2.7.1</title>
***************
*** 205,217 ****
Lynx also will attempt to create a complete URL if you include adequate
portions of it in the startfile argument. For example:<br>
! <tab indent="34"><em>wfbr</em>
! <tab indent="62">will be expanded to:<br>
! <tab indent="12"><em>http://www.wfbr.edu/</em>
! <tab indent="62">and:<br>
! <tab indent="26"><em>ftp.more.net/pub</em>
! <tab indent="62">will be expanded to:<br>
! <tab indent="14"><em>ftp://ftp.more.net/pub</em><br>
See <a href="lynx_url_support.html">URL Schemes Supported by Lynx</a> for
more detailed information. [<A HREF="#TOC">ToC</A>]
--- 205,217 ----
Lynx also will attempt to create a complete URL if you include adequate
portions of it in the startfile argument. For example:<br>
! <em>wfbr</em>
! will be expanded to:<br>
! <em>http://www.wfbr.edu/</em>
! and:<br>
! <em>ftp.more.net/pub</em>
! will be expanded to:<br>
! <em>ftp://ftp.more.net/pub</em><br>
See <a href="lynx_url_support.html">URL Schemes Supported by Lynx</a> for
more detailed information. [<A HREF="#TOC">ToC</A>]
***************
*** 439,446 ****
gateways for such servers. For example, an HTML index document can act as a
<em>cover page</em> describing a WAIS database and how to formulate query
strings for searching it, and include an element such as:<BR>
! <tab indent="12"><em><ISINDEX <tab id="idx">PROMPT="Enter WAIS query:"<BR>
! <tab to="idx">HREF="wais://net.bio.net/biologists-addresses"></em><BR>
for submitting a search of the Biologist's Addresses database directly
to the net.bio.net WAIS server. [<A HREF="#TOC">ToC</A>]
--- 439,446 ----
gateways for such servers. For example, an HTML index document can act as a
<em>cover page</em> describing a WAIS database and how to formulate query
strings for searching it, and include an element such as:<BR>
! <em><ISINDEX PROMPT="Enter WAIS query:"<BR>
! HREF="wais://net.bio.net/biologists-addresses"></em><BR>
for submitting a search of the Biologist's Addresses database directly
to the net.bio.net WAIS server. [<A HREF="#TOC">ToC</A>]
***************
*** 1105,1114 ****
keys also will invoke a no-cache resubmission if the reply from a form
submission included a META element with a no-cache Pragma or Cache-Control
directive:<BR>
! <tab indent="12"
! ><em><META HTTP-EQUIV="Pragma" CONTENT="no-cache"></em><BR>
! <tab indent="12"
! ><em><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"></em><BR>
or the server sent a "Pragma" or "Cache-Control" MIME header with a
no-cache directive.
--- 1105,1112 ----
keys also will invoke a no-cache resubmission if the reply from a form
submission included a META element with a no-cache Pragma or Cache-Control
directive:<BR>
! <em><META HTTP-EQUIV="Pragma" CONTENT="no-cache"></em><BR>
! <em><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"></em><BR>
or the server sent a "Pragma" or "Cache-Control" MIME header with a
no-cache directive.
***************
*** 1122,1129 ****
<em>submit</em> button. Lynx normally will not resubmit a form which has
<em>POST</em> as the METHOD if the document returned by the form has links
which you activated, and then you go back via the PREV_DOC
! (<em>left-arrow</em>) command or via the <a
! href="keystroke_commands/history_help.html">History Page</em>. Lynx can be
compiled so that it resubmits the form in those cases as well, and the default
can be changed via <em>lynx.cfg</em>, and toggled via the
<em>-resubmit_posts</em> command line switch.
--- 1120,1127 ----
<em>submit</em> button. Lynx normally will not resubmit a form which has
<em>POST</em> as the METHOD if the document returned by the form has links
which you activated, and then you go back via the PREV_DOC
! (<em>left-arrow</em>) command or via the
! <a href="keystroke_commands/history_help.html"><em>History Page</em></a>.
Lynx can be
compiled so that it resubmits the form in those cases as well, and the default
can be changed via <em>lynx.cfg</em>, and toggled via the
<em>-resubmit_posts</em> command line switch.
***************
*** 1236,1244 ****
ACTION, which is normally the script, itself, or a PATH_INFO field, and
thus might be misleading. This also can be done via a META element in
any document:
! <tab indent="12"
! ><em><META <tab id="cdis">HTTP-EQUIV="Content-Disposition"<BR>
! <tab to="cdis">CONTENT="file; filename=name.suffix"></em><BR>
[<A HREF="#TOC">ToC</A>]
<h2><A NAME="20"><em>Lynx and HTML Tables</em></a></h2>
--- 1234,1241 ----
ACTION, which is normally the script, itself, or a PATH_INFO field, and
thus might be misleading. This also can be done via a META element in
any document:
! <em><META HTTP-EQUIV="Content-Disposition"<BR>
! CONTENT="file; filename=name.suffix"></em><BR>
[<A HREF="#TOC">ToC</A>]
<h2><A NAME="20"><em>Lynx and HTML Tables</em></a></h2>
***************
*** 1385,1395 ****
whether or not that is indicated in its content) with greater than normal
left and right margins, and the block will begin with a <em>FOOTNOTE:</em>
label. For example, if the document contains:<BR>
! <tab indent="16">See the <em><A
HREF="#fn1"></em><a href="#an1">footnote</a><em></A></em>.<BR>
activating that link will take you to the labeled rendering of:
! <p><tab indent="16"><em><FN ID="fn1"></em><p><a name="an1">Lynx
does not use popups for FN blocks.</a></p><em></FN></em>
<p>i.e., position it at the top of the page. Then, upon reading the footnote,
--- 1382,1392 ----
whether or not that is indicated in its content) with greater than normal
left and right margins, and the block will begin with a <em>FOOTNOTE:</em>
label. For example, if the document contains:<BR>
! See the <em><A
HREF="#fn1"></em><a href="#an1">footnote</a><em></A></em>.<BR>
activating that link will take you to the labeled rendering of:
! <p><em><FN ID="fn1"></em><p><a name="an1">Lynx
does not use popups for FN blocks.</a></p><em></FN></em>
<p>i.e., position it at the top of the page. Then, upon reading the footnote,
***************
*** 1414,1423 ****
for <a href="#24">HTML Footnotes</a>, but the NOTE block need not be placed
at the bottom of the document. The content of a NOTE block can be any HTML
markup that is valid in the BODY of the document. This is an example:<BR>
! <tab indent="12"><em><NOTE CLASS="warning" ID="too-bad"><BR>
! <tab indent="14"><p>The W3C vendors did not retain
NOTE in the HTML 3.2 draft.</p><BR>
! <tab indent="12"></NOTE></em><BR>
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.
[<A HREF="#TOC">ToC</A>]
--- 1411,1420 ----
for <a href="#24">HTML Footnotes</a>, but the NOTE block need not be placed
at the bottom of the document. The content of a NOTE block can be any HTML
markup that is valid in the BODY of the document. This is an example:<BR>
! <em><NOTE CLASS="warning" ID="too-bad"><BR>
! <p>The W3C vendors did not retain
NOTE in the HTML 3.2 draft.</p><BR>
! </NOTE></em><BR>
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.
[<A HREF="#TOC">ToC</A>]
***************
*** 1578,1584 ****
same URL or a new URL, at a specified number of seconds following receipt
of the current document. This procedure has been termed
<em>client-side-pull</em>. An example of such an element is:<BR>
! <tab indent="12"><em><META HTTP-EQUIV="Refresh" CONTENT="3;
URL="http://host/path"></em><BR>
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,
--- 1575,1581 ----
same URL or a new URL, at a specified number of seconds following receipt
of the current document. This procedure has been termed
<em>client-side-pull</em>. An example of such an element is:<BR>
! <em><META HTTP-EQUIV="Refresh" CONTENT="3;
URL="http://host/path"></em><BR>
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,
***************
*** 1813,1819 ****
<dt><code>-noexec</code>
<dd>disable local program execution. (DEFAULT)
<dt><code>-nofilereferer</code>
! <dd>disable transmissions of Referer headers for file URLs.
<dt><code>-nolist</code>
<dd>disable the link list feature in dumps.
<dt><code>-nolog</code>
--- 1810,1816 ----
<dt><code>-noexec</code>
<dd>disable local program execution. (DEFAULT)
<dt><code>-nofilereferer</code>
! <dd>disable transmissions of Referrer headers for file URLs.
<dt><code>-nolist</code>
<dd>disable the link list feature in dumps.
<dt><code>-nolog</code>
***************
*** 1825,1831 ****
<dt><code>-noredir</code>
<dd>don't follow URL redirections
<dt><code>-noreferer</code>
! <dd>disable transmissions of Referer headers.
<dt><code>-nosocks</code>
<dd>disable SOCKS proxy usage by a SOCKSified Lynx.
<dt><code>-nostatus</code>
--- 1822,1828 ----
<dt><code>-noredir</code>
<dd>don't follow URL redirections
<dt><code>-noreferer</code>
! <dd>disable transmissions of Referrer headers.
<dt><code>-nosocks</code>
<dd>disable SOCKS proxy usage by a SOCKSified Lynx.
<dt><code>-nostatus</code>
*** lynx_help_main.html-dist Fri May 2 09:44:54 1997
--- lynx_help_main.html Fri May 2 09:46:40 1997
***************
*** 1,4 ****
! <!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">
<html>
<head>
<link rev="made" href="mailto:address@hidden";>
--- 1,4 ----
! <!DOCTYPE html public "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<link rev="made" href="mailto:address@hidden";>
***************
*** 8,17 ****
<H1>Lynx Help Menu</h1>
! <ul plain>
! <lh><em>Choose a subject:</em></lh>
<li><a href="Lynx_users_guide.html">Lynx Users Guide</a>
! <ul plain>
<li><a href="keystroke_commands/keystroke_help.html">Key-stroke Commands</a>
| <a href="keystroke_commands/edit_help.html">Line Editor</a>
<li><a href="lynx_url_support.html">Supported URLs</a>
--- 8,17 ----
<H1>Lynx Help Menu</h1>
! <ul>
! <li><em>Choose a subject:</em></li>
<li><a href="Lynx_users_guide.html">Lynx Users Guide</a>
! <ul>
<li><a href="keystroke_commands/keystroke_help.html">Key-stroke Commands</a>
| <a href="keystroke_commands/edit_help.html">Line Editor</a>
<li><a href="lynx_url_support.html">Supported URLs</a>
***************
*** 33,49 ****
<li><a
href="http://www.w3.org/pub/WWW/MarkUp/html-spec/html-spec_toc.html";
>HTML 2.0</a>
- | <a href="http://www.w3.org/pub/WWW/MarkUp/html3/Contents.html";
- >HTML 3.0</a>
| <a href="http://www.alis.com:8085/ietf/html/";
>HTML i18n</a>
| <a href="http://www.w3.org/pub/WWW/MarkUp/";
>HTML 3.2</a>
! <ul plain>
<li><a href="http://www.stonehand.com/doc/";
>Spyglass/Stonehand Technical Reference</a>
! <ul plain>
<li><a
href="http://www.stonehand.com/doc/comments.html";
>Keep Your Comments Legal</a>
--- 33,47 ----
<li><a
href="http://www.w3.org/pub/WWW/MarkUp/html-spec/html-spec_toc.html";
>HTML 2.0</a>
| <a href="http://www.alis.com:8085/ietf/html/";
>HTML i18n</a>
| <a href="http://www.w3.org/pub/WWW/MarkUp/";
>HTML 3.2</a>
! <ul>
<li><a href="http://www.stonehand.com/doc/";
>Spyglass/Stonehand Technical Reference</a>
! <ul>
<li><a
href="http://www.stonehand.com/doc/comments.html";
>Keep Your Comments Legal</a>
*** lynx_url_support.html-dist Fri May 2 09:58:01 1997
--- lynx_url_support.html Fri May 2 10:17:35 1997
***************
*** 1,4 ****
! <!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">
<HTML>
<HEAD>
<TITLE>URL Schemes Supported in Lynx</TITLE>
--- 1,4 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<TITLE>URL Schemes Supported in Lynx</TITLE>
***************
*** 6,12 ****
</HEAD>
<BODY>
- <BANNER>
<em>[</em><a href="#http">http, https</a> <em>|</em>
<a href="#telnet">telnet, tn3270, rlogin</a> <em>|</em>
<a href="#gopher">gopher</a> <em>|</em>
--- 6,11 ----
***************
*** 21,33 ****
<a href="#exec">lynxexec, lynxprog</a> <em>|</em>
<a href="#cgi">lynxcgi</a><em>|</em>
<a href="#internal">internal</a><em>]</em>
- </BANNER>
<H1><em>URL Schemes Supported in Lynx</em></H1>
Lynx handles a number of URL types, that are enumerated below. For
more details about URLs (Uniform Resource Locators) see <em>RFC1738</em>:
! <ul plain>
<li><a href="http://www.w3.org/pub/WWW/Addressing/rfc1738.txt";
>http://www.w3.org/pub/WWW/Addressing/rfc1738.txt</a>
<li><a href="ftp://ds.internic.net/rfc/rfc1738.txt";
--- 20,31 ----
<a href="#exec">lynxexec, lynxprog</a> <em>|</em>
<a href="#cgi">lynxcgi</a><em>|</em>
<a href="#internal">internal</a><em>]</em>
<H1><em>URL Schemes Supported in Lynx</em></H1>
Lynx handles a number of URL types, that are enumerated below. For
more details about URLs (Uniform Resource Locators) see <em>RFC1738</em>:
! <ul>
<li><a href="http://www.w3.org/pub/WWW/Addressing/rfc1738.txt";
>http://www.w3.org/pub/WWW/Addressing/rfc1738.txt</a>
<li><a href="ftp://ds.internic.net/rfc/rfc1738.txt";
***************
*** 37,43 ****
<p>Lynx resolves partial or relative URLs in documents with respect to
the BASE if one was specified, otherwise with respect to the document's
absolute URL, using the rules described in <em>RFC1808</em>:
! <ul plain>
<li><a href="http://www.w3.org/pub/WWW/Addressing/rfc1808.txt";
>http://www.w3.org/pub/WWW/Addressing/rfc1808.txt</a>
<li><a href="ftp://ds.internic.net/rfc/rfc1808.txt";
--- 35,41 ----
<p>Lynx resolves partial or relative URLs in documents with respect to
the BASE if one was specified, otherwise with respect to the document's
absolute URL, using the rules described in <em>RFC1808</em>:
! <ul>
<li><a href="http://www.w3.org/pub/WWW/Addressing/rfc1808.txt";
>http://www.w3.org/pub/WWW/Addressing/rfc1808.txt</a>
<li><a href="ftp://ds.internic.net/rfc/rfc1808.txt";
***************
*** 45,51 ****
</ul>
and in subsequent drafts of the <em>IETF</em>:
! <ul plain>
<li><a href="http://www.ics.uci.edu/pub/ietf/uri/";
>Uniform Resource Identifiers (URI) Working Group</a>
</ul>
--- 43,49 ----
</ul>
and in subsequent drafts of the <em>IETF</em>:
! <ul>
<li><a href="http://www.ics.uci.edu/pub/ietf/uri/";
>Uniform Resource Identifiers (URI) Working Group</a>
</ul>
***************
*** 77,83 ****
Lynx handles http URLs exactly as specified in RFC1738. The format
is:<BR>
! <tab indent="12"><em>http://host:port/path?searchpart#fragment</em><BR>
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
--- 75,81 ----
Lynx handles http URLs exactly as specified in RFC1738. The format
is:<BR>
! <em>http://host:port/path?searchpart#fragment</em><BR>
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
***************
*** 101,107 ****
A <em>telnet</em> URL generally results in Lynx spawning a telnet
session. Lynx implements the complete telnet URL scheme, i.e.:<BR>
! <tab indent="12"><em>telnet://user:address@hidden:port</em>
<p>The <em>user</em> and/or <em>:password</em> fields may be omitted, and
the <em>@</em> should be omitted if neither is present. The port defaults
--- 99,105 ----
A <em>telnet</em> URL generally results in Lynx spawning a telnet
session. Lynx implements the complete telnet URL scheme, i.e.:<BR>
! <em>telnet://user:address@hidden:port</em>
<p>The <em>user</em> and/or <em>:password</em> fields may be omitted, and
the <em>@</em> should be omitted if neither is present. The port defaults
***************
*** 121,127 ****
<H2><a name="gopher">The <em>gopher</em> URL:</a></H2>
The gopher URL takes the form:<BR>
! <tab indent="12"><em>gopher://host:port/gopher-path</em><BR>
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
--- 119,125 ----
<H2><a name="gopher">The <em>gopher</em> URL:</a></H2>
The gopher URL takes the form:<BR>
! <em>gopher://host:port/gopher-path</em><BR>
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
***************
*** 149,157 ****
<p>For the <em>gophertype</em> which signifies HTML (<em>h</em>), if the
<em>selector</em> begins with <em>GET%20/</em> Lynx will convert the gopher
URL to an http URL, e.g.:<BR>
! <tab indent="12"><em>gopher://www.wfbr.edu:80/hGET%20/</em><BR>
will become:<BR>
! <tab indent="12"><em>http://www.wfbr.edu/</em><BR>
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
--- 147,155 ----
<p>For the <em>gophertype</em> which signifies HTML (<em>h</em>), if the
<em>selector</em> begins with <em>GET%20/</em> Lynx will convert the gopher
URL to an http URL, e.g.:<BR>
! <em>gopher://www.wfbr.edu:80/hGET%20/</em><BR>
will become:<BR>
! <em>http://www.wfbr.edu/</em><BR>
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
***************
*** 165,187 ****
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>
! <tab indent="12"><em>file://localhost/path</em><BR>
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>The <em>/path</em> is treated as originating at the root, unless
you include a tilde (<em>~</em>), e.g.:<BR>
! <tab indent="12"><em>file://localhost/~/foo</em>
! <tab indent="60">will be converted to:<BR>
! <tab indent="12"><em>file://localhost/your/login/directory/foo</em><BR>
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>On VMS, the first element of the path, if not a tilde, is assumed to
be a device, e.g.:<BR>
! <tab indent="12"
! ><em>file://localhost/www_root/directory/filename.suffix</em><BR>
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
--- 163,184 ----
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>
! <em>file://localhost/path</em><BR>
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>The <em>/path</em> is treated as originating at the root, unless
you include a tilde (<em>~</em>), e.g.:<BR>
! <em>file://localhost/~/foo</em>
! will be converted to:<BR>
! <em>file://localhost/your/login/directory/foo</em><BR>
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>On VMS, the first element of the path, if not a tilde, is assumed to
be a device, e.g.:<BR>
! <em>file://localhost/www_root/directory/filename.suffix</em><BR>
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
***************
*** 193,200 ****
<H2><a name="ftp">The <em>ftp</em> URL:</a></H2>
The ftp URL has the general format:<BR>
! <tab indent="12"
! ><em>ftp://username:address@hidden:port/path;type=[D,I, or A]</em><BR>
<p>The default port is <em>:21</em> and the default <em>username</em>
is <em>anonymous</em>. If <em>username</em> is included but not
--- 190,196 ----
<H2><a name="ftp">The <em>ftp</em> URL:</a></H2>
The ftp URL has the general format:<BR>
! <em>ftp://username:address@hidden:port/path;type=[D,I, or A]</em><BR>
<p>The default port is <em>:21</em> and the default <em>username</em>
is <em>anonymous</em>. If <em>username</em> is included but not
***************
*** 220,231 ****
VMS ftp servers, if you wish to have the first element treated as a
device rather than file or subdirectory name, begin it with a hex-escaped
slash (<em>%2f</em>), e.g.:<BR>
! <tab indent="12"><em>ftp://address@hidden/%2fsys$common/syshlp</em><BR>
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.:<BR>
! <tab indent="12"><em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em>
<p>For Unix and Unix-emulation ftp servers, RFC1738 is not respected
and the lead slash is treated as the root, i.e., the <em>/path</em> is
--- 216,227 ----
VMS ftp servers, if you wish to have the first element treated as a
device rather than file or subdirectory name, begin it with a hex-escaped
slash (<em>%2f</em>), e.g.:<BR>
! <em>ftp://address@hidden/%2fsys$common/syshlp</em><BR>
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.:<BR>
! <em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em>
<p>For Unix and Unix-emulation ftp servers, RFC1738 is not respected
and the lead slash is treated as the root, i.e., the <em>/path</em> is
***************
*** 235,250 ****
do wish to get a listing of the login directory or have the <em>path</em>
string treated as a file or path under the login directory, include a
tilde (<em>~</em>) as for <a href="#file">file</a> URLs, e.g.:<BR>
! <tab indent="12"><em>ftp://address@hidden/~</em>
<HR WIDTH="100%">
<H2><a name="wais">The <em>wais</em> URL:</a></H2>
The wais URL is used to retrieve resources using the Wide Area Information
System protocol. The format is:<BR>
! <tab indent="12"><em>wais://host:port/database</em><BR>
! <tab indent="12"><em>wais://host:port/database?wais_query</em><BR>
! <tab indent="12"><em>wais://host:port/database/wais_type/wais_path</em><BR>
where <em>:port</em> defaults to <em>:210</em>
<p>Direct wais support is built into Lynx for VMS, and can be compiled
--- 231,246 ----
do wish to get a listing of the login directory or have the <em>path</em>
string treated as a file or path under the login directory, include a
tilde (<em>~</em>) as for <a href="#file">file</a> URLs, e.g.:<BR>
! <em>ftp://address@hidden/~</em>
<HR WIDTH="100%">
<H2><a name="wais">The <em>wais</em> URL:</a></H2>
The wais URL is used to retrieve resources using the Wide Area Information
System protocol. The format is:<BR>
! <em>wais://host:port/database</em><BR>
! <em>wais://host:port/database?wais_query</em><BR>
! <em>wais://host:port/database/wais_type/wais_path</em><BR>
where <em>:port</em> defaults to <em>:210</em>
<p>Direct wais support is built into Lynx for VMS, and can be compiled
***************
*** 275,289 ****
href="#http">http and https</a>).
<p>The formats are:<BR>
! <tab indent="12"><em>news:newsgroup</em> <tab
! id="ng">(retrieves list of messages in newsgroup)<BR>
! <tab indent="12"><em>news:messageID</em> <tab
! to="ng">(retrieves the message)<BR>
! <tab indent="12"><em>news:*</em> <tab
! to="ng">(retrieves list of all available newsgroups)<BR>
! <tab indent="12"><em>nntp://host:port/newsgroup</em><BR>
! <tab indent="12"><em>nntp://host:port/messageID</em><BR>
! <tab indent="12"><em>nntp://host:port/*</em><BR>
(snews same as nntp, but the default port is <em>:563</em>)
<p>The <em>messageID</em> is the message's unique identifier, consisting
--- 271,285 ----
href="#http">http and https</a>).
<p>The formats are:<BR>
! <em>news:newsgroup</em>
! (retrieves list of messages in newsgroup)<BR>
! <em>news:messageID</em>
! (retrieves the message)<BR>
! <em>news:*</em>
! (retrieves list of all available newsgroups)<BR>
! <em>nntp://host:port/newsgroup</em><BR>
! <em>nntp://host:port/messageID</em><BR>
! <em>nntp://host:port/*</em><BR>
(snews same as nntp, but the default port is <em>:563</em>)
<p>The <em>messageID</em> is the message's unique identifier, consisting
***************
*** 292,299 ****
<p>Lynx also supports wildcarding via an asterisk for listings of news
hierarchies or sub-hierarchies, e.g.:<BR>
! <tab indent="12"><em>news:comp.infosystems.*</em><BR>
! <tab indent="12"><em>nntp://host:port/comp.infosystems.*</em><BR>
(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.
--- 288,295 ----
<p>Lynx also supports wildcarding via an asterisk for listings of news
hierarchies or sub-hierarchies, e.g.:<BR>
! <em>news:comp.infosystems.*</em><BR>
! <em>nntp://host:port/comp.infosystems.*</em><BR>
(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.
***************
*** 306,317 ****
with a supported scheme into a link for accessing that URL.
<p>Lynx also supports the newsgroup and message number URL scheme:<BR>
! <tab indent="12"><em>news:newsgroup/startNo-endNo</em> <tab
! id="ngno">(lists message range in newsgroup)<BR>
! <tab indent="12"><em>news:newsgroup/messageNo</em> <tab
! to="ngno">(retrieves the message by number)<BR>
! <tab indent="12"><em>nntp://host:port/newsgroup/startNo-endNo</em><BR>
! <tab indent="12"><em>nntp://host:port/newsgroup/messageNo</em><BR>
(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
--- 302,312 ----
with a supported scheme into a link for accessing that URL.
<p>Lynx also supports the newsgroup and message number URL scheme:<BR>
! <em>news:newsgroup/startNo-endNo</em>
! (lists message range in newsgroup)<BR>
! <em>news:newsgroup/messageNo</em>(retrieves the message by number)<BR>
! <em>nntp://host:port/newsgroup/startNo-endNo</em><BR>
! <em>nntp://host:port/newsgroup/messageNo</em><BR>
(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
***************
*** 337,346 ****
on behalf of Lynx.
<p>The formats are:<BR>
! <tab indent="12"><em>newspost://host:port/newsgroup(s)</em> <tab
! id="ngp">(post a new message)<BR>
! <tab indent="12"><em>newsreply://host:port/newsgroup(s)</em> <tab
! to="ngp">(post a followup message)<BR>
(snewspost and snewsreply have the same formats, but the default port is
<em>:563</em>)
--- 332,341 ----
on behalf of Lynx.
<p>The formats are:<BR>
! <em>newspost://host:port/newsgroup(s)</em>
! (post a new message)<BR>
! <em>newsreply://host:port/newsgroup(s)</em>
! (post a followup message)<BR>
(snewspost and snewsreply have the same formats, but the default port is
<em>:563</em>)
***************
*** 350,356 ****
be specified as a comma-separated list. Wildcarding of newgroup names
is not supported for these URLs. For newsreply and snewsreply URLs, the
user is offered the option to include the currently displayed document,
! which presumeably is a news article with a <em>followup</em> link that
was activated, and if confirmed, each line of that document is prefixed
with a right-angle-bracket. These URLs can be used as command line
startfiles (in which case, Lynx will exit after posting the message,
--- 345,351 ----
be specified as a comma-separated list. Wildcarding of newgroup names
is not supported for these URLs. For newsreply and snewsreply URLs, the
user is offered the option to include the currently displayed document,
! which presumably is a news article with a <em>followup</em> link that
was activated, and if confirmed, each line of that document is prefixed
with a right-angle-bracket. These URLs can be used as command line
startfiles (in which case, Lynx will exit after posting the message,
***************
*** 365,371 ****
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 Internet email
address (address@hidden). The format is:<BR>
! <tab indent="12"><em>mailto:address@hidden</em>
<p>The description of the mailto URL in RFC1738 has been interpreted by
some as allowing only a single recipient, but Lynx invented the mailto URL,
--- 360,366 ----
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 Internet email
address (address@hidden). The format is:<BR>
! <em>mailto:address@hidden</em>
<p>The description of the mailto URL in RFC1738 has been interpreted by
some as allowing only a single recipient, but Lynx invented the mailto URL,
***************
*** 380,396 ****
The preferred way to indicate the default Subject: for a LINK or Anchor
with a mailto HREF, or a FORM with a mailto ACTION, is via a TITLE
attribute with the subject string as its value, e.g.:<BR>
! <tab indent="12"><em><LINK <tab id="rev">REV="made"<BR>
! <tab to="rev">HREF="mailto:address@hidden,address@hidden"; TITLE="The
Subject"></em>
! <p><tab indent="12"><em><A
HREF="mailto:address@hidden"; TITLE="The Subject">...</A></em>
! <p><tab indent="12"><em><FORM <tab id="met">METHOD="post"
ENCTYPE="text/plain"<BR>
! <tab to="met">ACTION="mailto:address@hidden"; TITLE="The Subject"><BR>
! <tab indent="14">...<BR>
! <tab indent="12"></FORM></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
--- 375,391 ----
The preferred way to indicate the default Subject: for a LINK or Anchor
with a mailto HREF, or a FORM with a mailto ACTION, is via a TITLE
attribute with the subject string as its value, e.g.:<BR>
! <em><LINK REV="made"<BR>
! HREF="mailto:address@hidden,address@hidden"; TITLE="The Subject"></em>
! <p><em><A
HREF="mailto:address@hidden"; TITLE="The Subject">...</A></em>
! <p><em><FORM METHOD="post"
ENCTYPE="text/plain"<BR>
! ACTION="mailto:address@hidden"; TITLE="The Subject"><BR>
! ...<BR>
! </FORM></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
***************
*** 419,430 ****
and will use physical newlines instead of '<em>&</em>' or '<em>;</em>'
to separate the pairs, so that the content will be readable directly.
Otherwise, Lynx will mail the content with the default:<BR>
! <tab indent="12"
! ><em>ENCTYPE="application/x-www-form-urlencoded"</em> <tab id="enc">('<em
>&</em>' separates pairs)<BR>
or:<BR>
! <tab indent="12"
! ><em>ENCTYPE="application/sgml-form-urlencoded"</em> <tab to="enc">('<em
>;</em>' separates pairs)<BR>
if the latter was indicated.
--- 414,423 ----
and will use physical newlines instead of '<em>&</em>' or '<em>;</em>'
to separate the pairs, so that the content will be readable directly.
Otherwise, Lynx will mail the content with the default:<BR>
! <em>ENCTYPE="application/x-www-form-urlencoded"</em> ('<em
>&</em>' separates pairs)<BR>
or:<BR>
! <em>ENCTYPE="application/sgml-form-urlencoded"</em> ('<em
>;</em>' separates pairs)<BR>
if the latter was indicated.
***************
*** 475,485 ****
The cso URL is intended to provide a gateway to CSO/PH (QI) servers.
The requests are made on port 105 by default (<em>:105</em>), with the
following overt cso URL format:<BR>
! <tab indent="12"><em>cso://host</em><BR>
<p>You also can use a gopher URL format with port 105 and the CSO
(<em>2</em>) <em>gophertype</em> specified:<BR>
! <tab indent="12"><em>gopher://host:105/2</em>
<p>Lynx will parse the stream returned by the server for the above
URLs and create a FORM for submitting additional requests (searches)
--- 468,478 ----
The cso URL is intended to provide a gateway to CSO/PH (QI) servers.
The requests are made on port 105 by default (<em>:105</em>), with the
following overt cso URL format:<BR>
! <em>cso://host</em><BR>
<p>You also can use a gopher URL format with port 105 and the CSO
(<em>2</em>) <em>gophertype</em> specified:<BR>
! <em>gopher://host:105/2</em>
<p>Lynx will parse the stream returned by the server for the above
URLs and create a FORM for submitting additional requests (searches)
***************
*** 495,505 ****
or invoke system utilities. Any system command and associated switches
or qualifiers can be used, with the syntax appropriate for a shell running
Lynx on Unix, or for DCL on VMS, e.g.:<BR>
! <tab indent="12"><em>lynxexec:dir/date/size foo:[blah]</em> <tab
! id="listing">(VMS)<BR>
! <tab indent="12"><em>lynxexec:ls -l /foo/blah</em> <tab
! to="listing">(Unix)<BR>
! <tab indent="12"><em>lynxprog:news</em><BR>
(Note, however, that restrictions on acceptable commands or utilities
may be imposed by the system administrator.)
--- 488,498 ----
or invoke system utilities. Any system command and associated switches
or qualifiers can be used, with the syntax appropriate for a shell running
Lynx on Unix, or for DCL on VMS, e.g.:<BR>
! <em>lynxexec:dir/date/size foo:[blah]</em>
! (VMS)<BR>
! <em>lynxexec:ls -l /foo/blah</em>
! (Unix)<BR>
! <em>lynxprog:news</em><BR>
(Note, however, that restrictions on acceptable commands or utilities
may be imposed by the system administrator.)
***************
*** 519,527 ****
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:<BR>
! <tab indent="12"><em>ly<tab id="lh">
! nxcgi://localhost/path_to_CGI_script</em><BR>
! <tab to="lh">where <em>//localhost/</em> is optional and always implied.
The output of the script must be text/html and is rendered and displayed
by Lynx. (Note that restrictions on acceptable paths can be imposed
by the system administrator.)
--- 512,519 ----
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:<BR>
! <em>lynxcgi://localhost/path_to_CGI_script</em><BR>
! where <em>//localhost/</em> is optional and always implied.
The output of the script must be text/html and is rendered and displayed
by Lynx. (Note that restrictions on acceptable paths can be imposed
by the system administrator.)
***************
*** 545,558 ****
find the self-restraint to <em>resist</em> that temptation!!!
<p>For example, tempting though it might be, do <em>not</em> use these:<BR>
! <tab indent="12"
! ><em>Return to your <A HREF="LYNXHIST:0">Startfile</A></em><BR>
! <tab indent="12"
! ><em>Review your <A HREF="LYNXKEYMAP:">Keymap</A></em><BR>
(Yes, they'll work. No, they won't do any harm. But...)
<p>If you <em>must</em> try one, the second is OK from the command line:<BR>
! <tab indent="12"><em>lynx LYNXKEYMAP:</em><BR>
But within Lynx, use the '<em>K</em>' keystroke command.
</BODY>
</HTML>
--- 537,548 ----
find the self-restraint to <em>resist</em> that temptation!!!
<p>For example, tempting though it might be, do <em>not</em> use these:<BR>
! <em>Return to your <A HREF="LYNXHIST:0">Startfile</A></em><BR>
! <em>Review your <A HREF="LYNXKEYMAP:">Keymap</A></em><BR>
(Yes, they'll work. No, they won't do any harm. But...)
<p>If you <em>must</em> try one, the second is OK from the command line:<BR>
! <em>lynx LYNXKEYMAP:</em><BR>
But within Lynx, use the '<em>K</em>' keystroke command.
</BODY>
</HTML>
--
Larry W. Virden INET: address@hidden
<URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;