This directory contains Metafont sources, for use by TeX typesetting program, for Pandora fonts. These fonts are: Copyright (c) 1989 by Neenie. N. Billawala but they were released for a general use. Original font files can be retrieved by ftp from, among other places, ymir.claremont.edu. A difference between this and general distribution is that here it was added NeXT specific (or rather dvips specific) Makefile which allows an easy generation of neccessary metric files and initial bitmaps needed for an installation. There is also one more sample file illustrating fonts in a context of a real text. Thanks are in order to Lones A. Smith , who suffered as an UNINTENTIONAL guinea-pig through initial iterations of this installation setup. ATTENTION! The provided Makefile goes to some length to ensure a correct operation even if you modified your various environment variables. Still it relies on a correct /usr/bin/MakeTeXPK and the one provided originally by NeXT had some problems. If you did not modify it to adjust to your local conditions you may just replace it with MakeTeXPK provided here. Otherwise ensure that MFINPUTS variable is set to contain the current working directory and that it will not clobber defaults if originally not set. One way to do that is to include the following line: MFINPUTS=`pwd`:${MFINPUTS-/usr/lib/mf/inputs}; export MFINPUTS preceding line which says 'mkdir $TEMPDIR'. See provided MakeTeXPK for a model when in doubt. It is an unfortunate fact that some Pandora files have names, like caps.mf or number.mf, are not specific enough and may possibly conflict with names of other Metafont sources. This is not the case when you have on your system only regular CM fonts and AMS collection. It may happen when you added some other extra fonts. In such situation your only recourse is to change these names and edit corresponding .mf files which rely on them. Even installing Pandora sources in their own subdirectory, which obvously should be added to MFINPUTS, will not help a lot since when making fonts Metafont may grab a wrong file anyway. You may, of course, modify your MakeTeXPK to behave smarter and use subdirectories, but if you know how to do that you do not need my instructions. :-) Steps to test and install Pandora fonts on NeXT =============================================== 1) Go to ./pandora subdirectory 2) Check in Makefile its header comment and directories which will be used for an installation (MFFILES, TFMFILES, LOCALPKS). Adjust to taste. 3) In Terminal window type make -k ; make -k print Metafont will complain about errors when generating screen fonts. Disregard! This resolution is too small. Print bitmaps will be OK. (This double 'make' is due to a misfeature/bug in NeXT make). 4) Go for a longer coffe break or lunch, since the first time around it will take a while. 5) Examine printed output and .dvi files with TeXview. 6) If you liked results become a root and type make install Exit root sheel. Fonts are already installed. 7) If you do not want to keep Pandora installed do (as root) make deinstall When doing 'make deinstall' make will remove from LOCALPKS all bitmaps with names in a pattern 'pn[brst]*pk'. It is not very likely that this will affect non-Pandora fonts, but be careful. 8) To cleanup leftovers after installation do make clobber (or 'make clean' for gentler cleaning) 9) These steps will not put LateX style pandora.sty into a directory listed in TEXINPUTS. This is left at your discretion. The style pandora.sty, when unmodified, requires Euler fonts from AMS collection and Concrete Roman for non-math numerals. 10) pandora.sty is meant to work with NFSS (New Font Selection Scheme). If you did not upgrade yet your installation to it then use instead an alternative pandora_old.sty. It is far less extensive and not as flexible but in a pinch it should do. Happy TeXing, Michal Jaegermann ntomczak@vm.cms.ualberta.ca ntomczak@vega.math.ualberta.ca