[ This texmf/macros/latex/distribs/latex/fonts/README
  for users of the Unix TeX distribution.
  
  May 1994 ]

Owing to the persistent risk of creating dialect versions of
Donald Knuth's Metafont character descriptions, 
duplicates and slightly modified duplicates of these source files 
have been removed from this directory.  Only the absolute minimum number 
of new files is provided in our distribution.

The Makefile will create temporary copies of required Metafont sources 
and modify them as needed.  To find out whether you need to keep any of 
these temporary .mf files, see lines 000-000 below.

If you are updating, and if the LaTeX on your system was installed
before 25 March 1992:

	"Please note that most of the Metafont source files have been changed
	slightly.  It is recommended that you rebuild the font set with 
	Metafont."  -- Leslie Lamport, "latex.ins"

	"The Metafont source files have also been updated. This does not mean
	that the shape of the characters were changed, only a few internals
	like the font identifier for the invisible fonts, and the addition of
	a check so that the line and circle fonts can no longer be run with
	cmbase.
	   It should be noted explicitly that ALL files have to be updated:
	otherwise it will not work."  -- Frank Mittelbach & Rainer Sch\"opf,
	"RELEASE.NOTES"
			

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *



LaTeX fonts are now delivered only in mf source files.  

To generate a basic set of fonts -- fonts at magnifications called for 
by lplain.tex and splain.tex, whose font definitions are taken from 
lfonts.tex and sfonts.tex -- use the Makefile provided in this directory.  

If you are installing the xdvi previewer and the dvips PostScript printer 
driver, both programs come with a MakeTeXPK script which automates the 
generation of bitmapped (pk) fonts.  This means that if you know that 
you will, for certain, not be using the slitex invisible fonts, you do 
not need to generate a set of bitmapped fonts at this time, using the 
Makefile we provide in this directory.  Any run during which dvips or 
xdvi must generate a pk font that is not yet in your permanent pk font 
library, will be a little slow (because it is invoking Metafont and 
GFtoPK, and placing the new font on the program's search path); but once 
you have built a good collection, the programs will run much more speedily.

If, however, you will be using SliTeX, we recommend running this Makefile
to generate a basic set of bitmapped fonts.  At the same time, the mf
sources for the slitex fonts will be generated from the current latex
mf sources.  We do this to guard against the proliferation of dialect 
versions of these source files.

			* * * * * * * * * *


How to use the Makefile to generate fonts: 


(1) Copy the Makefile to the directory in which you want the fonts to be 
    generated.  We recommend making a temporary directory for this purpose.

    If your device driver is capable of using pk fonts, copy the 
    LaTeX.gfconvert script to the same directory.

	(The dvips PostScript driver and the xdvi previewer both use
	pk fonts.)


(2) Edit the Makefile:

	-- Check the setting of the  DPI=  line (line 107).  

	   It should be set to the resolution of the device for which 
	   you are generating rastered fonts.  (For example, if you are 
	   generating fonts for the AppleLaserWriter, a 300dpi device, 
	   you will want to be sure that DPI is set to 300; if you are 
	   generating fonts for the dvisun previewer, you will want to 
	   be sure that DPI is set to 120; etc.)

	   If it is not set to 300 (or whatever you need), 
	   exit the Makefile, and type the following command
	   at your prompt (%):

		% make magsteps "DPI=nnn"

	   where nnn is replaced by you with the appropriate value.
	   This will recalculate the settings for  DPI=  *within* the 
	   Makefile.  (Note that this feature enables you to use 
	   this Makefile any number of times to generate a basic set 
	   of LaTeXfonts for any number of devices, that is to say 
	   at whatever resolution you wish.)

	-- Check to see that the settings for TEXHOME, etc. (in lines 
	   69-79) reflect what is the case at your site.  

		"TEXBIN" defines the location of your tex, mf, etc. binaries.

		"LINK" is the command that creates symbolic links
			on your machine.  If your machine is not 
			able to do this, the copy command (cp) will do.

		"MAGSTEP": keep this at 0.0; do not change it.

		"MF": unless you are confident about what you are doing,
			keep this defined as "mf"; do not change it.
			It is easy to invoke local variants of Metafont
			at run-time, from the command line (see lines 
			82 and following, in the Makefile).

		"MODE" names the mode_def appropriate for the device 
			for which you are generating these fonts.
			The default is "localfont" -- defined by you 
			in your modes.mf file during the installation 
			of the Metafont program; modes.mf resides in 
			your MFINPUTS directory.  

				Go to your MFINPUTS directory;
				grep 'localfont := ' modes.mf.

			If the mode_def defined there is the one for which 
			you are generating these fonts

				i.e., if it is CanonCX, and you are 
			   	generating these fonts for an Apple 
			   	LaserWriter or some other printer that uses 
			   	the CanonCX 300dpi write-black print engine; 
			   	or, if the mode_def defined there is 
			   	RicohFourZeroEightZero, and you are 
			   	generating these fonts for a printer that uses 
			   	a 300dpi write-white print engine, etc.,

			go to Step 4.

			If the mode_def given there is for a device 
			that is *not* the one for which you are generating 
			these fonts, then follow the instructions in the 
			Makefile, lines 82-103.  You will see that it is
			easy to substitute another mode_def on the command 
			line at the time you run the make.  

		"MFBASE" is the location of your Metafont base files.

		"CMINPUTS" is the location of your Metafont source (*.mf) files.
			Please note that this Makefile assumes that 
			all of the source files for the Computer Modern,
			LaTeX/SliTeX, and logo fonts are in a single
			flat directory.  If you have them organized
			in subdirectories, create symbolic links from
			the various subdirectories to the MFINPUTS
			directory before you run the make.

(3) Type 

	% make all	[ ... defining MODE at this time, if necessary]

    followed by 

	% make logo	[ ... defining MODE at this time, if necessary]

    The Makefile will invoke mf (Metafont) in batch mode, and produce 
    a set of fonts in gf format.


(4) If your previewer or printer driver is able to use fonts in pk format, 
    convert the gf output of Metafont to pk format by running the 
    LaTeX.gfconvert script (type its name at the prompt).  (This script
    invokes the gftopk conversion utility, which should have been made and 
    installed by default during the primary installation of TeX and Metafont.)


(5) We recommend testing at least some of the fonts just generated 
    by getting a previewer or printer driver to use them for previewing
    or printing.

	If you already have a previewer or printer driver installed,
	direct it to search your temporary directory for these fonts.
	(If you have no LaTeX source files of your own to test, try 
	running sample.tex, testpage.tex, or tryfonts.tex through 
	LaTeX, and preview or print the *.dvi output.)  

	If you do not yet have a previewer or printer driver installed,
	you may, at this point, wish to go to the DVIware directory 
	(parallel to TeX3.141), and make one or another of the programs.

		During the installation, you will have to define 
		the permanent "home" directory of these fonts (i.e., 
		the directory to which you will move these fonts
		after you have tested them).  

		Since they are still in a temporary directory, 
		you can -- for the purpose of testing the fonts -- 
		either link the fonts from their temporary directory 
		to their permanent "home" directory, or -- if the program 
		allows it -- set an environment variable or give an option 
		on the command line so that the temporary directory will be 
		searched for these fonts during the test.  The man page for 
		the previewer or printer driver program will tell you what 
		the environment variable or the option is.

    If the results are satisfactory, copy or move the *.*pk fonts 
    to their permanent directory.

    If you are, or will be, using the dvips PostScript driver from this 
    distribution:

	Do an ls *.mf in the directory in which the Makefile was run
	and where the fonts were generated.

	You will see that, in addition to files symbolically linked 
	from your MFINPUTS directory, there are twelve *.mf files that
	were generated by the Makefile from the linked source.  For sites 
	where it was necessary to substitute "cp" for "ln -s", the 
	Makefile-generated special parameter files for SliTeX are:

				icmcsc10.mf
				icmex10.mf
				icmmi8.mf
				icmsy8.mf
				icmtt8.mf
				ilasy8.mf
				ilcmss8.mf
				ilcmssb8.mf
				ilcmssi8.mf
				lcmss8.mf
				lcmssb8.mf
				lcmssi8.mf

	Place these files on your MFINPUTS path.  This is to say, place them 
	where the dvips driver -- using the MFINPUTS search path definition --
	will be able to find them, so that it will be able to generate more 
	rastered fonts via its MakeTeXPK script, at magsteps other than those
	just generated by the run of this Makefile.  

    If you do not need to generate another set of LaTeX/SliTeX fonts 
    (for another device at another resolution) you may now remove your 
    temporary directory and its files.  If you have installed the pk font
    files, you do not need the gf font files.  Nor do you need the tfm
    font files; a set of them from the distribution were copied over by you
    to your TEXINPUTS directory to enable you to dump formats.


    If another set of LaTeXfonts for another resolution is needed, 

	% rm *.*gf *.*pk

    This will remove all of the gf and pk fonts generated at whatever 
    resolution you set at the beginning of the process (Step 3 above).
    Set the Makefile to whatever resolution is necessary, and repeat 
    the steps above.


			* * * * * * * * * *


Together with the set of pk fonts in cmfonts, the LaTeXfonts you have 
generated should be sufficient for using LaTeX or SliTeX at the basic 
document size.

    No provision is made for 11pt or 12pt sizes.  If you need them,
    see the comments in the Makefile for a simple way to make all 
    necessary fonts at the higher magsteps needed for LaTeX 11pt and 
    12pt styles.

If any LaTeX source file calls for one of these fonts at a magnification 
not defined in lfonts or sfonts, your previewer or printer driver will 
complain that it cannot find that particular font.  If the previewer or 
printer driver is not able to make a substitution, or if a substitution 
is not acceptable to you, you will have to generate the font at that 
particular magnification.  The mf man page is your guide.  

	The exception is Tomas Rokicki's PostScript driver dvips 
	(in DVIware/laser-setters/dvi-to-ps/dvips547).  The MakeTeXPK
	script that accompanies the driver will automatically invoke 
	Metafont and gftopk to generate rastered fonts in gf format
	and convert them to pk format, if the driver does not find 
	a particular font in any of the font directories on its search 
	path.



			* * * * * * * * * *


System V NOTE:
=============

The filenames lcircle10.???xx and lcirclew10.???xx (where ??? = the resolution 
in dots-per-inch, and xx = pk or gf) extend beyond the 14-character limits of 
filenames on many systems.  

For the time being, if it is necessary for you to do so, we recommend re-naming 

	lcircle10	to 	lcirc10
and
	lcirclew10	to	lcircw10.

In time, these may become the standard names; but they are not yet so.

You will have to edit the appropriate lines in lfonts.tex (lines 467 and 468 
in the current version) and in sfonts.tex (lines 232, 233).  You do not have 
to refer to these fonts explicitly when you are running LaTeX.


			* * * * *  E O F  * * * * *

