1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
%%% instruct.txt
%%% part of mfpic 0.4.0 2000/08/31
%%%
This is a beta-test version of mfpic.
See manifest.txt for a list of files and a brief description of each.
The main new feature is support for production and inclusion of MetaPost
graphics.
Files Required
--------------
In a minimal installation only mfpic.tex is required by TeX or LaTeX,
grafbase.mf for Metafont and grafbase.mp for MetaPost (plus
dvipsnam.mp). The file mfpic.sty merely inputs mfpic.tex. It allows for
use in the LaTeX \usepackage command. The rest of the .tex files are
documentation and test files.
-- mfpic.tex goes where TeX will find it, mfpic.sty where LaTeX will
find it. On my system I put both in /texmf/tex/generic/mfpic/ .
-- All .mp files (grafbase.mp and dvipsnam.mp) go where MetaPost will
find them. On my system, I use /texmf/metapost/grafbase/ .
---The file grafbase.mf goes where Metafont will find it. On my system,
/texmf/metafont/grafbase/ .
Please process the supplementary documentation, mppicdoc.tex (run plain
TeX on it, making sure header.tex is where TeX will find it), and read
it before trying anything further. If you are new to mfpic, do the same
with mfpicdoc.tex.
The remaining instructions are about using mfpic with MetaPost.
In order to turn on MetaPost support you put something like this in your
file.tex (plain TeX, plain pdfTeX or LaTeX209):
+-----------------------+
| \input mfpic |
| \usemetapost |
| \opengraphsfile{figs} |
+-----------------------+
or in LaTeX2e or pdfLaTeX:
+------------------------------+
| \usepackage[metapost]{mfpic} |
| \opengraphsfile{figs} |
+------------------------------+
Using mfpic with MetaPost
-------------------------
For the most part, mfpic with MetaPost support is used just like mfpic
with Metafont, but instead of running a combination of Metafont and
gftopk on the output .mf file, one uses Metapost on the output .mp file.
That is:
1) Run the appropriate TeX on your file.tex. A file figs.mp is produced.
2) Run "mpost figs" (or "mp figs" on some systems). This creates files
figs.1, figs.2, etc., one for each mfpic environment.
3) Run TeX again, this resolves bounding box information and includes
the eps figures.
4) Process with an appropriate dvi-to-whatever processor that supports
.eps or .mps figure specials. (Omitted for pdf(La)TeX)
For this to work out of the box with plain TeX and LaTeX209 you need
epsf.tex (normally distributed with dvips); for pdfTeX and pdfLaTeX you
need supp-mis.tex and supp-pdf.tex (normally distributed with pdftex);
and for LaTeX2e and pdfLaTeX you need the graphics package (using the
pdftex option with pdfLaTeX). The graphics package is in most TeX
distributions, or can be found in CTAN/macros/latex/required/graphics/ .
The file epsf.tex supports only dvips \special s, but many dvi-to-whatever
software that can handle eps inclusions will accept these. If your
system happens not to be compatible with epsf.tex, and you need to use
plain TeX, you will need to load the appropriate macro files, and
redefine \setmfpicgraphic to the appropriate file inclusion command. See
mppicdoc.tex.
The syntax of the mfpic environments has _not_ changed. You still type
"\mfpic" or "\begin{mfpic}" to start a picture, and \lines{(0,0),(1,1)}
to draw a line, for example. There are a few new commands, and some old
commands now take an optional argument for the color (see mppicdoc), but
these are, well, optional. On the other hand, any old \mfsrc hacks are
almost certainly doomed to failure, as grafbase.mp is quite different
from grafbase.mf.
Compatibility
-------------
This version is intended to be backward compatible with versions
0.2.10.9 or later. The following should all work (within limits, in
particular nothing is likely to work for hacks that used \mfsrc):
1) Running MetaPost on old .mf files created with mfpic 0.2.10.9 or
later. Unless you hacked about with \mfsrc, this _should_ create
_some_ sort of picture without error messages (assuming none occurred
before). Postscript is a little more sensitive to the order of
drawing, so things might not look quite the same (see mppicdoc). On
the other hand, sometimes they look better. Please let us know if you
try this and anything goes wrong that you think shouldn't.
2) Using \input mfpic _without_ \usemetapost. This will create a
Metafont file, almost the same file as before, and it should be
possible to run either Metafont + gftopk, or MetaPost on the result.
In fact, some bugs have been removed (but maybe some have been added,
too). You could try this in old files (that used mfpic 0.2.10.9 or
later). If you do try this, please let us know if anything goes
wrong.
3) Adding \usemetapost to old files (using mfpic 0.2.10.9 or later).
Things should work (except for \mfsrc commands), but just as in (1)
above, Postscript can be more sensitive to the order of drawing.
Again, please report any problems.
Do _not_ run MetaFONT on figs.mp. Also, make sure MetaPost can find
grafbase.mp, otherwise it may try to input grafbase.mf. This will never
succeed.
Let us know the good as well as the bad results you have.
Where?
------
The latest test versions of this distribution should be available
at <a href="http://comp.uark.edu/~luecking/tex/mfpic.html">my web site</a>.
--
Dan Luecking email: luecking@comp.uark.edu
Department of Mathematical Sciences
University of Arkansas
Fayetteville, Arkansas 72701-1201
U.S.A
|
