This is a description of the group of Psizzl support files which comprise
the distribution package for Psizzl, and instructions for their use.
Psizzl is a macropackage for TeX. It is compatible with the distributed version
of TeX, and uses no special fonts.
 
The version of Psizzl currently running at SLACVM, the distribution point,
is 0.40. SLAC currently has no FTP ability, a la ARPA, but I will send this
group of files to requestors. Send mail to OGAWA@SLACVM.bitnet
 
Included in this group is a file called PSIZZL FILELIST. This contains
a list of all the files in the group. They are of several types:
 
* PSIZZL - these are the macros themselves. The file PSIZZL TEX will \input
  them.
 
* PSIZSAMP - these are sample files for various Psizzl functionalities and
  are meant to be run under the Psizzl macropackage.
 
* PSIZDOC  _ these comprise the documentation of Psizzl. You can generate
  SLAC-265 ``Psizzl - a macro package for TeX'' by Texing PSIZZL PSIZDOC.
 
* EXEC     - these are VM/CMS executive files which perform certain funtions.
 
* HELPCMS  - these are VM/CMS help files for the corresponding EXEC.
 
miscellaneous files - most of these are used in the production of the
  Psizzl manual.
 
Since I don't know about your system, your TeX, etc. I couldn't anticipate
your particular needs; these notes may be of assistance:
 
1. Psizzl makes use of a SLAC supported mod to TeX that passes commands to
   the CMS operating system via a \write16. Psizzl supports this by making
   \newwrite stop at 15, so that the user won't inadvertently create a
   \newwrite to CMS, and supports a \CMS{stuff} command that sends ``stuff''
   to CMS. You may have a similar hook in your TeX, or you may want to delete
   the \CMS and \newwrite definitions.
 
2. Psizzl supports merging of graphics into your text, via commands which
   create white space and gives a \special command at the lower left corner
   or upper left corner, as the case may be. See \insertUGS and \insertGREY.
   These give a \special{mergeUG(filename.filetype)} and \special{insert(
   filename.filetype)} respectively. If the syntax of your device driver is
   different, you should alter the \def of these commands appropriately.
 
3. Graphics at SLAC are produced via the highly portable Unified Graphics
   System, or by TOPDRAW, a UGS interface. Contact SLAC to port these
   programs to your site.
 
4. SLAC's printers are all Imagens, so the merged files used in the manual
   are generated for Imagen (IMPRESSF format). Your system will likely be
   different. When you attempt to typeset the manual, your device driver
   will then likely choke on the IMPRESSF files. You will want to provide
   your own graphics after the examples shown in the manual.
 
5. Building PSIZZL FMT, the preformatted version of Psizzl, is really easy.
   Just make sure you have a DUMMY version of MYPSIZZL TEX in place and then
   simply INITEX PSIZZL. TeX will run, inputting PLAIN TEX, and then it
   will \input all the source files for Psizzl. Then it will \dump.
   PSIZZL TEX is sensitive to its environment, and when run under INITEX,
   it will \dump automatically.
 
   In a similar vein, if you TEX PSIZZL, and if Psizzl is already the
   preloaded FMT for TeX, Psizzl TeX will sense this and not attempt to
   \input all the source files again. You will get an informative message.
 
   Or, if you TEX MYFILE and MYFILE has a command \input psizzl, and if
   Psizzl is already the FMT for TeX, you will again receive an informative
   message, and PSIZZL TEX will not attempt to \input the source files
   for Psizzl. Therefore, putting the command \input psizzl into your source
   file will never cause harm. I recommended that you use Psizzl on top
   of PLAIN TEX only.
 
6. At SLAC, we have a way for the user to specify the desired format (FMT)
   in the source file: a TeX comment of the form:
 
   % macropackage=name
 
   where name is PLAIN, PSIZZL, LATEX, AMSTEX, etc. The CMS EXEC for this,
   TEX EXEC, is available from SPRAGENS at SLACVM.bitnet
 
7. After Psizzl is in effect, the \catcode of › (the superscript character)
   is no longer 7, but 13, as it is an active character. Ordinary math
   typesetting will work fine, but if you want to use expressions like
   ››M for <carriage return>, etc. you must temporarily set the \catcode
   of › back to 7 while you use such expressions.
 
   This all was done to support the building of an index, like in the TeXbook.
   As an implementor of Psizzl, you can disable this index support by
   setting the catcode of › to 7 and leaving it there. The choice is yours.
 
   I mention this because most users don't care either way, rare ones want
   an index, and other rare ones want to diddle the catcodes of control
   characters....
 
8. By the way, SLAC uses an unusual convention for the EBCDIC code for
   three characters:
 
   tie          (^),
   superscript  (›),
   vertical bar (|)
 
   I have converted all occurrences of these characters to those required
   for the TeX distribution tape, but if I have missed any, please tell me.
 
9. In Psizzl, all site-dependent code will be found in the file INSTITUT E
   PSIZZL. You will want to edit this file so that the default aspects of
   the macropackage, like the letterhead, for instance, are appropriate to
   your institution.
 
If you encounter any problems bringing up or using Psizzl or printing the
manual, please contact me: OGAWA at SLACVM.bitnet
 
Notice this material is all public domain and may be freely used, distributed,
modified, enhanced, etc. The author requests, however, that any such use
be attributed back to ``Psizzl by Arthur Ogawa, SLAC, Stanford University''.
Furthermore, all the usual disclaimers apply. I support Psizzl, so if you
find a bug, please tell me. Also, I am always eager to learn more, so if
you think up a neat enhancement for Psizzl, contact me for possible inclusion
in later releases.