applied various patches

doc/generic/pgf/ChangeLog

@@ -1,3 +1,17 @@
+2013-06-20 Till Tantau <[email protected]>
+
+	- Applied patch #19 pgfkeys: ".search also" fails at unbalanced "\if" values
+	- Applied patch #18 Missing grid lines with
+	  negative increment
+	- Applied patch #17 TikZ folding library
+	- Applied patch #14 inheritance in the oo module
+	- Applied patch #13 leaking space in \pgfpointintersectionoflines
+	- Applied patch #11 Patch for Bug #3165961 (\pgfmathmax and \pgfmathmin)
+	- Fixed problem of patch #9 Add papersize to XeTeX driver
+	- Applied patch #8 Support for changing physical page size with XeTeX
+	  (also added position saving support, while I was at it...)
+	- Applied patches #3, #4, #5, #6 (typos in manual) as far as possible
+
 2013-06-18 Till Tantau <[email protected]>
 
 	- "cycle" can now be used with all path operations where it

doc/generic/pgf/text-en/pgfmanual-en-base-paths.tex

@@ -540,15 +540,15 @@ \subsection{Rectangle Path Operations}
 
 \subsection{The Grid Path Operation}
 
-\begin{command}{\pgfpathgrid\oarg{options}\marg{lower left}\marg{upper right}}
+\begin{command}{\pgfpathgrid\oarg{options}\marg{first corner}\marg{second corner}}
   Appends a grid to the current path. That is, a (possibly large)
   number of parts are added to the path, each part consisting of a
   single horizontal or vertical straight line segment.
 
   Conceptually, the origin is part of the grid and the grid is clipped
-  to the rectangle specified by the \meta{lower left} and
-  the \meta{upper right} corner. However, no clipping occurs (this
-  command just adds parts to the current path). Rather, the points
+  to the rectangle specified by the \meta{first corner} and
+  the \meta{second corner}. However, no clipping occurs (this
+  command just adds parts to the current path) and the points
   where the lines enter and leave the ``clipping area'' are computed
   and used to add simple lines to the current path.
 
@@ -576,7 +576,7 @@ \subsection{The Grid Path Operation}
 \end{pgfpicture}
 \end{codeexample}
   The command will apply coordinate transformations and update the
-  bounding boxes tightly. As for ellipses, the transformations are
+  bounding boxes. As for ellipses, the transformations are
   applied to the ``conceptually finished'' grid.
 \begin{codeexample}[]
 \begin{pgfpicture}

doc/generic/pgf/text-en/pgfmanual-en-drivers.tex

@@ -131,7 +131,8 @@ \subsection{Supported Output Formats}
   \TeX\ typesets your text and graphics. The result of this
   typesetting is mainly a long list of letter--coordinate pairs, plus
   (possibly) some ``special'' commands. This long list of pairs
-  is written to something called a |.dvi|-file.
+  is written to something called a |.dvi|-file (informally known as
+  ``device-independent file'').
 \item
   Some other program reads this |.dvi|-file and translates the
   letter--coordinate pairs into, say, PostScript commands for placing
@@ -142,7 +143,7 @@ \subsection{Supported Output Formats}
 and |dvips|. The |latex| program (which is just the |tex| program
 called with the \LaTeX-macros preinstalled) produces a |.dvi|-file as
 its output. The |dvips| program takes this output and produces a
-|.ps|-file (a PostScript) file. Possibly, this file is further
+|.ps|-file (a PostScript file). Possibly, this file is further
 converted using, say, |ps2pdf|, whose name is supposed to mean
 ``PostScript to PDF.'' Another example of programs using this
 process is the combination of |tex| and |dvipdfm|. The |dvipdfm|
@@ -153,7 +154,7 @@ \subsection{Supported Output Formats}
 output, this time it is a |.html| file. The programs |pdftex| and
 |pdflatex| are special: They directly produce a |.pdf|-file without
 the intermediate |.dvi|-stage. However, from the programmer's point of
-view they behave exactly as if there where an intermediate stage.
+view they behave exactly as if there was an intermediate stage.
 
 Normally, \TeX\ only produces letter--coordinate pairs as its
 ``output.'' This obviously makes it difficult to draw, say, a
@@ -444,7 +445,7 @@ \subsubsection{Producing Perfectly Portable DVI Output}
   \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
+    horizontal or vertical, they are composed of hundreds of small
     rectangles.
   \item Lines of different width are supported.
   \item Transformations are supported.

doc/generic/pgf/text-en/pgfmanual-en-guidelines.tex

@@ -716,7 +716,7 @@ \subsection{Attention and Distraction}
   horizontal and vertical lines or just dots are almost always
   distracting and, usually, serve no real purpose.
 \item
-  Background images and shadings distract and only seldom add
+  Background images and shadings distract and only seldomly add
   anything of importance to a graphic.
 \item
   Cute little clip arts can easily draw attention away from the

doc/generic/pgf/text-en/pgfmanual-en-installation.tex

@@ -11,7 +11,7 @@ \section{Installation}
 
 There are different ways of installing \pgfname, depending
 on your system and needs, and you may need to install other
-packages as well as, see below. Before installing, you may wish to
+packages as well, see below. Before installing, you may wish to
 review the licenses under which the package is
 distributed, see Section~\ref{section-license}.
 
@@ -41,12 +41,12 @@ \subsection{Package and Driver Versions}
 \item
   |dvips| version 5.94a or higher. Earlier versions may also work.
 
-  For inter-picture connections, you need process pictures using
+  For inter-picture connections, you need to process pictures using
   |pdftex| version 1.40 or higher running in DVI mode.
 \item
   |dvipdfm| version 0.13.2c or higher. Earlier versions may also work.
 
-  For inter-picture connections, you need process pictures using
+  For inter-picture connections, you need to process pictures using
   |pdftex| version 1.40 or higher running in DVI mode.
 \item
   |tex4ht| version 2003-05-05 or higher. Earlier versions may also work.
@@ -187,6 +187,6 @@ \subsection{Updating the Installation}
 |pgf| was installed, if you chose a \textsc{tds}-compliant
 installation). The easiest way to do this is to first delete the old
 version and then proceed as described above. Sometimes, there are
-changes in the syntax of certain command from version to version. If
+changes in the syntax of certain commands from version to version. If
 things no longer work that used to work, you may wish to have a look
 at the release notes and at the change log.

doc/generic/pgf/text-en/pgfmanual-en-introduction.tex

@@ -66,7 +66,7 @@ \subsection{Structure of the System}
   command |\pgfpathcircle| that generates the necessary curve
   coordinates for you.
 
-  The basic layer is consists of a \emph{core}, which consists of
+  The basic layer consists of a \emph{core}, which consists of
   several interdependent packages that can only be loaded \emph{en
     bloc,} and additional \emph{modules} that extend the core by more
   special-purpose commands like node management or a plotting
@@ -172,7 +172,7 @@ \subsection{Comparison with Other Graphics Packages}
 \item
   The |xfig| program is an important alternative to \tikzname\ for
   users who do not wish to ``program'' their graphics as is necessary
-  with \tikzname\ and the other packages above. Their is a conversion
+  with \tikzname\ and the other packages above. There is a conversion
   program that will convert |xfig| graphics to both \tikzname\ and
   for \pgfname, but it is still under construction.
 \end{enumerate}