From 3e4b187b7b9f0325d4834a233c8084df61b52a85 Mon Sep 17 00:00:00 2001 From: Tim Retout Date: Sat, 6 Mar 2010 12:47:19 +0000 Subject: [PATCH] Use standard INSTALL file, and replace old addresses in README. Signed-off-by: Tim Retout --- ChangeLog | 4 + INSTALL | 259 ------------------------------------------------------ README | 102 ++++++++++++++++----- 3 files changed, 85 insertions(+), 280 deletions(-) delete mode 100644 INSTALL diff --git a/ChangeLog b/ChangeLog index 1d66859..e737de6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -2,6 +2,10 @@ * states/hl/Makefile.am (highlightings): Add f90.st. + * INSTALL: Move enscript-specific details into README, and remove + from the repository (i.e. just use the standard INSTALL file). + * README: Replace all old web/mail addresses. + 2010-02-03 Tim Retout * All ChangeLog files in subdirectories have been renamed to diff --git a/INSTALL b/INSTALL deleted file mode 100644 index c99209e..0000000 --- a/INSTALL +++ /dev/null @@ -1,259 +0,0 @@ -Basic Installation -================== - - These are installation instructions for GNU enscript. The top of - this file describes how to compile and install the software; at the - bottom are instructions for configuring enscript. - - The `configure' shell script attempts to guess correct values for -various system-dependent variables used during compilation. It uses -those values to create a `Makefile' in each directory of the package. -It may also create one or more `.h' files containing system-dependent -definitions. Finally, it creates a shell script `config.status' that -you can run in the future to recreate the current configuration, a file -`config.cache' that saves the results of its tests to speed up -reconfiguring, and a file `config.log' containing compiler output -(useful mainly for debugging `configure'). - - If you need to do unusual things to compile the package, please try -to figure out how `configure' could check whether to do them, and mail -diffs or instructions to the address given in the `README' so they can -be considered for the next release. If at some point `config.cache' -contains results you don't want to keep, you may remove or edit it. - - The file `configure.in' is used to create `configure' by a program -called `autoconf'. You only need `configure.in' if you want to change -it or regenerate `configure' using a newer version of `autoconf'. - -The simplest way to compile this package is: - - 1. `cd' to the directory containing the package's source code and type - `./configure' to configure the package for your system. If you're - using `csh' on an old version of System V, you might need to type - `sh ./configure' instead to prevent `csh' from trying to execute - `configure' itself. - - Running `configure' takes awhile. While running, it prints some - messages telling which features it is checking for. - - 2. Type `make' to compile the package. - - 3. Optionally, type `make check' to run any self-tests that come with - the package. - - 4. Type `make install' to install the programs and any data files and - documentation. - - 5. You can remove the program binaries and object files from the - source code directory by typing `make clean'. To also remove the - files that `configure' created (so you can compile the package for - a different kind of computer), type `make distclean'. There is - also a `make maintainer-clean' target, but that is intended mainly - for the package's developers. If you use it, you may have to get - all sorts of other programs in order to regenerate files that came - with the distribution. - -Compilers and Options -===================== - - Some systems require unusual options for compilation or linking that -the `configure' script does not know about. You can give `configure' -initial values for variables by setting them in the environment. Using -a Bourne-compatible shell, you can do that on the command line like -this: - CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure - -Or on systems that have the `env' program, you can do it like this: - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure - -Compiling For Multiple Architectures -==================================== - - You can compile the package for more than one kind of computer at the -same time, by placing the object files for each architecture in their -own directory. To do this, you must use a version of `make' that -supports the `VPATH' variable, such as GNU `make'. `cd' to the -directory where you want the object files and executables to go and run -the `configure' script. `configure' automatically checks for the -source code in the directory that `configure' is in and in `..'. - - If you have to use a `make' that does not supports the `VPATH' -variable, you have to compile the package for one architecture at a time -in the source code directory. After you have installed the package for -one architecture, use `make distclean' before reconfiguring for another -architecture. - -Installation Names -================== - - By default, `make install' will install the package's files in -`/usr/local/bin', `/usr/local/man', etc. You can specify an -installation prefix other than `/usr/local' by giving `configure' the -option `--prefix=PATH'. - - You can specify separate installation prefixes for -architecture-specific files and architecture-independent files. If you -give `configure' the option `--exec-prefix=PATH', the package will use -PATH as the prefix for installing programs and libraries. -Documentation and other data files will still use the regular prefix. - - In addition, if you use an unusual directory layout you can give -options like `--bindir=PATH' to specify different values for particular -kinds of files. Run `configure --help' for a list of the directories -you can set and what kinds of files go in them. - - If the package supports it, you can cause programs to be installed -with an extra prefix or suffix on their names by giving `configure' the -option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. - -Optional Features -================= - - Some packages pay attention to `--enable-FEATURE' options to -`configure', where FEATURE indicates an optional part of the package. -They may also pay attention to `--with-PACKAGE' options, where PACKAGE -is something like `gnu-as' or `x' (for the X Window System). The -`README' should mention any `--enable-' and `--with-' options that the -package recognizes. - - For packages that use the X Window System, `configure' can usually -find the X include and library files automatically, but if it doesn't, -you can use the `configure' options `--x-includes=DIR' and -`--x-libraries=DIR' to specify their locations. - -Specifying the System Type -========================== - - There may be some features `configure' can not figure out -automatically, but needs to determine by the type of host the package -will run on. Usually `configure' can figure that out, but if it prints -a message saying it can not guess the host type, give it the -`--host=TYPE' option. TYPE can either be a short name for the system -type, such as `sun4', or a canonical name with three fields: - CPU-COMPANY-SYSTEM - -See the file `config.sub' for the possible values of each field. If -`config.sub' isn't included in this package, then this package doesn't -need to know the host type. - - If you are building compiler tools for cross-compiling, you can also -use the `--target=TYPE' option to select the type of system they will -produce code for and the `--build=TYPE' option to select the type of -system on which you are compiling the package. - -Sharing Defaults -================ - - If you want to set default values for `configure' scripts to share, -you can create a site shell script called `config.site' that gives -default values for variables like `CC', `cache_file', and `prefix'. -`configure' looks for `PREFIX/share/config.site' if it exists, then -`PREFIX/etc/config.site' if it exists. Or, you can set the -`CONFIG_SITE' environment variable to the location of the site script. -A warning: not all `configure' scripts look for a site script. - -Operation Controls -================== - - `configure' recognizes the following options to control how it -operates. - -`--cache-file=FILE' - Use and save the results of the tests in FILE instead of - `./config.cache'. Set FILE to `/dev/null' to disable caching, for - debugging `configure'. - -`--help' - Print a summary of the options to `configure', and exit. - -`--quiet' -`--silent' -`-q' - Do not print messages saying which checks are being made. - -`--srcdir=DIR' - Look for the package's source code in directory DIR. Usually - `configure' can determine that directory automatically. - -`--version' - Print the version of Autoconf used to generate the `configure' - script, and exit. - -`configure' also accepts some other, not widely useful, options. - - -Configuring Enscript to Your System -=================================== - -There are some options in enscript you might want to modify to meet -your system's needs. You can change them all after the compilation by -editing the global configuration file `enscript.cfg' at the directory -`PREFIX/etc/'. You can also change some of the during the `configure' -step by giving the configure script appropriate options. Please, -check the following things before reporting bugs; for the most cases -these help: - -* Paper size - - As a default enscript uses A4 paper. To change default paper to be - for example `Letter', edit following line in the config file: - - # Default output media. - DefaultMedia: A4 - - => DefaultMedia: Letter - - You can also select the default paper size during the configuration - by giving the configure script option --with-media=MEDIA, where - media is one of the media listed in the `lib/enscript.cfg.in' file: - A3, A4, A5, Legal, Letter, A4dj or Letterdj. - -* Default output device - - As a default (without any explicit options) enscript spools its - output to the printer. If you want to send outputs to stdout, edit - following line: - - # Where output goes as a default. - DefaultOutputMethod: printer - - => DefaultOutputMethod: stdout - -* Printer command - - Enscript's default printer command is `lpr'. To change it to be for - example `lp', edit following line: - - # Printer spooler command name. - Spooler: lpr - - => Spooler: lp - - You can also set the spooler command during the configuration by - giving the configure script option `--with-spooler=SPOOLER'. - - On SystemV machines, you might also want to change the printer queue - name switch from `-P' to `-d': - - # The spooler command switch to select the printer queue. - QueueParam: -P - - => QueueParam: -d - -* PostScript language level - - The PostScript language level that enscript uses for its output. - The default values is 2 (PostScript 2). If your printer supports - only level 1 PostScript, you can set it to default by giving the - configure script option `--with-ps-level=1'. You can also set the - level by editing the enscript.cfg file: - - # The PostScript language level that enscript should use. - PostScriptLevel: 2 - - => PostScriptLevel: 1 - - Or, you can select it at the print time with the `--ps-level=LEVEL' - option: - - $ enscript --ps-level=1 ... diff --git a/README b/README index 48605f6..d2f1c4a 100644 --- a/README +++ b/README @@ -10,7 +10,6 @@ $ ./configure --with-media=Letter - You have been warned.... ;-) // mtr@iki.fi GNU Enscript is a drop-in replacement for the enscript program. Enscript converts ASCII files to PostScript and stores generated @@ -30,7 +29,83 @@ GNU General Public License for more details. You should have received a copy of the GNU General Public License along with Enscript. If not, see . + +* Configuring Enscript for your system + +There are some options in enscript you might want to modify to meet +your system's needs. You can change them all after the compilation by +editing the global configuration file `enscript.cfg' at the directory +`PREFIX/etc/'. You can also change some of the during the `configure' +step by giving the configure script appropriate options. Please, +check the following things before reporting bugs; for the most cases +these help: + +** Paper size + + As a default enscript uses A4 paper. To change default paper to be + for example `Letter', edit following line in the config file: + + # Default output media. + DefaultMedia: A4 + + => DefaultMedia: Letter + + You can also select the default paper size during the configuration + by giving the configure script option --with-media=MEDIA, where + media is one of the media listed in the `lib/enscript.cfg.in' file: + A3, A4, A5, Legal, Letter, A4dj or Letterdj. + +** Default output device + + As a default (without any explicit options) enscript spools its + output to the printer. If you want to send outputs to stdout, edit + following line: + + # Where output goes as a default. + DefaultOutputMethod: printer + + => DefaultOutputMethod: stdout + +** Printer command + + Enscript's default printer command is `lpr'. To change it to be for + example `lp', edit following line: + + # Printer spooler command name. + Spooler: lpr + + => Spooler: lp + + You can also set the spooler command during the configuration by + giving the configure script option `--with-spooler=SPOOLER'. + + On SystemV machines, you might also want to change the printer queue + name switch from `-P' to `-d': + + # The spooler command switch to select the printer queue. + QueueParam: -P + + => QueueParam: -d + +** PostScript language level + The PostScript language level that enscript uses for its output. + The default values is 2 (PostScript 2). If your printer supports + only level 1 PostScript, you can set it to default by giving the + configure script option `--with-ps-level=1'. You can also set the + level by editing the enscript.cfg file: + + # The PostScript language level that enscript should use. + PostScriptLevel: 2 + + => PostScriptLevel: 1 + + Or, you can select it at the print time with the `--ps-level=LEVEL' + option: + + $ enscript --ps-level=1 ... + + * Supported Character Sets Enscript supports following character sets: @@ -64,7 +139,7 @@ Enscript supports following character sets: - ps PostScript font's default encoding - pslatin1 PostScript interpreter's `ISOLatin1Encoding' - + * Special Escapes Enscript supports special escapes sequences that can be used to add @@ -72,7 +147,7 @@ simple page formatting commands to ASCII documents. User can inline EPS files, change font on-the-fly insert comments and shade regions of text. See file README.ESCAPES for details. - + * Language sensitive highlighting Enscript supports language sensitive code highlighting. Highlighting @@ -81,12 +156,12 @@ files and annotates them with enscript's special escapes. The states definition file `enscript.st' is a machine independent ASCII file and it can be updated without re-compilation of the enscript program. The most recent version of this file can be downloaded from the GNU -enscript WWW home page: . +enscript WWW home page: . New highlighting definitions for different languages are welcome, -please send them directly to me: . - +please send them to: + * PostScript font support ** AFM files @@ -155,18 +230,3 @@ option `DownloadFont: name'. option `-o' lists missing characters. In GNU enscript `-o' is an alias for `-p' and missing characters are listed with an option `-O'. - -* Misc - -I am dedicated to make the GNU enscript the best a2ps converter ever, -this includes adding all the GNU features and cookies to it ;) - -Comments, suggestions, bug fixes, bug reports, etc. are welcome. - - - Markku Rossi - - - - GNU Enscript WWW home page: - -- 2.17.1