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.tex70
1 files changed, 41 insertions, 29 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 7bd8de69275..6cfcd4bbd96 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
@@ -68,10 +68,10 @@ The \pgfname\ system consists of different layers:
The basic layer is consists of a \emph{core}, which consists of
several interdependent packages that can only be loaded \emph{en
- bloc,} and additional packages that extend the core by more
+ bloc,} and additional \emph{modules} that extend the core by more
special-purpose commands like node management or a plotting
- interface. For instance, the \textsc{beamer} package uses the core,
- but not all of the additional packages of the basic layer.
+ interface. For instance, the \textsc{beamer} package uses only the
+ core and not, say, the |shapes| modules.
\item[Frontend layer:]
A frontend (of which there can be several) is a set of commands
or a special syntax that makes using the basic layer easier. A
@@ -143,7 +143,7 @@ other packages.
driver that produces anything but PostScript code.
Compared to \pgfname, |pstricks| has a broader support base. There
- are many nice extra packages for special purpose sitations that have
+ are many nice extra packages for special purpose situations that have
been contributed by users over the last decade.
The \tikzname\ syntax is more consistent than the |pstricks| syntax
@@ -180,27 +180,36 @@ other packages.
-\subsection{Utilities: Page Management}
-
-The \pgfname\ package include a special subpackage called |pgfpages|,
-which is used to assemble several pages into a single page. This
-package is not really about creating graphics, but it is part of \pgfname\
-nevertheless, mostly because its implementation uses \pgfname\ heavily.
-
-The subpackage |pgfpages| provides commands for assembling several
-``virtual pages'' into a single ``physical page.'' The idea is that
-whenever \TeX\ has a page ready for ``shipout,'' |pgfpages| interrupts
-this shipout and instead stores the page to be shipped out in a
-special box. When enough ``virtual pages'' have been accumulated in
-this way, they are scaled down and arranged on a ``physical page,''
-which then \emph{really} shipped out. This mechanism allows you to
-create ``two page on one page'' versions of a document directly inside
-\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.
+\subsection{Utility Packages}
+The \pgfname\ package comes along with a numer 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:
+\begin{enumerate}
+\item The |pgfkeys| package defines a powerful key management
+ facility. It can be used completely independently of \pgfname.
+\item The |pgffor| package defines a useful |\foreach| statement.
+\item The |pgfcalendar| package defines macros for creating
+ calendars. Typically, these calendars will be rendered using
+ \pgfname's graphic engine, but you can use |pgfcalendar| also
+ typeset calendars using normal text. The package also defines
+ commands for ``working'' with dates.
+\item The |pgfpages| package is used to assemble several pages into a
+ single page. It provides commands for assembling several
+ ``virtual pages'' into a single ``physical page.'' The idea is that
+ whenever \TeX\ has a page ready for ``shipout,'' |pgfpages| interrupts
+ this shipout and instead stores the page to be shipped out in a
+ special box. When enough ``virtual pages'' have been accumulated in
+ this way, they are scaled down and arranged on a ``physical page,''
+ which then \emph{really} shipped out. This mechanism allows you to
+ create ``two page on one page'' versions of a document directly inside
+ \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.
+\end{enumerate}
@@ -229,11 +238,14 @@ 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 was 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. 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!
+
+
\subsection{Getting Help}