    Permission for use of this software is granted only if the user accepts
full responsibility for any undesirable consequences; the authors accept
NO LIABILITY for damages of any kind. In addition the authors make NO WARRANTY 
or representation, either expressed or implied, with respect to this software, 
its quality, accuracy, merchantability, or fitness for a particular purpose.  
This software is provided "AS IS", and you, its user, assume the entire risk 
as to its quality and accuracy.

    This software may be redistributed as long as this notice remains with
the software.

    This software is based in part on the work of the Independent JPEG Group.

    Having said the legal stuff I must say that every attempt by the author has
been made to make this a usefull software package. We are trying very hard to
please the users of Bulldozer by supplying a reliable and usefull tool for
creating HTML documents. However, it is still in it's beta versions. There are
probably several bugs and things that just could be done better. I would 
like to hear from you as to the fitness, usefullness and bugginess of 
BullDozer in relation to your specific use. Please refer to the site...

http://cscsun1.larc.nasa.gov/~rboykin/Dozer/

for bug reports and other cool stuff related to Bulldozer.

    Thank you for trying Bulldozer 0.7.1.

A few things to get you started....

    The files are probably in the form.

dozer-(VERSION).(OS).(OS VERSION).tar.gz

or

dozer-(VERSION).(OS).(OS VERSION).tgz

or
 
dozer-(VERSION).(OS).(OS VERSION).tgz.bin

If you have a file that looks something like the latter case (ends in .bin),
move that file to the dozer-(VERSION).(OS).(OS VERSION).tgz form. That is
just remove the .bin form the file name. Now what you do is something like...

gzip -d dozer-(VERSION).(OS).(OS VERSION).tgz

or

gzip -d dozer-(VERSION).(OS).(OS VERSION).tar.gz

Which ever may be your case. That will get you a file with the name of the 
form...

dozer-(VERSION).(OS).(OS VERSION).tar

Now do a...

tar xovf dozer-(VERSION).(OS).(OS VERSION).tar

If everything worked OK you can do a...

rm dozer-(VERSION).(OS).(OS VERSION).tar

    All of that created a directory dozer-(VERSION) in the directory you
did the tar command in. cd to that directory and you will find a file called
setup. Don't run it until you have modified it.

    The installation script simply copies the binary to the 
appropriate place and copies the documents to the lib directory.

    Edit setup to determine a proper place for installation then
execute setup.

    The environment variable BULLDOZERLIB needs to point to the lib 
directory. If if is not set you just simply will not get any help pages.
BTW, the help pages are out of date. 

    If you get errors when running dozer of the form...

Warning: translation table syntax error: Unknown keysym name: osfLeft

you need to install the XKeysymDB. A copy of the X consortium's XKeysymDB
is included and will be installed in the library directory specified
in the setup script. To use that database either have your system administrator
install it or set the environment variable XKEYSYMDB to the location
of that file. (eg. setenv XKEYSYMDB /usr/local/dozer-0.7.1/lib/XKeysymDB)

    If your running on an SGI terminal you may experience colors that are
just to intense. This is due to the normal gamma value the SGI display
uses. Included in the installation libbrary director is the default
application defaults file for dozer. Within the top of the file there
are defaults for colors. To use the colors best used on an SGI uncomment
the appropriate lines. It should be obvious. Be sure to comment the
line in the section immediately following so as not to ignore what you are
trying to achieve. To use the app defaults file either have you system 
administrator install them or set the environment variable XENVIRONMENT to
the file. (eg. setenv XENVIRONMENT /usr/local/dozer-0.7.1/lib/Dozer.ad).
Notice the filename is included in the path specification. 

    For an overview and some simple instructions on the program choose the 
Attention Beta Testers... menu choice from the help menu.... 

-Rick Boykin
r.m.boykin@larc.nasa.gov

