Short installation description:
-------------------------------

1. Read the license, by using this program you signal your acceptance
   of the terms as presented within.

2. Run 'linkAllFonts.sh' in the gpstill_dist directory to generate
   the base font set:

   sh linkAllFonts.sh

3. Optional: Copy more PFA or PFB Type 1 fonts to PSFonts, if you
   use the URW GNU fonts set, rename fontsub_gsfonts.table to
   fontsub.table. 

   Be sure to run

    pstill -v -I

   after you installed more fonts, otherwise they are not known
   to PStill. If you like to install TrueType fonts use a utility
   alike ttf2pt1 (http://ttf2pt1.sourceforge.net/) to convert them
   to PS Type 1. As PStill can use the job embedded fonts (also
   embedded TrueTypes) installing TTFs is often unneded.

4. Run PStill (example):

   pstill -M default -o output.pdf input.ps

   when calling from another location use either a full path

   /usr/local/pstill_dist/pstill ...

  or setup the environment variable PSTILL_PATH to the location of
  the pstill.

  For more examples and option descriptions:

  pstill -H | more

  When running multiple instances in parallel be sure to suppy the
  the option -T tmppath. Each instance needs a unique temp directory.

5. Entering the license key (commercial users need to do so):

   pstill -key "yourlicensename-abcdefg123456789!ABCDEFG"

Depending on your shell you may need to escape the '!' char by placing
a '\' in front of it.


.....................................................................


Welcome to the public release of PStill (Command line version)

(c) by Frank Siegert, 1998-2006, see COPYRIGHT file for more info

See the pstill web page http://www.pstill.com
for more information and updates.

PStill is inexpensive shareware, please do not priate this software
or further development is not possible. Private and educational use
of this Linux Version is allowed without registration and costs.

Any commercial users must aquire a license, please see

	 http://www.pstill.com

to order one online or use the enclosed registration form.

You are using this software entirely at your own risk. The author
is not responsible for any damage its use or misuse might cause.
Especially he is not responsible for the accuracy or quality of
the produced PDF files. Having said that, I hope PStill will be
helpful to you, please drop me a note if you find it useful or
encourage others to try it.

PLEASE NOTE:

You need to purchase a license for every instance of PStill you
run in a commercial environment. An instance is a running program of
PStill regardless of working environment (client or server).

Please contact frank@wizards.de for more information about licensing
options and volume licenses.


**** INSTALLATION PROCEDURE ****

1. copy the pstillXXXX.tar.gz archive to a suitable place

2. unpack it using: 

   gzcat pstillXXXX.tar.gz | tar -xvf -

   or (if gnutar is present)

   tar xzvf pstillXXXX.tar.gz

3. cd pstill_dist
  
   you should find
  
   pstill      (the converter as static binary for your platform)
   annots.sl   (the pdfmark interpreter as S-LANG script)
   init.still  (the converter initialization file)
   PSFonts     (the 'Font Pool', a directory to hold all PS fonts, now empty)
   INSTALL     (this Text)
   COPYRIGHT   (the usage conditions and registration information)
   README.*    (things you should know)
   testfile.ps (a postscript testfile)
   controls    (directory containing some N-UP scripts as example)
 
4. run 

   pstill -H | more

   and see the options and further procedures. In particular you may
   have to set the PSTILL_PATH environment and put pstill in your
   search path. PSTILL_PATH must point to the directory where pstill
   finds its helper programs and the PSFonts directory.

   If you do not set the PSTILL_PATH variable pstill assumes it is
   working inside its home directory (where init.still and PSFonts are located)

   Example (assuming pstill_dist in /usr/local):

   For csh/tcsh: setenv PSTILL_PATH /usr/local/pstill_dist

   For bash:     PSTILL_PATH="/usr/local/pstill_dist"
                 export PSTILL_PATH 

   Put this into your profile or .cshrc startup file.

5. Install the fonts (depending on your system)

   cd PSFonts
   ../linkAllFonts.sh      OR      copy your PFA or PFB fonts here
   cd ..
   ./pstill -vI

   PStill will not run without a font pool (in PSFonts), especially
   it will need the Courier font to fall back when a font is not found.
   If some fonts fails here with an error, this is intended. PStill
   is quite picky with its fonts and if they do not pass certain
   tests they won't be used for PDF generation, to spare you problems
   later.

   You can use most Type 1 (prefered) and Type 3 PostScript fonts in
   either PFA or PFB format. Type 3 will be converted to bitmaps/outlines
   in the resulting PDF thus bloating the output, keep this in mind when
   creating PS file with dvips for use with pstill!

   PStill is now installed. Now run a test:

6. Convert the supplied testfile.ps

   pstill -2 -c -c -c -g -i -p -t -o testfile.pdf testfile.ps
   
   then open it using acroread (if installed on your system, otherwise
   xpdf 0.92 or better may work too)

   acroread testfile.pdf

   (You need Acrobat Reader >= 3.x for displaying compressed (-c option) PDFs)

If this works fine, you can convert your own files. 

If you see only black dots instead of text lines you need to install
fonts and at least the font "Courier" is missing!

To add new fonts copy the font files (pfa or pfb format, no truetype)
to the PSFonts directory and run pstill -I again. Filenames are irrelevant
as PStill will extract the 'true' fontname and rename the file accordingly.

Some FAQ points:

(See also http://www.wizards.de/~frank/pstill_qa.html)

- How do I create PDF/X:

  Use options:

  -m XPDFX="Output Intent Name"
  -m XPDFXVERSION=1A   (optional, default is PDF/X-3)
  -m XICCProfile=/path/to/profile.icc

- I need more fonts:

PStill accepts Type 1 fonts, usually font file with the postfix *.pfa
or *.pfb. PStill does not need any AFM (metric) files, it generate its
own metrics. Copy fonts to PSFonts and run 'pstill -v -I' in the work
directory of PStill.

PStill can also use TrueType fonts if these are converted to Type 1 by
ttf2pt1 first. See http://ttf2pt1.sourceforge.net/

(Hint: It is a good idea to turn off 'outline optimation' and 'smooth'
 for ttf2pt1 for best compatibility and results)

If you want to map a font to another use the file 'fontmap.table'.
A tailor made fontmap.table for the URW font set can be found in the 
directory 'utils+helper'

- I want to autoreplace TeX dvips bitmap fonts:

Use option "-D" and be sure to install the TeX fonts, e.g. Computer Modern
in PSFonts as Type 1 versions. See e.g. http://www.ctan.org/tex-archive/fonts/

- I get too dark colors in the PDF output:

Use option -C to write colors as RGB. Some PDF readers show CMYK too dark
on screen.

- What about PostScript Level 2 files:

PStill defines most Level 2 commands and some PS Level 3, when your PS job 
needs to identify a Level 2 RIP use option "-2". If you get an error
be sure to test using this option, it often helps!

- What about temp space:

During its first phase (PS interpretation) PStill is writing to /tmp
and needs space to work. If no space is available it may fail during this
stage. Please provide at least 50 MByte scratch area. You may change the
default temporary directory using the '-T path' option.

ATTENTION: For every running instance of PStill you need to specify
a unique temp directory, otherwise they might interfere with undefined
results!

- What about used VM (memory):

During its second phase (PDF generation) PStill holds the complete PDF
file in memory. For large files this could be quite a substancial amount
of memory, so please provide enough swap space and memory. An upcoming
version of PStill may use temp space in the filesystem for larger 
conversions. A system should have at least 128 MByte (256 recommended).

- A note about security:

PStill includes a full interpreter with file I/O capacities, so do not
run it as root as it is able to open/read/write files if told so in the
PostScript input. Running pstill in a closed environment or check the 
PostScript files with pscheck (inquire by email for more details) before is
usually a good idea if they come from suspicious sources. PStills write
mechanism is turned off by default - you can reactivate it using option -k


PStill must be registered if used for commercial purposes.

Please provide feedback to frank@wizards.de, Thanks!

Updates are available from http://www.pstill.com


