From smosna@smosna.cs.nyu.edu Wed Jun 21 16:45:02 1995
Received: from cs.NYU.EDU by SHASHA.CS.NYU.EDU (4.1/1.34)
	id AA25560; Wed, 21 Jun 95 16:45:02 EDT
Received: from SMOSNA.CS.NYU.EDU by cs.NYU.EDU (4.1/1.34)
	id AA26855; Wed, 21 Jun 95 16:42:34 EDT
Received: by SMOSNA.CS.NYU.EDU (4.1/1.34)
	id AA25385; Wed, 21 Jun 95 16:42:30 EDT
From: smosna@smosna.cs.nyu.edu (Matthew Smosna)
Message-Id: <9506212042.AA25385@SMOSNA.CS.NYU.EDU>
Subject: summary of new Tex/Latex changes...
To: dept@cs.NYU.EDU
Date: Wed, 21 Jun 95 16:42:30 EDT
X-Mailer: ELM [version 2.3 PL2]
Status: R

Dear Sun Users at CIMS,

This email briefly summarizes some of the changes that Tex/Latex users
should be aware of when using the newly installed Tex/Latex system.
None of the information given below is new--I have already disseminated
this information via email in response to individual questions and
mail to everybody@cims. If you are happily using the new Tex/Latex
system, you need not read further.

(1) Psfig is now a style file, not a tex file. To use psfig you "activate"
    psfig as follows:

	\documentstyle[psfig]{...}

(2) If you do *not* have your own personal Tex/Latex macros, you should 
    be sure that the TEXINPUTS environment variable is not set in 
    the shell startup files.

    If, on the other hand, you *do* have your own Tex/Latex macros,
    then you need to set the TEXINPUTS environment variable as follows.
    Set the environment variable TEXINPUTS to a colon-separated list
    of directories ending in a single colon. For example, let's say that
    you have place your macros in ~/tex/macros. If you
    are using the Csh, put the following line into .cshrc (for other
    shells, do the equivalent):

	setenv TEXINPUTS ~/tex/macros:

    Note the final colon. By placing the colon at the end you are
    syntactically specifying that the Tex system should look in 
    the "usual places" (that is, the standard subdirectories) for 
    all other macros.

(3) If you need to revert to the old Tex system (which is available
    on BARNEY) and preview the results, here's a summary of what to do:

    (a) On your workstation, Open up a window and log into BARNEY.
    (b) Tex/Latex your document by editing it and running latex/etc on BARNEY.
        This will create a DVI file for your document.
    (c) Open up a new window on your workstation and run xdvi locally.
        By "run xdvi locally" I mean that you can run the latest xdvi
        (the one in /usr/local/bin) to preview your document even though
        you created the DVI file on BARNEY using the old tex/latex.

(4) Remember that old files such as *.dvi, *.log, *.toc, *.aux,
    for example, may not be compatible between versions. For example,
    if you have a Latex/Tex document created using the old version 
    and attempt to print it out using the new version, there may be
    problems. The solution: Delete your old *.dvi, *.log, *.toc, *.aux
    files and rebuild those files from scratch.

(5) The program "makeindex" was not installed by default in the new
    installation. However, we have now installed makeindex in /usr/local/bin
    as of Tuesday, June 20th.

(6) Remember that when you run dvips, it is possible that some fonts
    will have to be built. In the old Tex/Latex installation all fonts
    were prebuilt, but this required that an enormous amount of space 
    (about 50 Megabytes of fonts) many of which you not used. After
    some period of time, we expect the list of fonts that are located in
    /usr/local/lib/texmf/fonts/tmp/pk/cx to reach a "steady state" so
    that all of the most frequently used fonts are available pre-built,
    and only an occassional font or two has to be built on-the-fly.
   
Matthew 

