[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev dev.16 patch 2 - minor doc changes
lynx-dev dev.16 patch 2 - minor doc changes
Sat, 4 Dec 1999 02:22:15 -0600 (CST)
Minor doc tweaks.
--- 1.22/src/LYMain.c Sat, 04 Dec 1999 00:06:06 -0600
+++ 2.30/src/LYMain.c Sat, 04 Dec 1999 01:44:26 -0600
@@ -3190,7 +3190,7 @@
"force_empty_hrefless_a", SET_ARG, &force_empty_hrefless_a,
- "force HREF-less 'A' elements to be empy (close them as soon as they are
+ "force HREF-less 'A' elements to be empty (close them as soon as they
"force_html", SET_ARG, &LYforce_HTML_mode,
@@ -3208,7 +3208,7 @@
"from", TOGGLE_ARG, &LYNoFromHeader,
- "toggle transmissions of From headers"
+ "toggle transmission of From headers"
"ftp", UNSET_ARG, &ftp_ok,
@@ -3326,7 +3326,7 @@
#endif /* EXEC_LINKS || EXEC_SCRIPTS */
"nofilereferer", SET_ARG, &no_filereferer,
- "disable transmissions of Referer headers for file URLs"
+ "disable transmission of Referer headers for file URLs"
"nolist", SET_ARG, &nolist,
@@ -3356,7 +3356,7 @@
"noreferer", SET_ARG, &LYNoRefererHeader,
- "disable transmissions of Referer headers"
+ "disable transmission of Referer headers"
"noreverse", FUNCTION_ARG, noreverse_fun,
--- 1.22/INSTALLATION Sat, 04 Dec 1999 00:06:06 -0600
+++ 2.30/INSTALLATION Sat, 04 Dec 1999 01:44:26 -0600
@@ -201,7 +201,7 @@
disabled DirEd completely, you can ignore all the more specific
- All DirEd key functions that were enabled on compilation can be
+ All DirEd menu functions that were enabled on compilation can be
disabled or modified at run time via DIRED_MENU symbols in lynx.cfg.
--disable-dired-dearchive (define ARCHIVE_ONLY)
--- 1.22/lynx_help/Lynx_users_guide.html Sat, 04 Dec 1999 00:06:06 -0600
+++ 2.30/lynx_help/Lynx_users_guide.html Sat, 04 Dec 1999 01:54:52 -0600
@@ -1378,7 +1378,8 @@
only non-hidden field in the form.
If <A NAME="tna">"Textfields Need Activation"</A> mode is turned on
- (with the <kbd>-tna</kbd> command-line option),
+ (with the <kbd>-tna</kbd> command-line option or in <A HREF="#lynx.cfg"
then text entry fields do not become active immediately upon being
selected, as normally. Keystrokes have their normal command meaning
unless the Line Editor gets activated with <em>Return</em> or <em>Right
@@ -1414,14 +1415,18 @@
To avoid confusion, either of these separate functions could be changed
(mapped away) with a KEYMAP directive in <em>lynx.cfg</em>. For
would map SWITCH_DTD away from <em>^V</em> to <em>#</em>, while leaving
its default Line Editor function as a command escape in place. On the
- other hand,<br>
+ other hand,
would move <em>^V</em>'s Line Editor binding as command escape to
<em>^_</em> for the first Line Edit style, letting <em>^V</em> still
act as SWITCH_DTD
@@ -1488,7 +1493,7 @@
adds a new line to the TEXTAREA, with the cursor on it.<p>
If you have some single keys (or control keys) to spare that you
- do not need for their normal purposes, you can dedicated those keys
+ do not need for their normal purposes, you can dedicate those keys
to invoke the special functions (without requiring a prefix key).
For example, to use
the <em>^E</em> key for the DWIMEDIT action, and
--- 1.22/lynx_help/lynx_url_support.html Sat, 04 Dec 1999 00:06:06 -0600
+++ 2.30/lynx_help/lynx_url_support.html Fri, 03 Dec 1999 04:54:03 -0600
@@ -594,7 +594,7 @@
<H2><a name="internal">The <em>LYNXfoo</em> internal URLs:</a></H2>
-Lynx uses a variety of private URL schemes form communication among its
+Lynx uses a variety of private URL schemes for communication among its
internal modules. They start with uppercase letters <code>LYNX</code>
by convention, although, as input, URL schemes are recognized in a
@@ -604,7 +604,7 @@
<UL><LI>There already is too much browser-specific markup around...
<LI>The schemes, or their meanings, may change between Lynx versions.
<LI>Even if a scheme stays the same, some aspect of its behavior may
- be modified without notice, or the context in which it is allows
+ be modified without notice, or the context in which it is allowed
<LI>If it doesn't work as expected when used outside of the intended
purpose, don't expect anyone to "fix" it.
@@ -622,7 +622,7 @@
But within Lynx, use the '<em>K</em>' keystroke command.
-Sometimes it may be convenient to use an internal scheme with
+Sometimes it may be convenient to use a private scheme with
'<em>g</em>'oto, as in:
--- 1.22/samples/lynx-keymaps Sat, 04 Dec 1999 00:06:06 -0600
+++ 2.30/samples/lynx-keymaps Fri, 03 Dec 1999 04:54:03 -0600
@@ -131,7 +131,7 @@
#setkey "\033e" Meta-'e'
#setkey "\033\033[28~" Meta-F1
-# The following extensions, introduced after lynx2.8.2, allow you to map
+# The following extensions, introduced after lynx2.8.2, allow mapping
# escape sequences directly to key commands (lynxactioncodes).
# setkey ESC-SEQUENCE LAC:LYNX_ACTION
--- 1.22/docs/README.TRST Sat, 04 Dec 1999 00:06:06 -0600
+++ 2.30/docs/README.TRST Sat, 04 Dec 1999 01:44:26 -0600
@@ -47,7 +47,7 @@
And that's exactly what TRST does. An implementation based on the
simple observation above is relatively straightforward, for simple
tables. On encountering the start of a TABLE element, Lynx generates
-output as unusual for LMTS. But it also keeps track of cell positions
+output as usual for LMTS. But it also keeps track of cell positions
and lengths in parallel. If all goes well, that additional information
is used to fix up the already formatted output lines when the TABLE
ends. If not all goes well, the table was not 'simple' enough, the
- lynx-dev dev.16 patch 2 - minor doc changes,
Klaus Weide <=