The full psfig should be available wherever you got dvips. It is also on labrea.stanford.edu. I recommend you get it; it's well worth the download time. ~~~~~~~~~~~~~~~~~original README file~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ psfig/tex -- TeX macros for the inclusion of postscript figures All software, documentation, and related files in this distribution of psfig/tex are Copyright (c) 1987,1990,1991 Trevor J. Darrell Permission is granted for use and non-profit distribution of psfig/tex providing that this notice be clearly maintained, but the right to distribute any portion of psfig/tex for profit or as part of any commercial product is specifically reserved for the author. Thanks to J. Daniel Smith for his contributions to verisons 1.4-1.6, and to Ned Batchelder and Greg Hager for their contributions to the original work. ================================================================== ================================================================== NEW IN VERSION 1.9 Version 1.9 fixes allows magfication and works with amstex. New features in version 1.8 include better rotation ability (\psfig{...,rotate=100}) and support for including compressed figures (use the included "pscompress" script). ================================================================== ================================================================== REQUIREMENTS Psfig/tex uses \special calls to manipulate the PostScript environment within a document and include figure files. To use psfig you must therefore be using a postscript device for your output. This version psfig/tex works with the "dvips" PostScript driver, which is available from labrea.stanford.edu. It should also work with the "dvips" driver sold by ArborText. Unsupported versions of psfig exist for the version of "dvi2ps" written by Tony Li and for OzTeX (see the unsupported directory). ================================================================== ================================================================== INSTALLATION To install psfig, simply copy the psfig.tex and psfig.sty (a symbolic link to psfig.tex) files into a directory on your TeX include path (e.g. /usr/lib/tex/macros). ** To use the compressed figure option, you need to patch dvips to allow for "zcat" arguments to plotfile specials. To do this copy dospecial.patch into your dvips directory and run "patch < dospecial.patch", and then recompile. "dospcial.frag" contains the modified portion of the code as it should appear in the patched file. ** ** To use magnification with psfig, you need to change the line /magscale false def in special.pro to /magscale true def This should be fixed in future versions of dvips. ** If you plan to use Macintosh figures, you'll proably want to use cleanfig (see below.) Cleanfig should be installed into /usr/local/bin or its equivalent. Cleanfig is just a one-line shell script that runs tr, sed and stripfonts.awk; you will have to edit cleanfig to refer to where you put stipfonts.awk. A copy of the users guide can be printed by running latex and dvips on psfig-doc.tex. ===================================================================== ===================================================================== Tips on including Macintosh figures: 1) How to capture a figure and the LaserPrep prolog into a disk file: Many different methods exist to appempt to do this, some of which As of this writing, it is possible to convince MacDraw to place a Postscript description of a figure in a file rather than sending it directly to a LaserWriter by hitting clover-F immediately after clicking `OK' on the print dialog box. The file is always called `PostScript' and is left in the folder MacDraw was started in. Use a communications program to move the file over to the host on which TeX is running. MacDraw creates a output file in the form of `QuickDraw' calls, which are interpreted as a set of PostScript procedures. These procedures are defined in what we call the Macintosh LaserPrep prolog, which must be downloaded before Macintosh figures are sent to the printer. By using clover-K rather than clover-F in the key sequence above both the prolog and figure will be captured in the PostScript file. The prolog can be extracted by hand-editing out the portion of the clover-K file also present in the clover-F file. You need to always make sure that you keep a version of the prolog that was resident in the Mac when the figures was generated, since the prolog is usually not backward compatible. E.g. figures which rely on laseprep version 68 will not print using laserprep verion 70. (Thanks Apple!) 2) Make the postscript suitible for including as an encapsulated postscript figure. Unfortunately, the postscript produced by most versions of the LaserWriter driver is not well suited to be included directly as a psfig figure. Most versions of the LaserPrep do not include an accurate bounding box comment in the PostScript files they produce; figures created by these systems will have to have their bounding box added by hand. "graphpaper.ps" is often useful for determining the bounding box of a figure. The "cleanfig" shell script adds a default bounding box, removes nasty "%%EOF" lines, converts CF-LF (useful for files that have been moved across appletalk), and strips away downloaded fonts. NOTE: fonts are stripped by the cleanfig program because I found that my documents were crashing on figures that were downloading fonts that were already printer-resident. Cleanfig will remove all fonts, so if you are using non-resident fonts in your figures you will have to modify cleanfig to not stip out the downloading of those fonts. 3) Make sure the Laserprep prolog is loaded in the printer before printing your document. Other Macintoshes will often automatically download the Laserprep code into the printer whenever access the printer and find it does not have the code already downloaded. The laserprep prolog can be manually sent down by either by prepending it using /bin/cat: cat lprep70.pro doc.ps | lpr or with the dvips special header command at the top of your latex file: \special{header=lprep70.procs} The only difference between the ".pro" and ".procs" version is what structuring comments are included. The ".procs" version works well as the argument to a \special{header=..} within dvips (e.g. it will preview correctly under NeWS). 4) Good luck! (you may need it.) "macdemo.tex" containts a test document that including four version 68 mac figures; "macdemo.tjd.ps" has what I get after running latex and dvips. ======================================================================