snapshot of project "lynx", label v2-8-2dev_9

1 files changed, 86 insertions, 77 deletions

diff --git a/INSTALLATION b/INSTALLATION
index d9f02ba9..f331159e 100644
--- a/INSTALLATION
+++ b/INSTALLATION
@@ -60,19 +60,9 @@ Step 4. (optional -- news for UNIX and VMS)
     in userdefs.h or lynx.cfg so that it points to users' signature files
     for appending to posted messages.
 
-Step 5. (optional -- UNIX only)
-    To add direct WAIS support, get the freeWAIS distribution from
-    "ftp://ftp.cnidr.org/pub/NIDR.tools/freewais", and compile it.  The
-    compile process will create the libraries you will need, wais.a and
-    client.a.  Edit the generated makefile in the top level directory and
-    add the library locations under the DIRECT WAIS ACCESS heading.  Edit
-    "WWW/Library/Implementation/CommonMakefile" to point to the include
-    directory for the freewais distribution.  Precompiled libraries are
-    available for many platforms if you don't wish to compile one yourself.
-
-Step 6. (Anonymous account -- VERY IMPORTANT!!!!! -- )
+Step 5. (Anonymous account -- VERY IMPORTANT!!!!! -- )
     If you are building Lynx for your personal use only you may skip this
-    step. If you are setting up an anonymous account with Lynx, you are
+    step.  If you are setting up an anonymous account with Lynx, you are
     STRONGLY advised to use the -anonymous command line option.  If you do
     not use this option, users may be able to gain access to all readable
     files on your machine!  ALSO NOTE that many implementations of telnetd
@@ -286,7 +276,10 @@ II. Compile instructions -- UNIX
   --enable-font-switch			(define EXP_CHARTRANS_AUTOSWITCH)
 	Allow Lynx to automatically change the Linux console state (switch
 	fonts) according to the current Display Character Set.  (Linux console
-        only.  *Use with discretion.*  See docs/README.chartrans.)
+	only.  *Use with discretion.*  See docs/README.chartrans.)
+
+  --enable-gzip-help
+	Install the lynx help files in gzip'd format [*.gz] to save space.
 
   --enable-internal-links		(define DONT_TRACK_INTERNAL_LINKS)
 	Disabled by default, this option allows tracking of internal links,
@@ -337,6 +330,12 @@ II. Compile instructions -- UNIX
 	use the GNU gettext library included here (default).  See
 	"--enable-nls".
 
+  --with-nls-datadir=DIR
+	Use this option to override the configure script's NLS data directory,
+	under which the locale (i.e., language) files are installed.  The
+	default value is derived at configure time, and depends on whether GNU
+	or native gettext is used.
+
   --with-screen=XXX
 	Use this option to select the screen type.  The option value,
 	XXX must be one of curses (the default), ncurses or slang.
@@ -436,6 +435,16 @@ II. Compile instructions -- UNIX
     top-level Makefile, and instructions on how to compile are given in
     "docs/INSTALLATION.old".
 
+3. Wais support (optional)
+    To add direct WAIS support, get the freeWAIS distribution from
+    "ftp://ftp.cnidr.org/pub/NIDR.tools/freewais", and compile it.  The compile
+    process will create the libraries you will need, wais.a and client.a.  Edit
+    the Makefile in the top level directory and add the library locations under
+    the DIRECT WAIS ACCESS heading.  Edit the Makefile for the WWW Library in
+    "WWW/Library/Implementation/CommonMakefile" to point to the include
+    directory for the freewais distribution.  Precompiled libraries are
+    available for many platforms if you don't wish to compile one yourself.
+
 
 III. Compile instructions -- VMS
 
@@ -458,7 +467,7 @@ Step 2.  Passive FTP
     If your system requires the PASV FTP code instead of the standard
     PORT FTP code (e.g., to deal with a firewall) then edit "WWW/Library/
     Implementation/HTFTP.c" and comment out line 43 like so:
-             /*  #define LISTEN   /* @@@@ Test LJM */.
+	     /*  #define LISTEN   /* @@@@ Test LJM */.
 
 Step 3a.
     Lynx uses the VMS port of gzip for uncompressing streams which have
@@ -475,10 +484,10 @@ Step 3a.
     or slang is in the top level directory.  All you have to do is type
     "@build" or "@build-slang" and answer its prompt for your system's TCP-IP
     software.  Current choices are:
-           MULTINET (default)
+	   MULTINET (default)
 	   UCX
 	   WIN_TCP
-           CMU_TCP
+	   CMU_TCP
 	   SOCKETSHR_TCP
 	   TCPWARE
     It will autosense whether you have VAXC, DECC or GNUC on VAX or AXP and
@@ -575,14 +584,14 @@ V. Compile instructions -- 386 DOS
 
     Compiling for DOS with DJGPP is a multistep procedure.  First install
     the c compiler and its libraries.  Update the distribution with the
-    patched lib.c, to take care of bug fixes. It is available at:
+    patched lib.c, to take care of bug fixes.  It is available at:
     "http://www.cartsys.com/eldredge/djgpp-patches.html".
     DJGPP, as distributed from the usual DJGPP archives, will
-    not successfully compile lynx. You need to "stubedit" your
-    "cc1.exe" file. The following parameters have worked successfully:
-    minstack=800k, bufsize=64k. To accomplish this, move to the
+    not successfully compile lynx.  You need to "stubedit" your
+    "cc1.exe" file.  The following parameters have worked successfully:
+    minstack=800k, bufsize=64k.  To accomplish this, move to the
     djgpp\bin directory and type the command:
-        "stubedit cc1.exe bufsize=64k minstack=800k".
+	"stubedit cc1.exe bufsize=64k minstack=800k".
     Or do it interactively with the command: "stubedit cc1.exe".
     (see "http://www.flora.org/lynx-dev/html/month0897/msg00145.html").
 
@@ -607,7 +616,7 @@ V. Compile instructions -- 386 DOS
     (available in two different versions at "ftp://neonatal.sm.med.ic.ac.uk/"
     and in "http://www.fdisk.com/doslynx/wlynx/source/djgpp.zip"). You
     can also use slang ("ftp://space.mit.edu/pub/davis/slang") as your
-    curses library. You need to compile these before you go any further.
+    curses library.  You need to compile these before you go any further.
     If you wish to use PDCurses 2.3, you need to first apply the
     following patch:
 
@@ -627,7 +636,7 @@ V. Compile instructions -- 386 DOS
     If you have trouble applying the patch, we recommend
     that you use the "patch" program,
     ("http://www.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/pat25b.zip"). The
-    WATTCP TCPLIB sources also need to be patched prior to compilation. See
+    WATTCP TCPLIB sources also need to be patched prior to compilation.  See
     "http://www.flora.org/lynx-dev/html/month1197/msg00403.html".
 
     To read the Unix man style documentation, use, for example, "less"
@@ -640,17 +649,17 @@ V. Compile instructions -- 386 DOS
     and INCLUDE_PATH in your DJGPP.ENV file.
 
     Move to the "lynx2-*/WWW/Library/djgpp" directory and do "make". This
-    should compile libwww.a. Next move to the "lynx2-*/src/chrtrans"
+    should compile libwww.a.  Next move to the "lynx2-*/src/chrtrans"
     directory and do "make -f makefile.dos" to compile the character tables.
-    Then move to the "lynx2-*/src" directory. There are three choices for
-    compiling at this point. You can do "make -f makefile.dos" to compile
+    Then move to the "lynx2-*/src" directory.  There are three choices for
+    compiling at this point.  You can do "make -f makefile.dos" to compile
     with PDCurses, "make -f makefile.wsl" to compile with SLANG, or
     "make -f makefile.dsl" to compile with SLANG and the DJGPP keyhandler.
     At the time of this writing, it is not clear what the advantages and
-    disadvantages of each version are. The PDCurses version has the most
-    experience and allows remapping of ALT and Function keys. The SLANG
-    version seems to have better screen handling. It allows mapping of
-    function keys, but not ALT keys. The SLANG with DJGPP keyhandler allows
+    disadvantages of each version are.  The PDCurses version has the most
+    experience and allows remapping of ALT and Function keys.  The SLANG
+    version seems to have better screen handling.  It allows mapping of
+    function keys, but not ALT keys.  The SLANG with DJGPP keyhandler allows
     mapping of ALT and Function keys, but has the risk of incompatibilities
     from mixing different programs.
 
@@ -812,51 +821,51 @@ VII. Setting environment variables before running Lynx (optional)
     the older gateway servers.  Each protocol used by Lynx can be mapped
     separately using PROTOCOL_proxy environment variables of the form:
 
-        UNIX
-                setenv http_proxy "http://some.server.dom:port/"
-                setenv https_proxy "http://some.server.dom:port/"
-                setenv ftp_proxy "http://some.server.dom:port/"
-                setenv gopher_proxy "http://some.server.dom:port/"
-                setenv news_proxy "http://some.server.dom:port/"
-                setenv newspost_proxy "http://some.server.dom:port/"
-                setenv newsreply_proxy "http://some.server.dom:port/"
-                setenv snews_proxy "http://some.server.dom:port/"
-                setenv snewspost_proxy "http://some.server.dom:port/"
-                setenv snewsreply_proxy "http://some.server.dom:port/"
-                setenv nntp_proxy "http://some.server.dom:port/"
-                setenv wais_proxy "http://some.server.dom:port/"
-                setenv finger_proxy "http://some.server.dom:port/"
-                setenv cso_proxy "http://some.server.dom:port/"
-
-        VMS
-                define "http_proxy" "http://some.server.dom:port/"
-                define "https_proxy" "http://some.server.dom:port/"
-                define "ftp_proxy" "http://some.server.dom:port/"
-                define "gopher_proxy" "http://some.server.dom:port/"
-                define "news_proxy" "http://some.server.dom:port/"
-                define "newspost_proxy" "http://some.server.dom:port/"
-                define "newsreply_proxy" "http://some.server.dom:port/"
-                define "snews_proxy" "http://some.server.dom:port/"
-                define "snewspost_proxy" "http://some.server.dom:port/"
-                define "snewsreply_proxy" "http://some.server.dom:port/"
-                define "nntp_proxy" "http://some.server.dom:port/"
-                define "wais_proxy" "http://some.server.dom:port/"
-                define "finger_proxy" "http://some.server.dom:port/"
-                define "cso_proxy" "http://some.server.dom:port/"
-                (Encase *BOTH* strings in double-quotes to maintain
+	UNIX
+		setenv http_proxy "http://some.server.dom:port/"
+		setenv https_proxy "http://some.server.dom:port/"
+		setenv ftp_proxy "http://some.server.dom:port/"
+		setenv gopher_proxy "http://some.server.dom:port/"
+		setenv news_proxy "http://some.server.dom:port/"
+		setenv newspost_proxy "http://some.server.dom:port/"
+		setenv newsreply_proxy "http://some.server.dom:port/"
+		setenv snews_proxy "http://some.server.dom:port/"
+		setenv snewspost_proxy "http://some.server.dom:port/"
+		setenv snewsreply_proxy "http://some.server.dom:port/"
+		setenv nntp_proxy "http://some.server.dom:port/"
+		setenv wais_proxy "http://some.server.dom:port/"
+		setenv finger_proxy "http://some.server.dom:port/"
+		setenv cso_proxy "http://some.server.dom:port/"
+
+	VMS
+		define "http_proxy" "http://some.server.dom:port/"
+		define "https_proxy" "http://some.server.dom:port/"
+		define "ftp_proxy" "http://some.server.dom:port/"
+		define "gopher_proxy" "http://some.server.dom:port/"
+		define "news_proxy" "http://some.server.dom:port/"
+		define "newspost_proxy" "http://some.server.dom:port/"
+		define "newsreply_proxy" "http://some.server.dom:port/"
+		define "snews_proxy" "http://some.server.dom:port/"
+		define "snewspost_proxy" "http://some.server.dom:port/"
+		define "snewsreply_proxy" "http://some.server.dom:port/"
+		define "nntp_proxy" "http://some.server.dom:port/"
+		define "wais_proxy" "http://some.server.dom:port/"
+		define "finger_proxy" "http://some.server.dom:port/"
+		define "cso_proxy" "http://some.server.dom:port/"
+		(Encase *BOTH* strings in double-quotes to maintain
 		 lower case for the PROTOCOL_proxy variable and for
 		 the http access type; include /system if you want
 		 proxying for all clients on your system.)
 
     If you wish to override the use of a proxy server for specific hosts or
-    entire domains you may use the "no_proxy" environment variable. Here is
+    entire domains you may use the "no_proxy" environment variable.  Here is
     an example use of "no_proxy":
 
-        UNIX
-                setenv no_proxy "host.domain.dom, domain1.dom, domain2"
+	UNIX
+		setenv no_proxy "host.domain.dom, domain1.dom, domain2"
 
-        VMS
-                define "no_proxy" "host.domain.dom, domain1.dom, domain2"
+	VMS
+		define "no_proxy" "host.domain.dom, domain1.dom, domain2"
 
     You can include a port number in the no_proxy list to override use
     of a proxy server for the host accessed via that port, but not via
@@ -887,9 +896,9 @@ VII. Setting environment variables before running Lynx (optional)
    "readme.dos" by Doug Kaufman)
 
     Here are some environment variables that should be set, usually in a
-    batch file that runs the lynx executable. Make sure that you have enough
-    room left in your environment. You may need to change your "SHELL="
-    setting in config.sys. In addition, lynx looks for a "SHELL" environment
+    batch file that runs the lynx executable.  Make sure that you have enough
+    room left in your environment.  You may need to change your "SHELL="
+    setting in config.sys.  In addition, lynx looks for a "SHELL" environment
     variable when shelling to DOS.  If  you wish to preserve the environment
     space when shelling, put a line like this in your AUTOEXEC.BAT file also
     "SET SHELL=C:\COMMAND.COM /E:2048". It should match CONFIG.SYS.
@@ -913,16 +922,16 @@ VII. Setting environment variables before running Lynx (optional)
 
     In lynx_386, a typical batch file might look like:
 
-        @echo off
-        set HOME=f:/lynx2-8
-        set USER=your_login_name
-        set LYNX_CFG=%HOME%/lynx.cfg
-        set WATTCP.CFG=%HOME%
-        f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9
+	@echo off
+	set HOME=f:/lynx2-8
+	set USER=your_login_name
+	set LYNX_CFG=%HOME%/lynx.cfg
+	set WATTCP.CFG=%HOME%
+	f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9
 
     You will also need to make sure that the WATTCP.CFG file has the
     correct information for IP number, Gateway, Netmask, and Domain Name
-    Server. This can also be automated in the batch file.
+    Server.  This can also be automated in the batch file.
 
 
 VIII. Acknowledgment