| 1 |
This is the 00readme.txt file to accompany PSfrag, a system for LaTeX to |
| 2 |
integrate LaTeX equations with Encapsulated PostScript figures. |
| 3 |
|
| 4 |
These files compose the April 11, 1998 release of PSfrag 3.04. This is a |
| 5 |
maintenance release, and fixes some bugs and shortcomings in version 3.03. If |
| 6 |
you decide to install this release, you should not need to re-compile any of |
| 7 |
your files, unless you happened to encounter one of the bugs in an earlier |
| 8 |
version. |
| 9 |
|
| 10 |
+-------------------------------+ |
| 11 |
|QUICK INSTALLATION INSTRUCTIONS| |
| 12 |
+-------------------------------+ |
| 13 |
|
| 14 |
1. Run LaTeX on psfrag.ins, generating the package file psfrag.sty and |
| 15 |
the PostScript header file psfrag.pro. |
| 16 |
2. Place psfrag.sty anywhere in your TeX search path; for kpathsea-based |
| 17 |
systems such as teTeX, this is determined by the TEXINPUTS variable. |
| 18 |
3. Place psfrag.pro where your DVI-to-PostScript driver (e.g., dvips) |
| 19 |
can find it. For kpathsea-based systems such as teTeX, this is |
| 20 |
determined by the DVIPSHEADERS variable. For dvips in particular, |
| 21 |
this includes the directory containing tex.pro and special.pro. |
| 22 |
|
| 23 |
More complete instructions are found in pfgguide.{tex,ps}. The files |
| 24 |
example.eps and testfig.eps are needed to typeset the documentation, so |
| 25 |
do not delete them if you want to re-generate pfgguide.ps. In fact, a |
| 26 |
good test to see if your TeX/LaTeX/PSfrag installation is working |
| 27 |
properly is to rename pfgguide.ps, generate a new pfgguide.ps from the |
| 28 |
.tex file, and compare the two files. |
| 29 |
|
| 30 |
+------------------------------------+ |
| 31 |
|IMPORTANT NOTES FOR PSFRAG 2.X USERS| |
| 32 |
+------------------------------------+ |
| 33 |
|
| 34 |
Note that PSfrag 3.x is quite a bit different from previous versions. |
| 35 |
The interface has been preserved, but the most notable difference is |
| 36 |
the absence of the preprocessing script ps2frag. That's right: _you |
| 37 |
will no longer need to run the ps2frag script_. This is a relief, of |
| 38 |
course, to users who could never get Perl working on their OS. |
| 39 |
|
| 40 |
However, PLEASE HEED the following differences between PSfrag 2.x and |
| 41 |
PSfrag 3.x! You will be soundly flogged with wet noodles if you ask |
| 42 |
about these and you haven't read this warning or the ones in pfgguide: |
| 43 |
1) PSfrag replacements no longer show up in their proper positions when |
| 44 |
viewing the file with Xdvi. Instead, they show up in a vertical list |
| 45 |
along the left side of the figure. So, you can check if they are |
| 46 |
typeset properly in Xdvi, but you can't make sure they are properly |
| 47 |
placed. To do that, you should use a PostScript previewer like |
| 48 |
GhostView and GhostScript. This is an unforunate but necessary |
| 49 |
consequence of the elimination of the preprocessing step. |
| 50 |
2) If you use the \tex command, note that it has been _deprecated_. |
| 51 |
Now, you have to explicitly turn it on, either for the entire |
| 52 |
LaTeX document or for each file individually. pfgguide.{tex,ps} |
| 53 |
describe how to do this in detail. The reasons for this once |
| 54 |
again turn to the elimination of the preprocessing step. |
| 55 |
I think that the elimination of the ps2frag script far outweighs |
| 56 |
either of these two (possible) disadvantages. |
| 57 |
|
| 58 |
+---------------+ |
| 59 |
| RELEASE NOTES | |
| 60 |
+---------------+ |
| 61 |
|
| 62 |
This is a bug-fix release, which fixes the following bugs encountered |
| 63 |
in PSfrag 3.03: |
| 64 |
|
| 65 |
1. Attempting to use EPS figures as PSfrag replacements would cause |
| 66 |
an infinite loop. This should work properly now. |
| 67 |
2. Since the last release, the DVI-to-PS driver DVIPSone changed in |
| 68 |
a way that made PSfrag replacements appear upside down. |
| 69 |
3. Small improvements to the psfrag.pro file have been made, which |
| 70 |
will hopefully allow you to make EPS files out of PSfrag-ged |
| 71 |
figures. I can't make any guarantees about this yet. |
| 72 |
4. The manual has been improved slightly; the known issues for |
| 73 |
XFig and Seminar are now discussed. In addition, a more complete |
| 74 |
discussion about ``valid'' tags is included. |
| 75 |
|
| 76 |
Bug reports and suggestions should go to [email protected], |
| 77 |
the PSfrag maintainer's email-list. However, before submitting a bug |
| 78 |
report, please make sure that it is not already covered in the "Known |
| 79 |
issues" section of pfgguide.tex! |
| 80 |
|
| 81 |
Michael C. Grant |
| 82 |
|