These are the BlueSky Research postscript CM fonts, placed in the
public domain as described in the READ.ME file.  If you don't use TeX,
then you probably don't need these.

No alterations have been made to the fonts, they have just been
repackaged as NeXT font directories for convenient installation and
use under NextStep or OpenStep.  No warranty is expressed or implied -
they work for me, but your mileage may vary.

INSTALLATION
============
To install, unpack the tar file (assuming it is in the current
directory) using the following command in a terminal window:

   gnutar xzf BlueSkyFonts.tar.gz

This will produce a subdirectory containing the following:

  File/Directory			  Explanation
--------------------------------	-----------------------------------
BlueSkyFonts/BlueSkyFonts.README	Installation directions for NeXTs
BlueSkyFonts/BlueSky.pkg		NextStep/OpenStep installer package
BlueSkyFonts/READ.ME			BlueSky/AMS announcement
BlueSkyFonts/cmsample.tex		To test installation
BlueSkyFonts/test.rtf			Another installation test

As root, install the BlueSky.pkg by double clicking on it in the
Workspace and clicking the "Install" button.  In addition to
installing the fonts to /LocalLibrary/Fonts, the package runs a script
which updates the font index files and updates your dvips
configuration to recognize the new fonts.  If there are any problems,
a copy of your original "config.ps" file will be saved as
"config.ps.backup".  [NOTE - If you decide to uninstall, the backup
file will be reverted back as config.ps.  If config.ps.backup does not
exist, config.ps is left alone.  Therefore, if you have made any
custom changes to config.ps after installing the BlueSky fonts, remove
the backup file manually BEFORE uninstalling and clean up config.ps
yourself.]

If you were already using another set of postscript Computer Modern
fonts, such as Bakoma, you'll need to edit config.ps by hand to
comment out or remove the old mapfile.

If TeXview is currently running, please exit now so it will make use
of the new fonts and configuration for the following tests. 

If all went well, you should be able to open test.rtf in Edit.app (as
a normal user), select the line of input (cmd-a from the keyboard or
click-drag the mouse across the entire line), and then select
"Services>TeXview>TeX EQ->.EPS" from the menu.  When it has run to
completion, the .rtf file will have transformed itself to an .rtfd
file and the graphic image it contains should be recognizable as the
quadratic formula.  If it looks jagged and/or has missing characters,
symbols, or lines, then there's a problem with the installation.
Note that the magnification was set to 1800, which is definitely not
a "standard" TeX size - one of the benefits of using PS fonts is the
ability to scale arbitrarily, not just to pre-defined sizes.

As a further test you should be able to tex and preview the file
"cmsample.tex" [Warning - this loads every single font in the CM
distribution, and may blow out printer memory if you actually try
to print all 10 pages.  This does not mean that the installation
failed, only that you should consider increasing memory on your
printer if you're going to routinely print using lots of
non-resident fonts.  If you would like a printer test, and are
encountering this problem, try printing a few pages at a time.]

When you are satisfied that all is well, you can probably remove the
bitmap fonts from the original distribution to save disk space.
HOWEVER, YOU DO SO ENTIRELY AT YOUR OWN RISK.  I mv'ed the pk
directory to pk.backup for a month to make sure nothing was broken
before actually removing them from my system.  I'd suggest that you
do something similar to guard against possible problems.

--Paul Sanchez
Parks College of St. Louis University
paul@spectrum.slu.edu