| 1 |
.TH ps2frag 1 "Feb 95" TeXware |
| 2 |
.SH NAME |
| 3 |
ps2frag - obsolete shell script for the PSfrag system. |
| 4 |
.SH IMPORTANT NOTICE |
| 5 |
The new PSfrag system no longer requires the ps2frag script; instead, it |
| 6 |
handles the processing entirely within TeX/LaTeX and DVIPS. I'm sure you |
| 7 |
will agree that never needing to run ps2frag again is a nice convenience! |
| 8 |
.P |
| 9 |
However, there are two significant differences in the way this new version |
| 10 |
of PSfrag works. Please make yourself aware of them: |
| 11 |
.P |
| 12 |
1) XDvi is no longer able to determine where your PSfrag replacements |
| 13 |
should |
| 14 |
go, so instead it lines them up in a vertical list to the left of the |
| 15 |
figure. This allows you to confirm that they have been typeset properly, at |
| 16 |
least. However, to confirm that PSfrag |
| 17 |
.B positions |
| 18 |
your replacements properly, you will have to view the PostScript |
| 19 |
version of your file with a viewer like GhostView, or print it out. |
| 20 |
This seems to be the |
| 21 |
only disadvantage to the elimination of the pre-processing step. |
| 22 |
.P |
| 23 |
2) If you embed '\\tex' commands inside your figures, you now need to |
| 24 |
explicitly _tell_ PSfrag to process these commands. To do so, use |
| 25 |
\\usepackage[scanall]{psfrag} |
| 26 |
instead of |
| 27 |
\\usepackage{psfrag} |
| 28 |
at the beginning of your LaTeX file. |
| 29 |
.P |
| 30 |
If you only use '\\tex' commands in a small number of figures, then a |
| 31 |
more efficient might be to turn on '\\tex'-scanning only for those |
| 32 |
figures. To do that, add the command '\\psfragscanon' immediately before |
| 33 |
each relevant \\includegraphics or \\epsfbox command. |
| 34 |
.P |
| 35 |
.SH NOTES |
| 36 |
See the PSfrag documentation for further information. |
| 37 |
.SH "SEE ALSO" |
| 38 |
dvips(1), gs(1), ghostview(1), latex(1) |
| 39 |
.SH AUTHORS |
| 40 |
.IP [email protected] |
| 41 |
The PSfrag maintainer's mailing list. |