diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-drivers.tex')
-rw-r--r-- | Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-drivers.tex | 89 |
1 files changed, 75 insertions, 14 deletions
diff --git a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-drivers.tex b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-drivers.tex index e4d12ab2392..15201b087aa 100644 --- a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-drivers.tex +++ b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-drivers.tex @@ -1,8 +1,11 @@ -% Copyright 2005 by Till Tantau <tantau@cs.tu-berlin.de>. +% Copyright 2006 by Till Tantau % -% This program can be redistributed and/or modified under the terms -% of the LaTeX Project Public License Distributed from CTAN -% archives in directory macros/latex/base/lppl.txt. +% This file may be distributed and/or modified +% +% 1. under the LaTeX Project Public License and/or +% 2. under the GNU Free Documentation License. +% +% See the file doc/generic/pgf/licenses/LICENSE for more details. \section{Input and Output Formats} @@ -65,8 +68,8 @@ The files in the |generic/pgf| directory do the actual work. \subsubsection{Using the Plain \TeX\ Format} When using the plain \TeX\ format, you say |\input{pgf.tex}| or -|\input{tikz.tex}|. Instead of |\begin{pgfpicture}| and - |\end{pgfpicture}| you use |\pgfpicture| and |\endpicture|. +|\input{tikz.tex}|. Then, instead of |\begin{pgfpicture}| and + |\end{pgfpicture}| you use |\pgfpicture| and |\endpgfpicture|. Unlike for the \LaTeX\ format, \pgfname\ is not as good at discerning the appropriate configuration for the plain \TeX\ format. In @@ -86,10 +89,27 @@ also just include the correct |tikz.code.tex| file. \subsubsection{Using the Con\TeX t Format} -Currently, there is no special support for the Con\TeX t -format. Rather, you have to use \pgfname\ and \tikzname\ as if you -were using the plain \TeX\ format when using Con\TeX t. This may -change in the future. +When using the Con\TeX t format, you say |\usemodule[pgf]| or +|\usemodule[tikz]|. As for the plain \TeX\ format you also have +to replace the start- and end-of-environment tags as follows: Instead +of |\begin{pgfpicture}| and |\end{pgfpicture}| you use +|\startpgfpicture| and |\stoppgfpicture|; similarly, instead of +|\begin{tikzpicture}| and |\end{tikzpicture}| you use must now use +|\starttikzpicture| and |\stoptikzpicture|; and so on for other +environments. + +The Con\TeX t support is very similar to the plain \TeX\ support, so +the same restrictions apply: You may have to set the output +format directly and graphics inclusion may be a problem. + +In addition to |pgf| and |tikz| there also exist modules like +|pgfcore|, |pgfbaseimage|, |pgflibrarysnakes| and so on. To +use them, you may need to include the module |pgfmod| first (the +modules |pgf| and |tikz| both include |pgfmod| for you, so typically +you can skip this). This special module is necessary since Con\TeX t +satanically restricts the length of module names to 6 characters +and \pgfname's long names are mapped +to cryptic 6-letter-names for you by the module |pgfmod|. @@ -130,7 +150,7 @@ the intermediate |.dvi|-stage. However, from the programmer's point of view they behave exactly as if there where an intermediate stage. Normally, \TeX\ only produces letter--coordinate pairs as its -``output.'' This obviously makes is difficult tho draw, say, a +``output.'' This obviously makes is difficult to draw, say, a curve. For this, ``special'' commands can be used. Unfortunately, these special commands are not the same for the different programs that process the |.dvi|-file. Indeed, every program that takes a @@ -195,12 +215,15 @@ exactly the same. inclusion and does not support masking. \item In plain \TeX\ mode it does not support image inclusion. + \item + Remembering of pictures (inter-picture connections) is not + supported. \end{enumerate} \end{filedescription} \begin{filedescription}{pgfsys-vtex.def} This is the driver file for use with the commercial \textsc{vtex} - program. Even though is will produce \textsc{pdf} output, it + program. Even though it produces \textsc{pdf} output, it includes |pgfsys-common-postscript.def|. Note that the \textsc{vtex} program can produce \emph{both} Postscript and \textsc{pdf} output, depending on the command line @@ -220,7 +243,10 @@ exactly the same. Shading is fully implemented, but yields the same quality as the implementation for |dvips|. \item - Opacity is not implemented at all. + Opacity is not supported. + \item + Remembering of pictures (inter-picture connections) is not + supported. \end{enumerate} \end{filedescription} @@ -249,6 +275,9 @@ conversion program like |ps2pdf| or the Acrobat Distiller. \item Opacity works only in conjunction with newer versions of GhostScript. + \item + Remembering of pictures (inter-picture connections) is not + supported. \end{enumerate} \end{filedescription} @@ -286,6 +315,9 @@ graphic in your text. \item In plain \TeX\ mode it does not support image inclusion. \item + Remembering of pictures (inter-picture connections) is not + supported. + \item Text inside |pgfpicture|s is not supported very well. The reason is that the \textsc{svg} specification currently does not support text very well and it is also not possible to correctly ``escape @@ -311,7 +343,7 @@ graphic in your text. output of |tex4ht| to a new file called |\jobname-xxx.svg|, where |xxx| is a number that is increased for each graphic. Then, till the end of the picture, each (system layer) graphic command creates a - specials that insert appropriate \textsc{svg} literal text into the + special that inserts appropriate \textsc{svg} literal text into the output file. The exact details are a bit complicated since the imaging model and the processing model of PostScript/\pdf\ and \textsc{svg} are not quite the same; but they are ``close enough'' @@ -319,3 +351,32 @@ graphic in your text. \end{filedescription} +\subsubsection{Producing Perfectly Portable DVI Output} + +\begin{filedescription}{pgfsys-dvi.def} + This is a driver file that can be used with any output driver, + except for |tex4ht|. + + The driver will produce perfectly portable |.dvi| files by composing + all pictures entirely of black rectangles, the basic and only graphic + shape supported by the \TeX\ core. Even straight, but slanted lines + are tricky to get right in this model (they need to be composed of + lots of little squares). + + Naturally, \emph{very little} is possible with this driver. In fact, + so little is possible that it is easier to list what is possible: + \begin{itemize} + \item Text boxes can be placed in the normal way. + \item Lines and curves can be drawn (stroked). If they are not + horizontal or vertical, they are composed of hundred of small + rectangles. + \item Lines of different width are supported. + \item Transformations are supported. + \end{itemize} + Note that, say, even filling is not supported! (Let alone color or + anything fancy.) + + This driver has only one real applications: It might be useful when + you only need horizontal or vertical lines in a picture. Then, the + results are quite satisfactory. +\end{filedescription} |