This is a port of GNU Shar utilities 4.2c to MSDOS/DJGPP.

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

     1) Changes needed for NLS support with DJGPP.
     2) All other changes concern the treatement of the usual
        MSDOS specific issues:
          - fork/pipe replacement.
          - binary/text file distinction.
          - path separator (semi-colon instead of colon) and
            dir separator (mixed backslash and slash) issue.
          - no multiple dots in a file name.
        The programs (shar, unshar, uuencode and uudecode) will always
        read and write files in binary mode, if possible.


        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.:   Copy the binary distribution into the top DJGPP installation
        directory. If you are installing Recode on 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 recode program on both DOS box on Win9X **AND**
        plain DOS. If this is not done shar and the other programs will
        **NOT** be able to find the .mo files (the catalogs containing the
        translated strings) on plain DOS.
        After the installation has been finished you can turn on numeric tail
        generation again if you like.
        Unzip the binary distribution running *ONE* of the following
        commands:
          unzip32 shar42cb.zip      or
          djtarx shar42cb.zip       or
          pkunzip -d shar42cb.zip

2.2.:   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 line:

+LANGUAGE=xx:yy:zz

        Please notice that the line must be completely shifted to the left
        in your djgpp.env file and that it starts with a plus sign. This plus
        allows you to change the value of LANGUAGE at the DOS command line.
        This 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.
        Replace xx, yy and zz by the country code of the catalogs you want
        to use.

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

2.4.:   The binaries distributed in this package have NLS support.
        I.E. run the command:
          shar
        and the binary should talk to you in your mother tonge, if
        supported.
        For futher information about GNU Shar utilities please read
        the info docs and man pages.

2.5.:   For unshar'ing an archive you will need *AT LEAST* bash and sed.
        Probably you will need also grep, gzip, fileutils, shellutils,
        textutils, uuencode and uudecode. This depends on the kind of
        archive you want to create or extract. shar and unshar rely
        on the availability of certain programs on the system where they
        are executed.
        Once again, please **READ** the docs.


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)
          gcc2952b.zip, bnu2951b.zip, mak3791b.zip,
          fil316b.zip, shl112b.zip, txt20b.zip,
          txi40b.zip, grep24b.zip, sed302b.zip,
          gtxt035b.zip, rcode35.zip and diff272b.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 (date: 2000-05-30) and shl112b.zip (date: 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: shar42cs.zip
        into the directory and unzip it runnig ONE of the following commands:
          unzip32 shar42cs.zip      or
          djtarx shar42cs.zip       or
          pkunzip -d shar42cs.zip

3.3.:   This package is preconfigured for NLS support and djdev203. This
        implies that you *MUST* install the GNU gettext library (gtxt035b.zip)
        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 (sharutil.42c) 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\sharutil.42c\djgpp\config x:/src/gnu/sharutil.42c 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\sharutil.42c\djgpp\config x:/src/gnu/sharutil.42c 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. 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 LANGUAGE environment variable.
        Please refer to 2.2.


4.:     Recodeing the .po files.
        ========================

        As told above, the .po files of this package have already been recoded.
        The recodeing of the .po files is one step more of the configuration
        process of the package and does usualy not need to be repeated by the
        user. This step is performed automatically by config.bat running the
        recodepo.sh shell script. This shell scripts uses two arguments:
        1: the name of the unix charset that have been used to write the
           .po file. This information is extracted from the .po file by the
           shell script itself.
        2: The number of the MSDOS code page corresponding to that particular
           .po file. This information is stored in the DosCodePage array of
           the shell script. The code page numbers have been taken from 
           MS-DOS 6.22 COUNTRY.TXT file and this code pages are the ones
           installed during a standard MSDOS installation process.
        Because this standard code pages have been used to recode the .po files,
        the distributed ones should fit the requirements of the majority of
        the users. If for some reason this is not true for you, you will have
        to recode the .po files manually. This packages supplies the original
        (not recoded) .po files in the po/po.orig directory. Cd into po/po.orig
        and edit the .po file you want to use. Search for a line that looks like:
          "Content-Type: text/plain; charset=ISO-8859-1\n"
        The unix charset used in this particular .po file is ISO-8859-1.
        If you are using the MSDOS code page 437 you will recode the .po file
        running the command:
          recode -Spo ISO-8859-1..cp437 xx.po
        where xx stands for the country code.
        If you want to recode all .po files you will proceed as follows:
        1) Cd into the po directory.
        2) Delete all .po files and stamp-po.
        3) Copy the original .po files from po.orig directory into the po directory.
        4) Edit recodepo.sh. Search for the DosCodePage array and make the appropiate
           changes.
        4) Run the command:
             sh recodepo.sh


        Send sharutils specific bug reports to <bug-gnu-utils@gnu.org>.
        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>
