home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Garbo
/
Garbo.cdr
/
pc
/
source
/
pep21.arc
/
AAREAD.ME
< prev
next >
Wrap
Text File
|
1989-12-29
|
7KB
|
161 lines
RELEASE-NOTES
=============
(( This is an english language version of the norwegian file aales.meg ))
Name: pep, ver. 2.1
Author: Gisle Hannemyr, Brageveien 3A, N-0452 Oslo, Norway.
EAN: gisle@nr.uninett
Inet: gisle@ifi.uio.no
UUCP: ..!mcvax!ifi!gisle
and a number of Oslo based BBS's
Purpose: Detergent for "dirty" files
Language: K&R C
Environment: Fairly generic (CP/M, MS-DOS, UNIX, VMS)
Files: PEP21.ARC
Contents:
aaread.me -- this file
aales.meg -- norwegian version of aaread.me
hjelp.txt -- answer to questions (norwegian)
pepvms.txt -- about vms RMS (norwegian)
header.txt -- advice about portability of pep
pep.1l -- manual page (nroff source)
pep.doc -- formatted version of pep.1l
Makefile -- commands to make distribution
Makefile.unx -- commands to make distribution (Unix)
Makevms.com -- DCL script to compile and link (VMS)
ansi.c -- ansi terminal interpreter
bdmg.c -- DUCOS brain damage compensation
main.c -- root module
plain.c -- standard filter module
bdmg.h -- bdmg.c types and functions
pep.h -- types and functions for pep
pep.exe -- executable (MS-DOS)
mac2ibm -- sample conversion table
ibm2mac -- sample conversion table
ebc2ns7 -- conv.-table EBCDIC to NS 4551
ibm2ro8 -- conv.-table IBM-PC to ROMAN8
ro82ibm -- ditto
ibm2iso -- conv.-table CP 850 to ISO 8859/1
iso2ibm -- ditto
Description:
Pep is a general purpose filter and file cleaning program.
It is named after an excellent Norwegian detergent. Pep may
be used to expand/compress tabs; convert to and from several
character sets; to interprete ANSI escape sequences; and to
remove unanted line noise from files. See the file pep.doc
for a complete description.
Installation:
The steps required to install pep are:
1) Print the manual page pep.doc on paper, and read it.
2) Compile the source file pep.c to a executable file.
3) Install the executable file.
4) Install the conversion tables.
5) Modify your startup profile as required.
In more detail:
1) If you have troff or ptroff, you may want to typeset the manual.
The troff command is: troff -man pep.1l .
2) One executable file (pep.exe) for MS-DOS systems is included
in the distribution archive. If you are able to use this,
you may skip the compilation.
If you want to install pep on another operating system, you must
first compile it. Instructions for compilation on several common
systems are at the start of the source file. A makefile is
also supplied. Pep is fairly generic and should compile with
almost any C-compiler after very little tweaking. Read the file
"header.txt" for advise about what pep expect to find in the
header files.
3) The executable will be named pep.exe, pep.com, pep.cmd or just
pep, depending upon which operating system you are using. See
operating system notes below for recommended placement.
4) This are the files named mac2ibm, ro82ibm, ibm2ro8, etc.
You may want to add your conversion tables, which should be
installed in the same directory as those in the distribution.
As with executables, see the notes below for hints about where
tables should be installed on different systems.
5) Pep uses one environment variable: PEP, which should be defined
in the startup profile if possible.
Operating system notes:
Below is some notes on points pertaining to the different operating
systems:
* CP/M systems:
Install the executable file and the conversion filters under
user 0. CP/M does not have a startup profile or environment
variables.
* MS-DOS systems:
Install PEP.EXE in a directory that is defined in your PATH
environment variable, and define an environment variable PEP
pointing to the directory where the conversion filters are
installed. If this is "c:\usr\lib" your startup profile
AUTOEXEC.BAT should contain a line like this:
set PEP=c:\usr\lib
Alternatively, you may put the conversion tables in the same
directory as you put the executables. If you use this alternative,
it is not necessary to define the PEP environment variable.
* UNIX systems:
Install the executable file pep in a directory that is defined
in your PATH environment variable (a canonical place will be
/usr/local/bin). Install the conversion table in a directory of
your choice (a canonical place will be /usr/local/lib).
Define an environment variable PEP pointing to the directory where
the conversion filters are installed. If this is "/usr/local/lib"
your startup profile (.login on BSD systems, .profile on SYS-V)
should contain a line like this:
setenv PEP /usr/local/lib
Also, Unix users may want to install the manpage "pep.1l" in the
online manual. The canonical placement is /usr/man/manl.
* VMS systems:
Pep need to be installed as a "foreign command", and you need
to define a symbol pointing to the conversion filters. If both
the executable file and the filters is placed in directory named
"disk_daf:<d_progbib.vms>", you need to have the following two
lines in your startup profile LOGIN.COM.
$ pep :== $disk_daf:<d_progbib.vms>pep
$ define PEP "disk_daf:<d_progbib.vms>"
Incidently, this is where pep is installed on the University of
Oslo VMS Vax cluster. If you have an account on one of the
machines in this cluster, having the two lines above in your
LOGIN.COM is all you need to use pep on these machines.
Also note that VMS does not support pipes and redirection, and
it is therefore awkward to use pep as a filter under VMS. The
distributed version does not even try to run as a filter under
VMS, it has the -o option (write output back on file named as
input file) permanently enabled.
Version 2.1, news:
* The -u option is expanded to allow user's to specify canonical
line terminator.
* New option: -v, to make pep generate hard line terminators only
between paragraphs.
* New conversion table "ebc2ns7" for EBCDIC and DisplayWrite.
* Some old conversion tables are expanded.
* Bugfixes.
..EOF