PSint INSTALL file (07/02/90)
                    Fabien LELAQUAIS (1990)
                    lelaquaf@apo.esiee.fr
                    `Forgive my poor english'
------------------------------------------------------------------------

  PSint has been written so that it can be run on any Unix-like
system, and some modifications has been done so that it can run on a
Vax-VMS system.

1 - COMPILATION
----------------

  On a Unix system, just a make will do.
  Under VMS, look at the compile.com file for details.

  You should not have any problems to bring up a running version on
your system, since the program is not too big, and the running version
won't consume your memory too fast. I haven't heard any installation
problems yet (it true it hasn't been installed that often...).

  The only file you'll have to check is the ``machine.h'' file you
have in the ``Sources'' subdirectory. The original file is made to be
correct on an APOLLO system (rev 10.0 or later).

  It defines a few very-general flags that make the compiler behave
correctly, depending where you will install your code.

  All those `define's should be set to `0', except the ones that match
your machine.

  Don't worry about the SECMAI flag... It has been created for a
specific application in a French company...

2 - CONFIGURATION
------------------

  At launch time, PSint loads a profile file that creates new
commands, and how some system-specific tasks can be done.

  Look at the `Doc/running_PSint' file to know what should be in that
file, and where it is.

  To tell PSint where it can find fonts, you will have to modify the
very first lines of that profile :

   /FontFiles (/your/font/directory/) def

  Depending on what kind of fonts you're up to load, you will have to
change the definition of the initial font in the FontDirectory
dictionnary, filled in that file to be able to run procedures that
actually do the loading process.
