
w3browser Beta release version 0.1

Installing
  This package requires perl.  If you don't have it, one of the many
  places you can get it is (via ftp) from archive.cis.ohio-state.edu, 
  in pub/perl.

  At the top of w3browser, (down below the copyright) edit the
  "require" line to point to the installation location for cusses-lib.
  This might typically be /usr/local/lib/perl/cusses-lib.

  Just below that, edit the default page line.  Set it to whatever
  you want.  There is a line already there that will make it default
  to the current directory.

  Put w3browser wherever you like, and enjoy.  Press the question mark
  key for help.

Usage
  w3browser [ -pedantic | -quiet ] [ address ]

Options
  By default, it prints error messages, and keeps on going.  With -quiet,
  you can make it shut up.  With -pedantic, it will abort on the first
  problem it finds with the html.  You can combine both these options, but
  why you'd want to I'll never know.
  
Description
  This is a tty-based browser for world-wide web.  It relies on termcap
  for all screen manipulations.  The main idea is to present the information
  on the screen as close as possible to the way it would look under a
  graphically based browser.  You can scroll the screen, select buttons
  and press them, all with various keystrokes.

  If no address is given on the command line, w3browser checks for the
  environment variable WWW_HOME, and uses that if it is set.  If not,
  it uses the hard-coded default file, which in the distribution is the
  current directory, but can easily be changed to point to some file
  (see Installing, above).

  The key bindings were designed by a vi user. :-)  However, I tried to
  make them generally universal, utilizing vi, emacs, and more commands
  for the scrolling.  The key bindings are easy to change, but you have
  to edit the source - hunt for the string "browsemap=".  This should
  be broken out into a separate file.

Bugs

  Please report them to fine@cis.ohio-state.edu.  So far the testing
  hasn't included many terminal types.  I know it works well with xterms.
  If you have a terminal that seems to have problems, please send me your
  termcap entry for that terminal.  If you have a specific document that
  my browser can't parse, please send me the html source, or the address
  of the document if it is publicly available.

Misfeatures

  Probably does lots of things wrong in the HTML parsing.

  Formats UL and MENU the same.

  Can't split an anchor across (output) lines, meaning anchors must be
  shorter than the screen width.

  It really wants to be on a terminal which has underline, standout, and
  bold.  However, it will still run without them, it just may be hard to
  tell what is a button.

Currently unimplemented features

  The following protocols have not been implemented:
    gopher, wais, prospero, telnet, news

  The following HTML tags are ignored:
    HP1-HP6, NEXTID, and perhaps a few newly proposed tags

Future work

  Better history (stack history in addition to the current unique history)

  Grab key bindings from separate file.
  
  Improve the help (maybe make it an html doc generated on the fly based
  on current key bindings).

  Postscript printing

  -lint option (find all problems in given html, and quit)

  An editor???

