Differences between current version and predecessor to the previous major change of virmpost(1).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, June 4, 2002 12:22:59 am | by perry | |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:22:59 am | by perry | Revert |
@@ -13,9 +13,9 @@
----
!!NAME
-mpost, inimpost, virmpost - MetaPost, a system for drawing pictures
+mpost, inimpost, virmpost - !
MetaPost, a system for drawing pictures
!!SYNOPSIS
__mpost__ [[''options''] [[''commands'']
@@ -27,25 +27,25 @@
info file or manual ''Web2C: A TeX
implementation''.
-MetaPost interprets the MetaPost language and produces
-PostScript pictures. The MetaPost language is similar to
+!
MetaPost interprets the !
MetaPost language and produces
+!
PostScript pictures. The !
MetaPost language is similar to
Knuth's M ETAFONT with additional features
for including tex(1) or troff(1) commands and
-accessing features of PostScript not found in M
+accessing features of !
PostScript not found in M
ETAFONT .
-Like TEX and M ETAFONT , MetaPost is normally
+Like TEX and M ETAFONT , !
MetaPost is normally
used with a large body of precompiled macros. This version
-of MetaPost looks at its command line to see what name it
+of !
MetaPost looks at its command line to see what name it
was called under. Both __inimpost__ and __virmpost__
are symlinks to the __mpost__ executable. When called as
__inimpost__ (or when the __--ini__ option is given)
it can be used to precompile macros into a ''.mem'' file.
When called as __virmpost__ it will use the ''plain''
-mem. When called under any other name, MetaPost will use
+mem. When called under any other name, !
MetaPost will use
that name as the name of the mem to use. For example, when
called as __mpost__ the ''mpost'' mem is used, which
is identical to the ''plain'' mem. Other mems than
''plain'' are rarely used.
@@ -54,9 +54,9 @@
The ''commands'' given on the command line to the program
are passed to it as the first input line. (But it is often
easier to type extended arguments as the first input line,
since UNIX shells tend to gobble up or misinterpret
-MetaPost's favorite symbols, like semicolons, unless you
+!
MetaPost's favorite symbols, like semicolons, unless you
quote them.) The first line should begin with a filename, a
\''controlsequence'', or a
''''.
@@ -88,9 +88,9 @@
__btex__ ''TeX commands''
__etex__
-This causes ''mp'' to generate a MetaPost picture
+This causes ''mp'' to generate a !
MetaPost picture
expression that corresponds to the TEX commands. If the TEX
commands generate more than one line of text, it must be in
a ''vbox'' or a minipage environment.
@@ -109,18 +109,18 @@
Since most TEX fonts have to be downloaded as bitmaps, the
''btex'' feature works best when the output of ''mp''
is to be included in a TEX document so that dvips(1)
-can download the fonts. For self-contained PostScript output
+can download the fonts. For self-contained !
PostScript output
that can be used directly or included in a ''troff''
-document, start your MetaPost input file with the command
-''prologues:=1'' and stick to standard PostScript fonts.
-TEX and MetaPost use the names in the third column of the
+document, start your !
MetaPost input file with the command
+''prologues:=1'' and stick to standard !
PostScript fonts.
+TEX and !
MetaPost use the names in the third column of the
file ''trfonts.map'', which can be found in the
-directories with support files for MetaPost.
+directories with support files for !
MetaPost.
-MetaPost output can be included in a ''troff'' document
+!
MetaPost output can be included in a ''troff'' document
via the ''-m pictures'' macro package. In this case
''mp'' should be invoked with the __-T__ flag so that
the commands between ''btex'' and ''etex'' or between
''verbatimtex'' and ''etex'' are interpreted as
@@ -128,9 +128,9 @@
''prologues:=1'' ).
!!OPTIONS
-This version of MetaPost understands the following command
+This version of !
MetaPost understands the following command
line options.
__--file-line-error-style__
@@ -175,9 +175,9 @@
__--mem__ ''mem''
Use ''mem'' as the name of the mem to be used, instead of
-the name by which MetaPost was called or a ''%''
+the name by which !
MetaPost was called or a ''%''
line.
__--progname__ ''name''
@@ -226,9 +226,9 @@
utility can be used to query the values of the
variables.
-If the environment variable TEXMFOUTPUT is set, MetaPost
+If the environment variable TEXMFOUTPUT is set, !
MetaPost
attempts to put its output files in it, if they cannot be
put in the current directory.
@@ -259,9 +259,9 @@
MPXCOMMAND
The name of a shell script that converts embedded
-typesetting commands to a form that MetaPost understands.
+typesetting commands to a form that !
MetaPost understands.
Defaults: ''makempx'' for ''tex'' and ''troffmpx''
for ''troff''.
@@ -269,9 +269,9 @@
The version of TEX - or L A TEX - to use when
processing ''btex'' and ''verbatimtex'' commands.
-Default ''tex''. This version of MetaPost allows you to
+Default ''tex''. This version of !
MetaPost allows you to
use a `%''
TROFF
@@ -303,26 +303,26 @@
''inimpost'' and giving macro definitions followed by a
''dump'' command.
-The MetaPost language is similar to M ETAFONT
-, but the manual ''A User's Manual for MetaPost'' assumes
-no knowledge of M ETAFONT . MetaPost does not
+The !
MetaPost language is similar to M ETAFONT
+, but the manual ''A User's Manual for !
MetaPost'' assumes
+no knowledge of M ETAFONT . !
MetaPost does not
have bitmap output commands or M ETAFONT 's
online display mechanism.
!!FILES
''mpost.pool''
-Encoded text of MetaPost's messages.
+Encoded text of !
MetaPost's messages.
''*.mem''
-Predigested MetaPost mem files.
+Predigested !
MetaPost mem files.
''plain.mp''
@@ -340,9 +340,9 @@
''$TEXMFMAIN/metapost/base/*.mp''
-The standard MetaPost macros included in the original
+The standard !
MetaPost macros included in the original
distribution.
''$TEXMFMAIN/metapost/support/*''
@@ -355,34 +355,34 @@
''$TEXMFMAIN/metapost/support/trfonts.map''
Table of corresponding font names for ''troff'' and
-PostScript.
+!
PostScript.
''psfonts.map''
Table of corresponding font names for ''tex'' and
-PostScript.
+!
PostScript.
''$TEXMFMAIN/doc/metapost/examples.mp''
The source file for a few sample figures that are part of a
L A TEX document
''$TEXMFMAIN/doc/metapost/mpintro.tex'' that describes
-the MetaPost system in a little more detail.
+the !
MetaPost system in a little more detail.
!!SUGGESTED READING
Donald E. Knuth, ''The M ETAFONT book''
(Volume C of ''Computers and Typesetting''),
Addison-Wesley, 1986, ISBN 0-201-13445-4.
-John D. Hobby, ''A User's Manual for MetaPost'', CSTR
+John D. Hobby, ''A User's Manual for !
MetaPost'', CSTR
162, AT''
-John D. Hobby, ''Drawing Graphs with MetaPost'', CSTR
+John D. Hobby, ''Drawing Graphs with !
MetaPost'', CSTR
164, AT''
TUGboat'' (the journal of the TEX Users
Group).
!!SEE ALSO
@@ -391,28 +391,28 @@
tex(1), mf(1), dvips(1).
!!AUTHORS
-MetaPost was designed by John D. Hobby, incorporating
+!
MetaPost was designed by John D. Hobby, incorporating
algorithms from M ETAFONT by Donald E. Knuth.
It was originally implemented on Unix, incorporating
system-dependent routines from __web2c__, while not
relying on it except for the actual W EB
-to-C translator.
-Ulrik Vieth adapted MetaPost to take advantage of the
+Ulrik Vieth adapted !
MetaPost to take advantage of the
advanced path searching features in more recent versions of
-__web2c__ and worked towards fully integrating MetaPost
+__web2c__ and worked towards fully integrating !
MetaPost
into the canonical Unix TEX distribution. He also updated
and extended this manual page.
!!TRIVIA
-Unlike TEX and M ETAFONT , MetaPost
+Unlike TEX and M ETAFONT , !
MetaPost
originally didn't use any fancy logo. John Hobby says he
-prefers the spelling ``MetaPost'', yet Don Knuth has updated
+prefers the spelling ``!
MetaPost'', yet Don Knuth has updated
the M ETAFONT ''logo.mf'' font to be able
-to typeset a proper MetaPost logo similar to the M
+to typeset a proper !
MetaPost logo similar to the M
ETAFONT logo. Feel free to use whatever you
think is more appropriate!
----
