This is a port of GNU Enscript 1.6.2 to MSDOS/DJGPP.

1.:     DJGPP specific changes.
        =======================

      - Changes needed for NLS support with DJGPP.
      - All other changes are mostly based on the previous port
        (ens150[bs].zip) done by Eli Zaretskii.
        There are no new DJGPP *specific* user *visible* changes
        except that the binaries will look for the enscript.cfg
        file and the AFM font collection at the standard places,
        this are:
        /dev/env/DJDIR/etc for enscript.cfg and
        /dev/env/DJDIR/share/enscript for the AFM fonts.
        This is a little bit different from the way the previous
        port worked. If you are familiar with the previuos version,
        you should not have any difficulties using this version.

        All changes I have done against the original GNU distribution
        are documented in the diffs file stored in the djgpp subdir
        of the source package.


2.:     Installing the binary package.
        ==============================

2.1.:   It is highly recommended to deinstall the old port (ens150b.zip) or
        (ens161b.zip) *BEFORE* installing this new one. This package will
        install the configuration file: enscript.cfg into the etc dir and the
        collection of AFM fonts into the share/enscript dir. The author of GNU
        enscript has completely changed the AFM fonts names (plain DOS clean)
        and this implies that the new files will *NOT* overwrite the old ones
        when the binary package is installed. To avoid having a lot of useless
        AFM files in the share/enscript directory and a wrong enscript.cfg file
        in share/enscript, it is *HIGHLY* recommended to deinstall the old
        enscript package before installing the new one running the command:

          rm -vf @manifest\ens150b.mft

        or

          rm -vf @manifest\ens161b.mft

        from the top DJGPP installation directory.        

2.2.:   Copy the binary distribution into the top DJGPP installation directory.
        If you are installing Enscript on a dual DOS/WINDOWS 9X systems, you
        should first turn off the generation of numeric tails for 8.3 aliases
        Windows creats for long file names. For information about how to do
        this, please read the DJGPP FAQ List V 2.30, chapter 22.19: "How to Set
        Up a Dual DOS/Windows Installation". Please note that you **MUST** turn
        off the numeric tail generation for short file names during installation
        of the binary package if you want to use the enscript program on both
        DOS window on Win9X **AND** plain DOS. If this is not done enscript and
        friends will **NOT** be able to find the .mo files (the catalog files
        containing the translated strings) on plain DOS. After the installation
        has been finished you can turn on numeric tail generation again if you
        like.

2.3.:   Copy the binary distribution into the top DJGPP installation directory
        and unzip it running *ONE* of the following commands:
          unzip32 ens12b.zip      or
          djtarx ens12b.zip       or
          pkunzip -d ens12b.zip

2.4.:   Edit the djgpp.env file which is located in the top DJGPP installation
        directory. Move to the global part of your djgpp.env and add the
        following lines:

+LANG=xx
+LANGUAGE=yy:zz

        The lines must be completely shifted to the left in your djgpp.env file.
        Please note the plus sign at the beginning of the lines. This plus sign
        allows you to overwrite the contain of the environment variable at the
        command line or from inside a batch file or shell script. The plus sign
        should **NOT** be omited or a lot of shell scripts, in this and in
        other packages, that try to reset this value will stop working. The
        LANG entry is obligatory, the LANGUAGE entry may be omited. The
        LANGUAGE variable allows you to select an alternate catalog that the
        one stipulated by LANG but the LANG variable *ALWAYS* determines the
        the DOS codepage to be used to display the translations and can not be
        omited or no tarnslations will be perfomed at all. Replace xx, yy and
        zz by the language code of the catalogs you want to use.

        Some examples:
        If you only want to use the catalog containig the translations for
        your mother tongue (in my case the spanish translations) the above
        lines will only use the LANG variable and will look like this:

+LANG=es

        If you want to use the spanish (es) and german (de) catalogs
        the above lines will look like this:

+LANG=es
+LANGUAGE=es:de

        In this case a DJGPP binary that has been compiled with NLS support
        will first search for the spanish translations. If this translations
        can not be found it will search for the german translations and if
        this can also not been found it will default to the build-in english
        messages. If you want to reverse this search order the above lines
        would look like this one:

+LANG=es
+LANGUAGE=de:es

        Please note that if you omit the LANG environment variable, the
        LANGUAGE variable will not be honuored at all. The LANG varaiable must
        always be set to your default catalog. With the aid of LANGUAGE you can
        select other catalogs apart of the default one. If for some reason you
        want to disable NLS, then you should comment out the LANG variable or
        select 'C' (uppercase `c' character) as your catalog:
+LANG=C

        Users not familiar with djgpp.env should refer to kb.info.
        This document can be read running the command:
          info -f kb -n DJGPP.ENV

2.5.:   To create an entry for the gettext info docs in your dir file run from
        the top DJGPP installation directory the command:
          install-info --info-dir=./info ./info/gettext.info

2.6.:   The binaries distributed in this package have NLS support.
        E.G. run the command:
          enscript
        and the binary should talk to you in your mother tonge, if supported.
        For futher information about GNU Enscript please read the man pages.

2.7.:   `enscript' will look for its AFM fonts library in the standard place:
          /dev/env/DJDIR/share/enscript.
        If you do not install the binary package into the DJGPP tree you will
        have to add the following entries to your DJGPP.ENV file, if they do
        not exist:

[enscript]
ENSCRIPT_LIBRARY=<ENSCRIPT_PATH>/share/enscript
+FULLNAME=<your full name>

        Replace ENSCRIPT_PATH with the path where you have installed
        the products. Put your full name into the value of FULLNAME
        (it is used by `enscript' for certain optional headers).

        If you don't have DJGPP.ENV (i.e., if you install `enscript' without
        the rest of DJGPP), just put these two variables into your environment,
        either from the DOS prompt or in your AUTOEXEC.BAT; in that case,
        replace ENSCRIPT_PATH with the name of the directory where you unzip
        the package.

2.8.:   `Enscript' comes with a library of AFM fonts (they install into the
        share/enscript directory).  If you have additional AFM fonts installed
        anywhere on your system, and you would like to make them available to
        `enscript', edit the file etc/enscript.cfg and add the directories
        where those fonts are kept to the AFMPath entry there. The syntax is
        similar to the DOS PATH variable: a list of directories separated by
        semi-colons `;'.

2.9.:   By default, `enscript' pipes its output to a spooler called `lpr', as
        it would on Unix.  Since most DOS installations don't have such a
        program, the ported version was modified to write directly to the local
        printer device if it cannot find the spooler as an executable file
        either in the current directory or along your PATH. The name of the
        default spooler can be changed from `lpr' to any other name by editing
        the "Spooler:" entry of the configuration file etc/enscript.cfg. You
        might consider using this feature if your printer doesn't have a built-
        in PostScript interpreter (put an appropriate Ghostscript command as
        the value of "Spooler:"), or if a PostScript printer is accessible via
        a LAN using a network printing utility, or if you indeed have a printer
        spooler installed.

        If you need to change the local printer port where `enscript'  writes
        its output, use the `-p' command-line option (like in -pLPT2). The
        default is "PRN" and is built into `enscript'.

2.10.:  Please read the docs.  `Enscript' has a lot of options, and you will
        benefit more if you study them carefully.

2.11.:  Some of the scripts which come with the package need Perl or Bash to
        run.  You can find DJGPP ports of these on the usual DJGPP sites.


3.:     Building the binaries from sources.
        ===================================

3.1.:   To build the binaries you will need the following binary packages:
          djdev203.zip (NOT a prior version)
          bsh203b.zip  (NOT a prior version)
          gcc2953b.zip, bnu210b.zip, mak3791b.zip,
          fil316b.zip, shl112b.zip, txt20b.zip,
          txi40b.zip, grep24b.zip, sed302b.zip,
          gtxt037b.zip, licv161b.zip, dif272b.zip,
          gwk30b.zip, flx254b.zip and bsn128b.zip.

        All this packages can be found in the v2gnu directory of any Simtel.NET
        mirror. You will need bsh203b.zip and *NOT* a prior version or the build
        will fail. The same applies to djdev203.zip. You *MUST* use the updated
        version of fil316b.zip (timestamp: 2000-05-30) and shl112b.zip
        (timestamp: 2000-08-11).
        This updated versions have been recompiled with djdev203.zip and know
        about the "/dev/env" functionality introduced with djdev203.zip. All the
        other packages are the ones I have used to build the binaries from this
        sources. Previuos versions of this packages may do the job as well but
        I have not tested this.

3.2.:   Create a temporary directory. Copy the source package: ens12s.zip
        into the directory and unzip it runnig ONE of the following commands:
          unzip32 ens12s.zip      or
          djtarx ens12s.zip       or
          pkunzip -d ens12s.zip

3.3.:   This package is preconfigured for NLS support and djdev203. This
        implies that you *MUST* install the GNU gettext library (gtxt037b.zip)
        *AND* the libiconv library (licv161b.zip) or later if you want to
        reconfigure and recompile this package. Of course, this  must be done
        *BEFORE* reconfiguring and recompiling the package. The configuration
        batch file of this package, located in the djgpp directory, allows you
        to enable or disable NLS support and to compile from a different
        partition than from where the sources are located. config.bat always
        configures the package for NLS support enabled and for in place
        compilation if no options are given. The available NLS options are:
          NLS
          no-NLS

        If for some reason you want no NLS support you will have to reconfigure
        the package. For this purpose cd into the top srcdir (enscript.16.2) and
        run the following commands:
          make distclean
          djgpp\config no-NLS

        Please note that you *MUST* use the "distclean" option or the config.cache
        file will *NOT* be deleted. In this case you are *NOT* reconfiguring
        because the configuration informations is read from the cache file instead
        of being newly computed.
        You *MUST* specify "no-NLS" or config.bat will default to the "NLS"
        option. To build the programs in a directory other than where the sources
        are, you must add the parameter that specifies the source directory,
        e.g:
          x:\src\gnu\enscript.16.2\djgpp\config x:/src/gnu/enscript.16.2 no-NLS

        Lets assume you want to build the binaries in a directory placed on a 
        different drive (z:\build in this case) from where the sources are,
        then you will run the following commands:
          z:
          md \build
          cd \build
          x:\src\gnu\enscript.16.2\djgpp\config x:/src/gnu/enscript.16.2 no-NLS

        If you want NLS support you will omit the "no-NLS" option or replace it
        by the "NLS" option in the above examples.
        The order of the NLS option and the srcdir option does *NOT* matter.
        You *MUST* use forward slashes to specify the source directory.

        This batch file will set same environment variables, make MSDOS
        specific modifications to the Makefile.ins and supply all other
        needed options to the configure script.


3.4.:   To compile the package run from the top srcdir the command:
          make

3.5.:   Now you can run the tests if you like. *BEFORE* you run the testsuite,
        you should either deinstall your old enscript package or delete/rename
        your enscript.cfg file located in the %DJDIR/etc directory or the check
        will fail (This has already reported to the enscript author). From the
        top srcdir run the command:
          make check

        Non test should fail.

3.6.:   To install the binaries, header, library, catalogs, and info docs
        run the following command from the top srcdir:
          make install CATALOGS="xx.gmo yy.gmo zz.gmo"

        This will install the products into your DJGPP installation tree given
        by the default prefix "/dev/env/DJDIR". If you prefer to install them
        into some other directory you will have to set prefix to the appropiate
        value. Replace xx, yy and zz by the language codes of the catalogs you
        want to install.
        Example:
          make install CATALOGS="xx.gmo yy.gmo zz.gmo" prefix=z:/some/other/dir

3.7.:   Now you have to set the LANG and LANGUAGE environment variable.
        Please refer to 2.4.




        Send enscript specific bug reports directely to Markku Rossi 
        at <mtr@iki.fi>.
        Send suggestions and bug reports concerning the DJGPP port to
        comp.os.msdos.djgpp or <djgpp@delorie.com>.

Enjoy.

          Guerrero, Juan Manuel <st001906@hrz1.hrz.tu-darmstadt.de>
