summaryrefslogtreecommitdiff
path: root/Build/source/texk/texlive/tl_support/ps2frag.1
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2020-01-31 18:59:27 +0000
committerKarl Berry <karl@freefriends.org>2020-01-31 18:59:27 +0000
commit3bd232dd726daf258464933f206bc339d9120df5 (patch)
tree7016b218d20a57aac11a11f45f16d4a66d1fac16 /Build/source/texk/texlive/tl_support/ps2frag.1
parent9a1ad7e9152cd1028cc01bd7430c10b17c5ead9c (diff)
rename tl_scripts dir to Build/source/texk/texlive/tl_support
git-svn-id: svn://tug.org/texlive/trunk@53614 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Build/source/texk/texlive/tl_support/ps2frag.1')
-rw-r--r--Build/source/texk/texlive/tl_support/ps2frag.141
1 files changed, 41 insertions, 0 deletions
diff --git a/Build/source/texk/texlive/tl_support/ps2frag.1 b/Build/source/texk/texlive/tl_support/ps2frag.1
new file mode 100644
index 00000000000..b572c5733c1
--- /dev/null
+++ b/Build/source/texk/texlive/tl_support/ps2frag.1
@@ -0,0 +1,41 @@
+.TH ps2frag 1 "Feb 95" TeXware
+.SH NAME
+ps2frag - obsolete shell script for the PSfrag system.
+.SH IMPORTANT NOTICE
+The new PSfrag system no longer requires the ps2frag script; instead, it
+handles the processing entirely within TeX/LaTeX and DVIPS. I'm sure you
+will agree that never needing to run ps2frag again is a nice convenience!
+.P
+However, there are two significant differences in the way this new version
+of PSfrag works. Please make yourself aware of them:
+.P
+1) XDvi is no longer able to determine where your PSfrag replacements
+should
+go, so instead it lines them up in a vertical list to the left of the
+figure. This allows you to confirm that they have been typeset properly, at
+least. However, to confirm that PSfrag
+.B positions
+your replacements properly, you will have to view the PostScript
+version of your file with a viewer like GhostView, or print it out.
+This seems to be the
+only disadvantage to the elimination of the pre-processing step.
+.P
+2) If you embed '\\tex' commands inside your figures, you now need to
+explicitly _tell_ PSfrag to process these commands. To do so, use
+\\usepackage[scanall]{psfrag}
+instead of
+\\usepackage{psfrag}
+at the beginning of your LaTeX file.
+.P
+If you only use '\\tex' commands in a small number of figures, then a
+more efficient might be to turn on '\\tex'-scanning only for those
+figures. To do that, add the command '\\psfragscanon' immediately before
+each relevant \\includegraphics or \\epsfbox command.
+.P
+.SH NOTES
+See the PSfrag documentation for further information.
+.SH "SEE ALSO"
+dvips(1), gs(1), ghostview(1), latex(1)
+.SH AUTHORS
+.IP psfrag@rascals.stanford.edu
+The PSfrag maintainer's mailing list.