summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex')
-rw-r--r--Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex56
1 files changed, 26 insertions, 30 deletions
diff --git a/Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex b/Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex
index e420947df95..c818579dfd1 100644
--- a/Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex
+++ b/Master/texmf-dist/doc/generic/mfpic/mfpic-doc.tex
@@ -1,5 +1,5 @@
%%% File: mfpic-doc.tex
-%%% A part of mfpic 1.04 2010/03/30
+%%% A part of mfpic 1.05 2010/06/10
%%%
% Documentation of mfpic macros
\documentclass[letterpaper]{article}
@@ -29,7 +29,7 @@
\stepcounter{secnumdepth}
\title{\Mfp{}: Pictures in \TeX{}\\ with Metafont and
-MetaPost\thanks{Copywrite 2002--2006, Daniel H. Luecking}}
+MetaPost\thanks{Copyright 2002--2010, Daniel H. Luecking}}
\author{%
Daniel H. Luecking%
@@ -3472,14 +3472,10 @@ of the figure (as given by the arguments to the \env{mfpic} environment)
is divided by 100. For example, in a 5-by-10 graph, giving a step size
of $0$ will actually select \meta{step}${}= 10/100 = 0.1$.
-The algorithm used will produce incorrect results if there are two
-points on the curve closer that \meta{step} in straight-line distance,
+The algorithm used will produce imprecise results if there are two
+points on the curve closer than \meta{step} in straight-line distance,
but much further apart when measured along the curve.
-The algorithm used will produce incorrect results if two points of the
-curve that are distant (as measured along the curve) are closer than
-\meta{step} in straight-line distance.
-
\subsection{Plotting external data files}\label{external}
\begin{cd}\pagelabel{datafile}
@@ -6071,17 +6067,17 @@ further dicussion.
\end{cd}
With the \opt{metapost} option, when you write
-\cs{opengraphsfile{figs}}, a file \file{figs.mp} is created. By default,
-running \MP{} on it results in files named \file{figs.1}, \file{figs.2},
-etc. Recent \MP{} allows the output filenames to be modified. As of
-\mfp{} version \mfpversion, you can do this to some extent from your
-\file{.tex} file. One needs to define a template that tells \MP{} how to
-construct the output file name from the `jobname' and the figure number.
-This is done with the above command. In \meta{template} you can put any
-plain characters, plus the two special tokens: \verb$\_$ and \verb$\#$.
-Each figure's filename is constructed by replacing these tokens with the
-\MP{} jobname and the figure number, respectively. For example, with the
-jobname \file{figs},
+\cs{opengraphsfile}\marg{figs}, a file \file{figs.mp} is created. By
+default, running \MP{} on it results in files named \file{figs.1},
+\file{figs.2}, etc. Recent \MP{} allows the output filenames to be
+modified. As of \mfp{} version 1.00, you can do this to some extent from
+your \file{.tex} file. One needs to define a template that tells \MP{}
+how to construct the output file name from the `jobname' and the figure
+number. This is done with the above command. In \meta{template} you can
+put any plain characters, plus the two special tokens: \verb$\_$ and
+\verb$\#$. Each figure's filename is constructed by replacing these
+tokens with the \MP{} jobname and the figure number, respectively. For
+example, with the jobname \file{figs},
\begin{verbatim}
\setfilenametemplate{my\_-\#.mps}
\end{verbatim}
@@ -6139,7 +6135,7 @@ with the \cs{opengraphsfile} commands reading of these booleans.
\end{cd}
This expands to the current \mfp{} version multiplied by 100. At this
-writing, it produces `\texttt{104}' because the version is 1.04. It can
+writing, it produces `\texttt{105}' because the version is 1.05. It can
be used to test the version:
\begin{verbatim}
\ifx\mfpicversion\undefined \def\mfpicversion{0}\fi
@@ -6304,12 +6300,12 @@ all later environments.
When \cs{plotdata} passes from one curve to the next, it increments a
counter and uses that counter to select a dash pattern, color, or
-symbol. It uses predefined dash \mfc{dashtype0} through \mfc{dashtype5},
-or predefined colors \mfc{colortype0} through \mfc{colortype7}, or
-predefined symbols \mfc{pointtype0} through \mfc{pointtype8}. Here
-follows a description of each of these variables. These variables must
-not be used in the second argument of \cs{reconfigureplot}, whose
-purpose is to redefine these variables.
+symbol. It uses predefined dash patterns named \mfc{dashtype0} through
+\mfc{dashtype5}, or predefined colors named \mfc{colortype0} through
+\mfc{colortype7}, or predefined symbols named \mfc{pointtype0} through
+\mfc{pointtype8}. Here follows a description of each of these variables.
+These variables must not be used in the second argument of
+\cs{reconfigureplot}, whose purpose is to redefine these variables.
\medskip
Under \cs{dashedlines}, we have the following dash patterns:
@@ -6383,10 +6379,10 @@ fonts prepared for a LaserJet4 (600 DPI), this means 6.825 inches
(17.3355cm). For a 1200 DPI pronter, the limit is 3.4125 inches.
A similar limit holds for numbers input, and the values of variables:
-\MF{} will return an error for \mfc{sin 4096}. Intermediate values can
-be greater (\mfc{sin (2*2048)} will cause no error), but final, stored
-results are subject to the limit. An \mfp{} example that generated an
-error recently was:
+\MF{} will return an error for ``\mfc{sin 4096}''. Intermediate values
+can be greater (\mfc{sin (2*2048)} will cause no error), but final,
+stored results are subject to the limit. An \mfp{} example that
+generated an error recently was:
\begin{verbatim}
\mfpicunit 1mm
\mfpic[10]{-3}{7}{-3.5}{5}