summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex')
-rw-r--r--Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex52
1 files changed, 30 insertions, 22 deletions
diff --git a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex
index 6cfcd4bbd96..7db4aa68733 100644
--- a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex
+++ b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-introduction.tex
@@ -12,7 +12,7 @@
The \pgfname\ package, where ``\pgfname'' is supposed to mean ``portable
graphics format'' (or ``pretty, good, functional'' if you
-prefer\dots), is a package for creating graphics in an ``inline''
+prefer\dots), is a package for creating graphics in an ``inline''
manner. It defines a number of \TeX\ commands that draw
graphics. For example, the code |\tikz \draw (0pt,0pt) -- (20pt,6pt);|
yields the line \tikz \draw (0pt,0pt) -- (20pt,6pt); and the code
@@ -20,13 +20,13 @@ yields the line \tikz \draw (0pt,0pt) -- (20pt,6pt); and the code
\fill[orange] (1ex,1ex) circle (1ex);.
In a sense, when you use \pgfname\ you ``program'' your graphics, just
-as you ``program'' your document when you use \TeX. You get all
-the advantages of the ``\TeX-approach to typesetting'' for your
+as you ``program'' your document when you use \TeX. You get all
+the advantages of the ``\TeX-approach to typesetting'' for your
graphics: quick creation of simple graphics, precise positioning, the
use of macros, often superior typography. You also inherit all the
disadvantages: steep learning curve, no \textsc{wysiwyg}, small
changes require a long recompilation time, and the code does not
-really ``show'' how things will look like.
+really ``show'' how things will look like.
@@ -46,7 +46,7 @@ The \pgfname\ system consists of different layers:
differences. For example, the system command
|\pgfsys@lineto{10pt}{10pt}| extends the current path to the coordinate
$(10\mathrm{pt},10\mathrm{pt})$ of the current
- |{pgfpicture}|. Depending on whether |dvips|,
+ |{pgfpicture}|. Depending on whether |dvips|,
|dvipdfm|, or |pdftex| is used to process the document, the system
command will be converted to different |\special| commands.
The system layer is as ``minimalistic'' as possible since each
@@ -83,7 +83,7 @@ The \pgfname\ system consists of different layers:
the third, one for closing the path, and one for actually painting
the triangle (as opposed to filling it). With the |tikz| frontend
all this boils down to a single simple \textsc{metafont}-like
- command:
+ command:
\begin{verbatim}
\draw (0,0) -- (1,0) -- (1,1) -- cycle;
\end{verbatim}
@@ -94,10 +94,10 @@ The \pgfname\ system consists of different layers:
The \tikzname\ frontend is the ``natural'' frontend for \pgfname. It gives
you access to all features of \pgfname, but it is intended to be
easy to use. The syntax is a mixture of \textsc{metafont} and
- \textsc{pstricks} and some ideas of myself. This frontend is
+ \textsc{pstricks} and some ideas of myself. This frontend is % TODOsp: change all `pstricks' to `PStricks'? (ff)
\emph{neither} a complete \textsc{metafont} compatibility layer nor
a \textsc{pstricks} compatibility layer and it is not intended to
- become either.
+ become either.
\item
The |pgfpict2e| frontend reimplements the standard \LaTeX\
|{picture}| environment and commands like |\line| or |\vector|
@@ -157,15 +157,15 @@ other packages.
\item
The |xypic| package is an older package for creating
graphics. However, it is more difficult to use and to learn because
- the syntax and the documentation are a bit cryptic.
+ the syntax and the documentation are a bit cryptic.
\item
The |dratex| package is a small graphic package for creating a
graphics. Compared to the other package, including \pgfname, it is
- very small, which may or may not be an advantage.
+ very small, which may or may not be an advantage.
\item
The |metapost| program is a very powerful alternative to
\pgfname. However, it is an external program, which entails a
- bunch of problems. The time needed both to create a small graphic
+ bunch of problems. The time needed both to create a small graphic
and also to compile it is much greater than in \pgfname.
The main problem with |metapost|, however, is the inclusion of
labels. This is \emph{much} easier to achieve using \pgfname.
@@ -182,11 +182,11 @@ other packages.
\subsection{Utility Packages}
-The \pgfname\ package comes along with a numer of utility package that
+The \pgfname\ package comes along with a number of utility package that
are not really about creating graphics and which can be used
independently of \pgfname. However, they are bundled with \pgfname,
partly out of convenience, partly because their functionality is
-closely intertwined with \pgfname. These utility packages are:
+closely intertwined with \pgfname. These utility packages are:
\begin{enumerate}
\item The |pgfkeys| package defines a powerful key management
facility. It can be used completely independently of \pgfname.
@@ -208,7 +208,7 @@ closely intertwined with \pgfname. These utility packages are:
\LaTeX\ without the use of any external programs. However,
|pgfpages| can do quite a lot more than that. You can use it to put
logos and watermark on pages, print up to 16 pages on one page, add
- borders to pages, and more.
+ borders to pages, and more.
\end{enumerate}
@@ -223,7 +223,7 @@ esoteric features are discussed later.
If you have not yet installed \pgfname, please read the installation
first. Second, it might be a good idea to read the tutorial. Finally,
-you might wish to skim through the description of \tikzname. Typically,
+you might wish to skim through the description of \tikzname. Typically,
you will not need to read the sections on the basic layer. You will
only need to read the part on the system layer if you intend to write
your own frontend or if you wish to port \pgfname\ to a new driver.
@@ -238,12 +238,21 @@ in green is optional and can be left out.
\label{section-authors}
The bulk of the \pgfname\ system and its documentation was written by
-Till Tantau. The \pgfname\ mathematical engine, many shapes, and the
-decoration engine were written and documented by Mark
-Wibrow. Additionally, numerous people have contributed to the
-\pgfname\ system by writing emails, spotting bugs, or sending
-libraries. Many thanks to all these people, who are too numerous to
-name them all!
+Till Tantau. A further member of the main team is Mark Wibrow, who
+is responsible, for example, for the \pgfname\ mathematical engine,
+many shapes, the decoration engine, and matrices. The third member is
+Christian Feuers\"anger who contributed the floating point library,
+image externalization, extended key processing, and automatic hyperlinks
+in the manual.
+
+Furthermore, occasional contributions have been made by Christophe
+Jorssen, Jin-Hwan Cho, Olivier Binda, Matthias Schulz, Ren\'ee Ahrens,
+Stephan Schuster, and Thomas Neumann.
+
+Additionally, numerous people have contributed to the \pgfname\ system
+by writing emails, spotting bugs, or sending libraries and patches.
+Many thanks to all these people, who are too numerous to name them
+all!
@@ -284,4 +293,3 @@ following:
Please, do not phone me in my office (unless, of course, you attend
one of my lectures).
\end{enumerate}
-