This is a port of Lynx 2.8.9 to MSDOS/DJGPP.


   Lynx is a fully-featured World Wide Web (WWW) client for users running
   cursor-addressable, character-cell display devices such as vt100 terminals,
   vt100 emulators running on character-cell display.  It will display Hypertext
   Markup Language (HTML) documents containing links to files on the local system,
   as well as files on remote systems running http, gopher, ftp, wais, nntp,
   finger, or cso/ph/qi servers, and services accessible via logins to telnet,
   tn3270 or rlogin accounts.


   DJGPP specific changes.
   =======================

   This port is based on the current develop code of lynx (aka lynx2.8.9dev.11)
   available as:
     http://invisible-island.net/datafiles/release/lynx-cur.tar.bz2
   and replaces the previous port based of lynx2.8.9dev.9 that has been deleted.

   The code has been adjusted to detect at runtime if LFN support is available
   or not.  If LFN support is available the original posix style file names will
   be used else DOS compatible ones will be used.

   The port will use cp850 as default code page instead of using iso-8859-1 as
   it is in the current code.  It is clear that having iso-8859-1 on plain DOS
   as character set is useless as soon as spanish, german or other non-english
   texts shall be displayed.  You can always select another character set by
   either setting the corresponding environment variable or by editing lynx.cfg
   acordingly.

   The current version of lynx requires that the HOME environment variable is
   set to a writable directory or it will refuse to start.  To alleviate this
   situation, if HOME is not set, the current directory will be used instead
   by this port version.

   The port has been configured using the configure script provided by the
   source package.  This means that neither old DJGPP specific scripts nor
   makefiles distributed by the package have been used.  Most of the porting
   work has been invested in the DJGPP specific configuration scripts.

   This port has been configured to be compiled with BZIP2, ZIP and PDCURSE
   support.  This means that if you want to recompile the preconfigured sources
   you must have installed the following ports:
     ftp://ftp.delorie.com/pub/djgpp/current/v2apps/bz2-106ar2.zip
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/zlib128br2.zip
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/pdcur34a.zip

   The port has been configured and build without NLS support enabled.  To enable
   this feature, the latest ports of libiconv and gettext must be installed:
     ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/licv114br2.zip
     ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/gtxt194b.zip
   If you prefer NLS, then reconfigure the sources passing the nls flag to the
   config.bat file.

   The port has been configured with OPENSSL support.  OpenSSL support requires
   installing the WATT-32 port.  The following ports have been used:
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/ssl101ub.zip
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/wat3222br6.zip
   No other versions have been tested.  To be able to use this program compiled
   with OpenSSL and WATT-32 a noise source must be installed.  A noise source
   can be obtained as:
     http://www.rahul.net/dkaufman/noise063a2.zip
   If for some reason you decide to reconfigure the source package, then you
   will have to set the WATT_ROOT environment variable to point to the directory
   where the headers and the library reside.  This is:
     set WATT_ROOT=/dev/env/DJDIR/net/watt

   To be able to run the program, configuration files are expected to be found
   in their canonical place.  This is the /dev/env/DJDIR/etc directory.  The
   configuration files lynx.cfg and lynx.css are stored in the /etc directory
   and reflect, to certain extent, the conditions during the configuration and
   compilation process of this port.  You may need to adjust the entries to fit
   your requiriments.  To run the program, a working version of wattcp.cfg is
   required.  This file is __NOT__ distributed with this port.  That file will
   reflect your network environment and hardware.  It is the user's job write
   one that matches his environment.  As a starting point you can use the one
   distributed with the WATT-32 port.  Please note that the location of wattcp.cfg
   must be specified by setting the WATTCP.CFG environment variable.  This can
   be done either in the environment, in autoexec.bat or in djgpp.env.

   To be able to run the program, a DOS packet driver (PKTDRVR) is required.
   This may be obtained from the card manufacturer or from one of the archives
   of packet drivers (such as "http://www.lanet.lv/simtel.net/msdos/pktdrvr-pre.html"
   or "http://ftp.freenet.de/pub/ftp.simtel.net/pub/simtelnet/msdos/pktdrvr/").
   Even when only browsing local files, a NULLPKT packet driver is required like
   nullpkt.zip.  The zip file can be downloaded as:
     http://www.jumpjet.info/Application-Software/DOS/Hardware/2/NULLPKT/NULLPKT.zip

   The lynx executable itself handles http:, https:, ftp:, file:, news:, nntp:
   and gopher: protocols. You will need external programs if you want to access
   telnet:, tn3270:, or mailto: URLs.  In this case a port of kermit may be required.

   Please note that lynx does _NOT_ support javascript at all.  So nothing will
   work that requires this feature.  If you need this, look for a different text
   web browser.

   It is important to realize that this port is a _PURE_ DOS port.  If for some
   reason you want to use lynx under Windows, you should download a windows port
   of lynx.

   If you decide to use this port as stand alone program then you __MUST__ set
   the following environment variables to point to the required configuration
   files:
     LYNX_CFG      Set to the full path and filename for lynx.cfg
     LYNX_LSS      Set to the full path and filename for lynx.lss
     WATTCP.CFG    Set to the full path for the WATTCP.CFG directory
     SSL_CERT_FILE Set to the full path and filename for your file of trusted
                   certificates
   There is a batch file stored in the /share/lynx_doc/samples directory that
   shows how to run lynx as a stand alone application.

   I have tested this port by trying to access all sites that are listed in:
     http://royal.pingdom.com/2012/06/25/using-web-browser-lynx-visit-top-websites/
   and I have experienced no issues.  I have also accessed some german and spanish
   sites to check if the special native characters are correctly displayed and
   I have found no issues.  I have also accessed www.delorie.com to check if the
   ftp support works well and if the cvs repository can be accessed via cvsweb
   interface and everthing works flawlessly.  Of course, the mail archives can
   also be accessed without issues.

   Please note that I am not a lynx user.  I have ported it as a real world test
   for the OpenSSL and WATT-32 ports.

   As usual, all djgpp specific files (config.bat, diffs, readme files, etc.)
   are located in the /djgpp directory.

   Please read the docs very __CAREFULLY__ to become familiar with the product.



   The port consists of the usual three packages produced using djdev205
   that can be downloaded from ftp.delorie.com and mirrors as (time stamp 2016-12-30):


     Lynx 2.8.9 binaries, scripts and man format documentation:
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/lynx289b.zip

     Lynx 2.8.9 html format documentation and sample files:
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/lynx289d.zip

     Lynx 2.8.9 source:
     ftp://ftp.delorie.com/pub/djgpp/current/v2tk/lynx289s.zip


   Send lynx utils specific bug reports to <lynx...@nongnu.org>.
   Send suggestions and bug reports concerning the DJGPP port to
   comp.os.msdos.djgpp or <dj...@delorie.com>.


Enjoy.

         Guerrero, Juan Manuel <juan.g...@gmx.de>
