pst-node (4feb14)

git-svn-id: svn://tug.org/texlive/trunk@32891 c570f23f-e606-0410-a88d-b1316a301751

3 files changed, 31 insertions, 27 deletions

diff --git a/Master/texmf-dist/doc/generic/pst-node/Changes b/Master/texmf-dist/doc/generic/pst-node/Changes
index ee5be9abfb3..bb7e2739a24 100644
--- a/Master/texmf-dist/doc/generic/pst-node/Changes
+++ b/Master/texmf-dist/doc/generic/pst-node/Changes
@@ -1,4 +1,6 @@
 ----- pst-node.tex
+1.32  2014-02-03 - fixed bug in \pst@newnode for savedCoors 
+1.31  2014-01-04 - added \dotnodes, plural of \dotnode 
 1.30  2013-09-17 - use \expandafter with \nodexn for the first argument 
 1.29  2013-07-13 - fix bug with missing angle in special node 
                    coordinates
@@ -45,6 +47,7 @@
 
 
 ----- pst-node.pro
+1.15  2014-01-27 - comment out empty lines
 1.14  2012-09-18 - add subroutines for global dict
 1.13  2011-11-21 - fix bug for xelatex and scaling
 1.12  2010-04-30 - small changes to the code
diff --git a/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.pdf b/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.pdf
index 81b855418b8..128d7d6a51a 100644
--- a/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.pdf
+++ b/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.pdf
diff --git a/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.tex b/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.tex
index a7a55b17fdd..5fa262a3adc 100644
--- a/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.tex
+++ b/Master/texmf-dist/doc/generic/pst-node/pst-node-doc.tex
@@ -1,4 +1,4 @@
-%% $Id: pst-node-doc.tex 806 2013-07-13 10:48:09Z herbert $
+%% $Id: pst-node-doc.tex 876 2014-01-28 15:03:13Z herbert $
 \documentclass[11pt,english,BCOR10mm,DIV12,bibliography=totoc,parskip=false,smallheadings
     headexclude,footexclude,oneside]{pst-doc}
 \listfiles
@@ -325,10 +325,11 @@ ellipse. Here is an example with \Lcs{circlenode} and \Lcs{ovalnode}:
 \end{LTXexample}
 
 \begin{BDef}
-\LcsStar{dotnode}\OptArgs\Largr{\CAny}\Largb{name}
+\LcsStar{dotnode}\OptArgs\Largr{\CAny}\Largb{name}\\
+\LcsStar{dotnodes}\OptArgs\Largr{\CAny}\Largb{name}\Largr{\CAny}\Largb{name}\ldots
 \end{BDef}
 
-  This is a variant of \Lcs{psdot}. For example:
+This is a variant of \Lcs{psdot}. For example:
 \begin{LTXexample}
 \begin{pspicture}(3,2)
   \dotnode[dotstyle=triangle*,dotscale=2 1](0,0){A}
@@ -650,7 +651,7 @@ other at right angles, and then join arm B. For example:
   \rnode{a}{\psframebox{\Huge A loop}}
   \ncloop[angleB=180,loopsize=1,arm=.5,linearc=.2]{->}{a}{a}
   \ncput[npos=3.5,nrot=:U]{\psline{|<->|}(.5,-.2)(-.5,-.2)}
-  \nbput[npos=3.5,nrot=:D,labelsep=.35cm]{{\tt loopsize}}
+  \nbput[npos=3.5,nrot=:D,labelsep=.35cm]{{\ttfamily loopsize}}
   \kern .5cm
 \end{LTXexample}
 
@@ -2096,8 +2097,8 @@ For example,
 \begin{verbatim}
 \normalvec(P){P}\normalvec(2;30){Q}
 \end{verbatim}
-first redefines the node {\tt P} as a node whose vector interpretation is of the same 
-length as the original {\tt P}, but rotated 90 degrees. The second instance has the 
+first redefines the node \texttt{P} as a node whose vector interpretation is of the same 
+length as the original \texttt{P}, but rotated 90 degrees. The second instance has the 
 same effect as \Lcs{pnode}\verb|(2;120){Q}|.
 \begin{BDef}
 \Lcs{curvepnode}\Largb{tval}\Largb{expression in t}\Largb{nodename}
@@ -2107,9 +2108,9 @@ For example,
 \begin{verbatim}
 \curvepnode{1}{cos(t) | sin(t)}{P}
 \end{verbatim}
- sets a node named {\tt P} at \verb|(cos(1), sin(1))| and a node named {\tt Ptang} 
- which represents a unit vector in the tangent direction to the curve at {\tt P}. 
- The expression in {\tt t} in this case is algebraic, which is detected automatically by the macro.
+ sets a node named \texttt{P} at \verb|(cos(1), sin(1))| and a node named \texttt{Ptang} 
+ which represents a unit vector in the tangent direction to the curve at \texttt{P}. 
+ The expression in \texttt{t} in this case is algebraic, which is detected automatically by the macro.
 
 \begin{LTXexample}[width=.35\textwidth]
 \begin{pspicture}[showgrid=true](-.5,-.5)(2.5,2)
@@ -2141,8 +2142,8 @@ For example,
 \begin{verbatim}
 \curvepnodes[plotpoints=100]{0}{1}{t+t^2 | Ex(-t)}{P}
 \end{verbatim}
- sets nodes {\tt P0 .. P99} at equally spaced {\tt t} values along the curve, 
- and assigns the macro \Lcs{Pnodecount} to 99, the highest index. The expression in {\tt t} 
+ sets nodes \texttt{P0 .. P99} at equally spaced \texttt{t} values along the curve, 
+ and assigns the macro \Lcs{Pnodecount} to 99, the highest index. The expression in \texttt{t} 
  may be either algebraic or PostScript, and is handled automatically. The values 
  \verb|<tmin>, <tmax>| may be expressed using PostScript---eg, \verb|{Pi neg}{PiDiv2}|.
  
@@ -2173,7 +2174,7 @@ For example,
 \pnode(!/x 0.5 def x x x 1 add mul 2 div}){P}
 \end{verbatim}
 
- If your expression in {\tt t} is algebraic, you must specify the keyword {\tt algebraic}, as in 
+ If your expression in \texttt{t} is algebraic, you must specify the keyword \texttt{algebraic}, as in 
  \Lcs{fnpnode}\verb|[algebraic]{0.5}{x*(x+1)/2}{P}|. 
  
 \begin{LTXexample}[width=.35\textwidth]
@@ -2305,8 +2306,8 @@ is similar to \Lcs{psRelNode}, and provides a means of scaling and rotating  a l
 \end{verbatim}
  but the third argument (2;30) may be specified in any form acceptable to \Lcs{SpecialCoor}, 
  while specifying the angle argument in \Lcs{psRelNode} using PostScript is not possible. 
- Note that  \Lcs{psRelNodeVar}\verb|(0,0)(A)(B){C}|  may be interpreted as defining {\tt C} to 
- be the complex product of {\tt A} and {\tt B}. 
+ Note that  \Lcs{psRelNodeVar}\verb|(0,0)(A)(B){C}|  may be interpreted as defining \texttt{C} to 
+ be the complex product of \texttt{A} and \texttt{B}. 
 
 
 \begin{LTXexample}[width=5cm]
@@ -2325,7 +2326,7 @@ is similar to \Lcs{psRelNode}, and provides a means of scaling and rotating  a l
 \end{BDef}
  stands to \Lcs{psRelLine} as \Lcs{psRelNodeVar} stands relative to \Lcs{psRelNode}. 
  
-\Lcs{psRelLine}\verb|Var(A)(B)(a;b){C}| defines the node {\tt C}, and, in addition, draws the line segment {\tt AC}. 
+\Lcs{psRelLine}\verb|Var(A)(B)(a;b){C}| defines the node \texttt{C}, and, in addition, draws the line segment \texttt{AC}. 
 
 \begin{BDef}
 \Lcs{rhombus}\Largb{edge length}\Largr{A}\Largb{B}\Largb{C}\Largb{D}
@@ -2352,7 +2353,7 @@ could be handled easily by \Lcs{psline}. Internally, \Lcs{rhombus} uses
 \begin{BDef}
 \Lcs{psxline}\Largr{basept}\Largb{nodexpr1}\Largb{nodexpr2}
 \end{BDef}
-The {\tt x} here stands for expression. The idea is that one builds a 
+The \texttt{x} here stands for expression. The idea is that one builds a 
 line from \verb|<basept>+<nodexpr1>| to \verb|<basept>+<nodexpr2>|.
 
 \begin{LTXexample}[width=.35\textwidth]
@@ -2382,17 +2383,17 @@ is the most complicated macro in the collection. It has two forms.
 \end{verbatim}
 
 defines the polyline \verb|L=(1,2)(3;30)(6,5)...|, and computes the two points of 
-intersection closest to {\tt A} in each direction with the directed line starting at 
+intersection closest to \texttt{A} in each direction with the directed line starting at 
 A heading toward B. The first intersection point in the positive direction is named 
 \verb|<Name1>|, and the first intersection point in the opposite direction (from A) 
 is named \verb|<Name2>|. If one or other of these intersections is empty, the nodes are 
-set to remote points on the line {\tt AB}.  The effect of the line joining the constructed 
-nodes depends on the location of {\tt A} and {\tt B} relative to {\tt L}, with two cases worth noting.
+set to remote points on the line \texttt{AB}.  The effect of the line joining the constructed 
+nodes depends on the location of \texttt{A} and \texttt{B} relative to \texttt{L}, with two cases worth noting.
 \begin{itemize}
-\item if {\tt L} is closed and if {\tt A, B} are interior to one of its components, the 
-resulting line extends across that component of {\tt L}, and contains {\tt AB}.
-\item If {\tt L} is simple and closed, one of {\tt A, B} is inside and the other outside, 
-the resulting line segment will contain {\tt A} but not {\tt B}. 
+\item if \texttt{L} is closed and if \texttt{A, B} are interior to one of its components, the 
+resulting line extends across that component of \texttt{L}, and contains \texttt{AB}.
+\item If \texttt{L} is simple and closed, one of \texttt{A, B} is inside and the other outside, 
+the resulting line segment will contain \texttt{A} but not \texttt{B}. 
 \end{itemize}
 
 \begin{verbatim}
@@ -2505,8 +2506,8 @@ assuming \verb|P0...Pn| to be previously defined nodes.
 takes as inputs the root name of the node sequence, the index at which the arrow 
 tip is to be drawn, and the direction (one of \verb+>,<+) of the arrow. It then 
 constructs the notch as a node with name \verb|<Notch>|. The arrowhead may then be 
-drawn with a command like \Lcs{psline}\verb|{->}(N)(P3)|, assuming the tip was to be {\tt P3} 
-and the notch was {\tt N}. Keep in mind that the macro takes its settings for linewidth, 
+drawn with a command like \Lcs{psline}\verb|{->}(N)(P3)|, assuming the tip was to be \texttt{P3} 
+and the notch was \texttt{N}. Keep in mind that the macro takes its settings for linewidth, 
 arrowscale, etc from the current values, so it is generally preferable to include them 
 in a \Lcs{psset} before drawing the curve and calling \Lcs{ArrowNotch}. 
 (Alternatively, they may be included as optional settings in \Lcs{ArrowNotch}.)
@@ -2515,10 +2516,10 @@ good. The second shows how to make a version using \Lcs{ArrowNotch}. Notice that
 parameter values in the second example had to be modified to keep the curve 
 from protruding near the end arrowheads.
 
-\Lcs{ArrowNotch} is a computationally expensive macro (quadratic in {\tt plotpoints}) designed to 
+\Lcs{ArrowNotch} is a computationally expensive macro (quadratic in \texttt{plotpoints}) designed to 
 improve the placement of arrows on curves in those cases (high curvature, large values of 
 linewidth, arrowscale, etc) where the native arrow direction is not optimal. The macro 
-depends on the construction of a node sequence, say {\tt P0..Pn}, of samples of the curve 
+depends on the construction of a node sequence, say \texttt{P0..Pn}, of samples of the curve 
 (eg, with \Lcs{curvepnodes}) from which it computes the position of the notch of the arrow 
 so that, when drawn, the arrow notch will be located on the curve in all cases. It operates 
 with only two particular arrow shapes---those arrows specified with either