add pstricks config subdir

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

7 files changed, 1125 insertions, 0 deletions

diff --git a/Master/texmf-dist/tex/generic/pstricks/config/README b/Master/texmf-dist/tex/generic/pstricks/config/README
new file mode 100644
index 00000000000..3814ed7302c
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/README
@@ -0,0 +1,45 @@
+This directory contains the special PSTricks config files for
+the different platforms. By default the dvips config file is
+already in your current TeX distribution as pstricks.con.
+If you use another platform then you have to replace the current
+pstricks.con by one of the following cfg files:
+
+- PostScript header files
+
+-- If you use the Y&Y's "dvipsone" DVI to PostScript converter,
+you have to rename config.cfg to generic/pstricks.con and to move
+all the files of the "dvips" subdirectory to the TeX input folder.
+
+-- If you use the MicroPress "VTeX" DVI to PostScript converter,
+you have to rename config/vtex.cfg to generic/pstricks.con and to move
+all the files of the "dvips" subdirectory to the TeX input folder.
+
+-- If you use XeTeX, you have to rename config/xdvipdfmx.cfg to 
+   generic/pstricks.con
+
+-- If you use the "textures" (version 1.7/1.8 or 2.0) DVI to PostScript
+   converter (for Macintosh), you should proceed as follows:
+          * create a new folder PSTricks (for instance) as a subfolder in
+            Textures' TeX inputs folder,
+          * copy the "generic", "dvips", "latex" and "contrib" subfolders
+            from the "pstricks" folder to the newly created "PSTricks" folder,
+          * open the "generic" folder and remove the file pstricks.con,
+            then rename the file textures.cfg to pstricks.con,
+          * open the "dvips" folder and change the following line in the file
+            pstricks.pro (courtesy Michael J. Sharpe <msharpe@euclid.ucsd.edu>):
+            /STV { SDict begin normalscale end STP  } def
+            by
+            /STV { Mag 72.27 72 div mul dup neg scale STP  } def
+            It was also reported that the `pst-text' package (to put text
+            along paths) doesn't work with the "textures" driver.
+            Textures's users must also look at the page kindly maintained
+            by Michael Sharpe: http://math.ucsd.edu/~msharpe/pst-textures.html
+
+-- If you use another driver than these four ones, you have to adapt
+a pstricks.con file for it, if the one for "dvips" doesn't work for it.
+You can also look at the instructions of the old obsolete/src/pstricks.con
+file. And if nothing work, ask for help on the PSTricks mailing list,
+hopping that somebody on the list has the same configuration than you ...
+
+--
+2010-01-22 hv
\ No newline at end of file
diff --git a/Master/texmf-dist/tex/generic/pstricks/config/distiller.cfg b/Master/texmf-dist/tex/generic/pstricks/config/distiller.cfg
new file mode 100644
index 00000000000..b44c2fb27bc
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/distiller.cfg
@@ -0,0 +1,62 @@
+%% BEGIN: distiller.con (for distiller driver)
+%%
+%% Configuration file for PSTricks
+%%
+%% Version 0.01 (2008/01/24)
+%%
+%% For use with Adobes Distiller (tested with v7.0.7)
+%%
+%% COPYRIGHT 2008 by Herbert Voss, hvoss@tug.org.
+%%
+%% 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.
+%
+\def\pstdriver{distiller}
+{\catcode`\"=12\gdef\pstverb#1{\special{" #1}}}  % Check catcode of "
+\def\pstunit{1bp}%
+\def\pstVerb#1{\special{ps: #1}}
+\def\pstverbscale{SDict begin normalscale end}
+\ifx\textsuperscript\@undefined
+   \def\pstheader#1{\special{header=#1}}
+\else
+  \ifx\Gin@PS@file@header\@undefined
+    \def\pstheader#1{\AtBeginDvi{\special{header=#1}}}
+  \else
+    \let\pstheader\Gin@PS@file@header
+  \fi
+\fi
+%% In the following, CP is short for currentpoint.
+%% The neg is necessary because dvips scales the coordinates by 1 -1.
+%% \tx@NET means neg exch neg exch translate.
+\def\pstrotate{CP CP translate 3 -1 roll neg rotate \tx@NET}
+%
+\pst@def{setTransparency}<
+ [ /BM/Normal 
+   /ca \psk@opacityalpha 
+   /CA \psk@opacityalpha /SetTransparency pdfmark >
+\pst@def{setStrokeTransparency}<
+ [ /BM/Normal 
+   /ca \psk@strokeopacityalpha 
+   /CA \psk@strokeopacityalpha /SetTransparency pdfmark >
+\pst@def{setBlendmode}<
+  [ /BM\ifcase\psk@blendmode%
+      /Normal \or
+      /Compatible %\or
+     \else /Normal
+      /Screen \or
+      /Multiply %\or
+%      /Hardlight
+    \fi/ca \psk@shapealpha /CA \psk@opacityalpha /SetTransparency pdfmark >
+%%
+%% ****************** END distiller.con *****************************
+
+%%%%%%%%%%%%%%%%%%% !! CUSTOMIZATION STUFF GOES HERE: !! %%%%%%%%%%%%%%%%%%
+%% If you want to include your own customizations to pstricks.tex, then
+%% uncomment the \pstcustomize command, and include your modifications
+%% after \pstcustomize. These will be read in after pstricks.tex.
+%\pstcustomize
+%
+\endinput
+%%
+%% END: distiller.con
diff --git a/Master/texmf-dist/tex/generic/pstricks/config/dvips.cfg b/Master/texmf-dist/tex/generic/pstricks/config/dvips.cfg
new file mode 100644
index 00000000000..08f7a66be78
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/dvips.cfg
@@ -0,0 +1,358 @@
+%% BEGIN: pstricks.con (for dvips driver)
+%%
+%% Configuration file for PSTricks
+%%
+%% Version 1.00 (2010/01/16)
+%%
+%% For use with Rokicki's dvips (tested with v5.74 and older)
+
+\def\pstdriver{Rokicki's dvips}
+{\catcode`\"=12\gdef\pstverb#1{\special{" #1}}}  % Check catcode of "
+\def\pstunit{1bp}%
+\def\pstVerb#1{\special{ps:#1}}% hv write it without a preceding space
+\def\pstverbscale{SDict begin normalscale end}
+% DG/SR modification begin  - Apr. 28, 1997 (D. Carlisle + S. Rahtz)
+% \def\pstheader#1{\special{header=#1}}
+% We used to check for |\AtBeginDvi|, but that was broken in early release
+% so we now check for the existence of |\textsuperscript| (added 1995/05/16)
+\ifx\textsuperscript\@undefined
+   \def\pstheader#1{\special{header=#1}}
+\else
+  \ifx\Gin@PS@file@header\@undefined
+    \def\pstheader#1{\AtBeginDvi{\special{header=#1}}}
+  \else
+    \let\pstheader\Gin@PS@file@header
+  \fi
+\fi
+% DG/SR modification end
+%%
+%% In the following, CP is short for currentpoint.
+%% The neg is necessary because dvips scales the coordinates by 1 -1.
+%% \tx@NET means neg exch neg exch translate.
+\def\pstrotate{CP CP translate 3 -1 roll neg rotate \tx@NET}
+%%
+%% ****************** END Rokicki's dvips *****************************
+
+%%%%%%%%%%%%%%%%%%% !! CUSTOMIZATION STUFF GOES HERE: !! %%%%%%%%%%%%%%%%%%
+%% If you want to include your own customizations to pstricks.tex, then
+%% uncomment the \pstcustomize command, and include your modifications
+%% after \pstcustomize. These will be read in after pstricks.tex.
+%\pstcustomize
+
+\endinput
+
+%%
+%%%%%%%%%%%%%%%%%%% !! GENERAL INSTRUCTIONS !! %%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+Because there are no standards for dvi-to-PS driver \special's,
+some driver-dependent commands must be defined in this file.
+
+Possibly correct definitions for some dvi drivers are given below.
+Copy the section for the driver you want to use to the indicated place
+near the beginning of the file, replacing any other definitions you
+might find there.
+
+When changing drivers, you may need to remake the header file.
+
+See the PSTricks read-me file for further installation instructions.
+
+Please report good and bad experiences with dvi-to-PS drivers,
+along with the definitions of these commands that worked
+for you, to tvz@Princeton.EDU.  Thanks.
+
+
+%%%%%%%%%%%%%%%% DESCRIPTION OF CONFIGURATION DEFINITIONS %%%%%%%%%%%%%%%
+
+Here are the commands that must be defined in this file:
+
+   \pstverb{}    -  The argument is included as verbatim PostScript,
+                    grouped by save and restore. The coordinate system
+	should be square, not rotated, and with the origin
+	at TeX's currentpoint.
+
+   \pstVerb{}    -  The argument is included as verbatim PostScript, not
+                    grouped by (g)save and (g)restore. The currentpoint
+	should be TeX's currentpoint.
+
+   \pstunit      -  The units used by driver for graphics included with
+                    \pstverb. Probably 1bp or 1sp.
+
+   \pstverbscale - The PostScript code that scales the coordinate system
+                   from that in effect with \pstVerb to that in effect
+                   with \pstverb. Should not translate to the currentpoint.
+
+   \pstrotate    - The PostScript code that takes a number off the stack
+                   and rotates the axes properly. I.e.,
+                   \pstVerb{angle \pstrotate} is used to begin rotations.
+
+   \pstheader{}  - The argument is a header file (e.g., .pro file).
+                   If your driver does not support such a special, then
+                   the command might just remind you to include the header
+                   when printing. You can use PSTricks without a header,
+                   in which case it does not matter how you define
+                   \pstheader. See read-me.pst for details.
+                   If you cannot change the default directory where your
+                   driver looks for header files, and you cannot write to
+                   that directory, then you include the path for your
+                   PSTricks header files.
+                   E.g., \def\pstheader#1{\special{header=~/tex/#1}}.
+
+   \pstdriver    - The name of the driver.
+
+
+%%%%%%%%% !! HOW TO MAKE A TEX FORMAT WITH PSTRICKS PRELOADED !! %%%%%%%%
+
+See your local TeX documentation for instructions on creating a TeX format.
+
+Before making the format, be sure that this configuration file is correct.
+It will be read only when creating the format, and not with every job.
+
+If you are not using header files, there are no more special instructions.
+
+Special instructions when using header files:
+
+ - If you want to include supplementary PSTricks files (e.g., pst-node.tex),
+   add \input commands in the customization section above.
+
+ - If your definition of \pstheader is, e.g.
+
+     \def\pstheader#1{\special{\header=#1}}
+
+   then change it to
+
+     \def\pstheader#1{%
+       \expandafter\everyjob\expandafter{\the\everyjob
+         \special{header=#1}}}
+
+   and put your original definition in the customization section, AFTER
+   any \input commands. E.g., the customization section might look like:
+
+     \pstcustomize
+     \input pst-node.tex
+     \input pst-coil.tex
+     \def\pstheader#1{\special{header=#1}}
+
+ - Input pstricks.tex at the appropriate time when creating the format.
+   E.g., when initex stops running:
+     *\input pstricks
+     *\dump
+
+
+%%%%%%%%%% !! CONFIGURATIONS FOR SOME DRIVERS !! %%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%% **********************************************************************
+%% ***** Rokicki's dvips ***** Rokicki's dvips ***** Rokicki's dvips ****
+%% **********************************************************************
+%% Life is bliss with Rokicki's dvips (tested with v5.396, v5.47, 5.491):
+%%
+\def\pstdriver{Rokicki's dvips}
+{\catcode`\"=12\gdef\pstverb#1{\special{" #1}}}  % Check catcode of "
+\def\pstunit{1bp}%
+\def\pstVerb#1{\special{ps: #1}}
+\def\pstverbscale{SDict begin normalscale end}
+\def\pstheader#1{\special{header=#1}}
+%%
+%% In the following, CP is short for currentpoint.
+%% The neg is necessary because dvips scales the coordinates by 1 -1.
+%% \tx@NET means neg exch neg exch translate.
+\def\pstrotate{%
+  CP CP translate 3 -1 roll neg rotate \tx@NET}
+%%
+%% If using a version before 5.47, clipping may not work. You can
+%% try the following definition of \pstverb:
+%\def\pstverb#1{\special{ps: @beginspecial #1 @endspecial}}
+%% or change "{initclip}ifelse" to "if" in the definition of @setspecial
+%% in dvips' special.pro.
+%%
+%% ****************** END Rokicki's dvips *****************************
+
+
+%% **********************************************************************
+%% **** Arbortext's dvips *** Arbortext's dvips *** Arbortext's dvips ***
+%% **********************************************************************
+%% Thanks to Wolfgang Sienel:
+%%
+\def\pstdriver{Arbortext's dvips}
+\def\pstverb#1{%
+  \special{ps::[asis] 0 SPB /ChartCheckPoint save def
+  Xpos Ypos translate #1 ChartCheckPoint restore 0 SPE}}
+\def\pstunit{1bp}
+\def\pstVerb#1{\special{ps:: #1}}
+\def\pstverbscale{}
+\def\pstrotate{CP CP translate 3 -1 roll rotate \tx@NET}
+\def\pstheader#1{%
+  \typeout{**********************************************************}%
+  \typeout{** Don't forget to include #1 when printing:}%
+  \typeout{** \space\space dvips -PRO #1 myfile}%
+  \typeout{**********************************************************}}
+%%
+%% Comments by Wolfgang on header files:
+%%  Normally the  standard prolog file is  downloaded once to the printer
+%%  with psload.ps (the initializing  file for your  TeX-printer)  before
+%%  printing  TeX-documents.  If you don't  make any changes to psload.ps
+%%  you  have  to type  dvips -PRO PATH/pstricks.pro myfile   (-PRO  just
+%%  works for  UNIX systems.  I don't have any idea about other systems).
+%%  If psload.ps  was not  downloaded to the  printer  you have to append
+%%  pstricks.pro  to  the standard  prolog  file dvips.pro.  In this case
+%%  invoke  dvips as always.   Note that after hitting  the enter key you
+%%  have to specify the option download all prolog in both cases.  If you
+%%  are frequently using pstricks you might want to change psload.ps.  In
+%%  this case contact your local TeX-guru and ask him politely to do this
+%%  for you. Attention: If psload.ps is getting too big you may run  into
+%%  trouble with printer memory!
+%%
+%% ****************** END Arbortext's dvips *****************************
+
+
+%% **********************************************************************
+%% **** Textures *** Textures *** Textures *** Textures *** Textures ****
+%% **********************************************************************
+%% These have been tested with v1.3. It is nice to have a PostScript
+%% screen previewer, such as TScript (USA: 1-617-734-9700). (The
+%% Textures preview window will not show the PSTricks graphics.)
+%%
+\def\pstdriver{Textures}
+\def\pstunit{1bp}
+\def\pstverb#1{\special{postscript /TX@Save save def #1 TX@save restore}}
+\def\pstVerb#1{\special{postscript grestore #1 gsave}}
+\def\pstverbscale{Mag 1000 div 72.27 72 div mul dup neg scale}
+\def\pstrotate{%
+  CP CP translate 3 -1 roll neg rotate \tx@NET}
+%%
+%% \pstVerb does not define the currentpoint properly. As a workaround,
+%% insert the following lines in the customization section above.
+%%
+%%   \def\pst@Verb#1{%
+%%     \special{postscript \pst@dict /sps { moveto /Mag ed } def
+%%       userdict begin}%
+%%     \special{postscript #1 end gsave}}
+%%
+%% Textures does not support header files.
+%% However, it may still be worth using a header file for increased speed.
+%% Also, some macros can overload Textures 1.3 when not used with a header
+%% file. You can include the header file pstricks.pro by saving the
+%% PostScript output to a file and inserting the pstricks.pro with an
+%% editor. Probably a better solution is to append pstricks.pro to a
+%% copy of the laserprep, and, by changing file names of the modified
+%% laserprep and the original laserprep, use the laserprep with pstricks.pro
+%% whenever you are printing pstricks documents.
+\def\pstheader#1{%
+  \typeout{******************************************}%
+  \typeout{*** Include header file #1!! ***}%
+  \typeout{******************************************}}
+%%
+%% ****************** END Textures **************************************
+
+
+%% **********************************************************************
+%% ***** dvi2ps ***** dvi2ps ***** dvi2ps ***** dvi2ps ***** dvi2ps *****
+%% **********************************************************************
+%% I.e., dvi2ps, v2.xx. There are lot's of such things around.
+%% This probably doesn't work. Considering upgrading to Rokicki's dvips.
+%%
+\def\pstdriver{dvi2ps v2.xx}
+\def\pstunit{1pt}
+\def\pstverb#1{ pstext="save currentpoint translate
+  Resolution 72.27 div neg scale #1 restore" \space}
+\def\pstVerb#1{ pstext="#1" \space}
+\def\pstverbscale{Resolution 72.27 div neg scale}
+\def\pstrotate{%
+  CP CP translate 3 -1 roll neg rotate \tx@NET}
+\def\pstheader#1{%
+  \typeout{******************************************************}
+  \typeout{Don't forget to include the header file #1!!}
+  \typeout{******************************************************}
+%%
+%% ***************************** END dvi2ps *****************************
+
+
+%% **********************************************************************
+%% ***** dvi3ps ***** dvi3ps ***** dvi3ps ***** dvi3ps ***** dvi3ps *****
+%% **********************************************************************
+%% I.e., dvi2ps, version 3.xx, by Kevin Coombes.
+%% This has not been tested. Consider upgrading to Rokicki's dvips.
+%%
+\def\pstdriver{dvi2ps v3.xx}
+\def\pstunit{1bp}
+\def\pstverb#1{pstext="#1"}
+% \def\pstVerb#1{%
+%   \special{pstext="@endspecial #1 @beginspecial @setspecial"}}  % v3.0
+\def\pstVerb#1{\special{psraw="#1"}}                            % v3.3
+\def\pstverbscale{Resolution 72.27 div neg scale}
+\def\pstrotate{%
+  CP CP translate 3 -1 roll neg rotate \tx@NET}
+\def\pstheader#1{%
+  \typeout{******************************************************}
+  \typeout{Don't forget to include the header file #1!!}
+  \typeout{******************************************************}
+%%
+%% ******************* END dvi3ps ***************************************
+
+
+%% **********************************************************************
+%% **** OzTeX **** OzTeX **** OzTeX **** OzTeX **** OzTeX **** OzTeX ****
+%% **********************************************************************
+%% Only the pure graphics objects are supported for OzTeX.
+%% No color, rotation, clipping, nodes and node connections, overlays, etc.
+%% Also, \rput cannot be used with \SpecialCoor.
+%%
+%% The reason is given in the documentation for Version 1.3, September 1990:
+%%
+%%   OzTeX generates highly efficient PostScript code but it does so at
+%%   the expense of some \special functionality. Many DVI-to-PostScript
+%%   translators allow you to do things like use one \verb|\special| to start
+%%   rotating TeX text and another to stop the rotation. The way OzTeX
+%%   interprets a DVI page makes this impossible.
+%%
+%% If using the header file, you should copy pstricks.pro to global.ps, in
+%% the same directory as your dvi file.
+%%
+\def\pstdriver{OzTeX}
+\def\pstverb#1{\special{null.ps #1}}
+\def\pstunit{1bp}
+\def\pstVerb#1{%
+  \typeout{PSTRICKS WARNING:}%
+  \typeout{\space\space You are using features not supported by OzTeX.}%
+  \typeout{\space\space These will be ignored.}%
+  \gdef\pstVerb##1{}}
+\def\pstverbscale{}
+\def\pstrotate{}
+\def\pstheader#1{%
+  \typeout{******************************************************}
+  \typeout{Don't forget to include the header file #1!!}
+  \typeout{******************************************************}}
+%%
+%% ************************* END OzTeX **********************************
+
+
+%% **********************************************************************
+%% ***** DirectTeX ***** DirectTeX ***** DirectTeX ***** DirectTeX ******
+%% **********************************************************************
+%% DirectTeX is for the Macintosh. These has been tested unsuccessfully,
+%% apparently due to a problem with DirectTeX.
+%%
+\def\pstdriver{DirectTeX}
+%%
+%% Check catcode of "
+{\catcode`\"=12\gdef\pstverb#1{\special{" #1 /Foo{}def }}}
+\def\pstunit{1bp}
+\def\pstVerb#1{\special{ps: #1 }}
+\def\pstverbscale{TeXDict begin normalscale end}
+%%
+%% In the following, CP is short for currentpoint. The neg is necessary
+%% because dvips scales the coordinates by 1 -1:
+\def\pstrotate{%
+  CP CP translate 3 -1 roll neg rotate \tx@NET}
+%%
+\def\pstheader#1{%
+  \typeout{**********************************************************}%
+  \typeout{** Don't forget to include #1 when printing:}%
+  \typeout{** \space\space DVIReader -header #1 myfile}%
+  \typeout{**********************************************************}}
+%%
+%% ****************** END DirectTeX *****************************
+
+
+%%
+%% END: pstricks.con
diff --git a/Master/texmf-dist/tex/generic/pstricks/config/dvipsone.cfg b/Master/texmf-dist/tex/generic/pstricks/config/dvipsone.cfg
new file mode 100644
index 00000000000..4a90292dd00
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/dvipsone.cfg
@@ -0,0 +1,138 @@
+%% BEGIN pstricks.con (for DVIPSONE driver)
+%%
+%% Configuration file for PSTricks 97: must be renamed `pstricks.con'
+%%
+%% Version 97 (1994/03/29)
+%%
+%% For use with DVIPSONE. (May require the -j flag with dvipsone)
+
+\def\pstdriver{DVIPSONE}
+\def\pstunit{1bp}
+{\catcode`\"=12 \gdef\pstverb#1{\special{" #1}} }
+\def\pstVerb#1{\special{ps:: #1}}
+\def\pstverbscale{1 dviscl div dup neg scale}
+\def\pstrotate{CP CP translate 3 -1 roll neg rotate \tx@NET}
+\def\pstheader#1{\special{header=#1}}
+
+\pstcustomize
+
+\endinput
+
+%% To get PSTricks charpath and textpath to work:
+%----------- pst-show.pro ------------------------------------------
+%!
+% Patch for dvipsone to get PSTricks' charpath and textpath to work.
+% Save as pst-show.pro, put it with your other PSTricks .pro files.
+% Add "\pstheader{pst-show.pro}" to the beginning of your document.
+%
+% We unbind show:
+dvidict begin
+/S {show dup 0 rmoveto} def
+/T {show 2 index 0 rmoveto} def
+/s {show} def
+end
+
+\endinput
+%------------- end pst-show.pro ------------------------------------
+%%
+%%%%%%%%%%%%%%%%%%% !! GENERAL INSTRUCTIONS !! %%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+Because there are no standards for dvi-to-PS driver \special's,
+some driver-dependent commands must be defined in this file.
+
+Possibly correct definitions for some dvi drivers are given below.
+Copy the section for the driver you want to use to the indicated place
+near the beginning of the file, replacing any other definitions you
+might find there.
+
+When changing drivers, you may need to remake the header file.
+
+See the PSTricks read-me file for further installation instructions.
+
+Please report good and bad experiences with dvi-to-PS drivers,
+along with the definitions of these commands that worked
+for you, to tvz@Princeton.EDU.  Thanks.
+
+
+%%%%%%%%%%%%%%%% DESCRIPTION OF CONFIGURATION DEFINITIONS %%%%%%%%%%%%%%%
+
+Here are the commands that must be defined in this file:
+
+   \pstverb{}    -  The argument is included as verbatim PostScript,
+                    grouped by save and restore. The coordinate system
+	should be square, not rotated, and with the origin
+	at TeX's currentpoint.
+
+   \pstVerb{}    -  The argument is included as verbatim PostScript, not
+                    grouped by (g)save and (g)restore. The currentpoint
+	should be TeX's currentpoint.
+
+   \pstunit      -  The units used by driver for graphics included with
+                    \pstverb. Probably 1bp or 1sp.
+
+   \pstverbscale - The PostScript code that scales the coordinate system
+                   from that in effect with \pstVerb to that in effect
+                   with \pstverb. Should not translate to the currentpoint.
+
+   \pstrotate    - The PostScript code that takes a number off the stack
+                   and rotates the axes properly. I.e.,
+                   \pstVerb{angle \pstrotate} is used to begin rotations.
+
+   \pstheader{}  - The argument is a header file (e.g., .pro file).
+                   If your driver does not support such a special, then
+                   the command might just remind you to include the header
+                   when printing. You can use PSTricks without a header,
+                   in which case it does not matter how you define
+                   \pstheader. See read-me.pst for details.
+                   If you cannot change the default directory where your
+                   driver looks for header files, and you cannot write to
+                   that directory, then you include the path for your
+                   PSTricks header files.
+                   E.g., \def\pstheader#1{\special{header=~/tex/#1}}.
+
+   \pstdriver    - The name of the driver.
+
+
+%%%%%%%%% !! HOW TO MAKE A TEX FORMAT WITH PSTRICKS PRELOADED !! %%%%%%%%
+
+See your local TeX documentation for instructions on creating a TeX format.
+
+Before making the format, be sure that this configuration file is correct.
+It will be read only when creating the format, and not with every job.
+
+If you are not using header files, there are no more special instructions.
+
+Special instructions when using header files:
+
+ - If you want to include supplementary PSTricks files (e.g., pst-node.tex),
+   add \input commands in the customization section above.
+
+ - If your definition of \pstheader is, e.g.
+
+     \def\pstheader#1{\special{\header=#1}}
+
+   then change it to
+
+     \def\pstheader#1{%
+       \expandafter\everyjob\expandafter{\the\everyjob
+         \special{header=#1}}}
+
+   and put your original definition in the customization section, AFTER
+   any \input commands. E.g., the customization section might look like:
+
+     \pstcustomize
+     \input pst-node.tex
+     \input pst-coil.tex
+     \def\pstheader#1{\special{header=#1}}
+
+ - Input pstricks.tex at the appropriate time when creating the format.
+   E.g., when initex stops running:
+     *\input pstricks
+     *\dump
+
+
+%%
+%% END: pstricks.con
+
+%%
+%% END: dvipsone.con
diff --git a/Master/texmf-dist/tex/generic/pstricks/config/textures.cfg b/Master/texmf-dist/tex/generic/pstricks/config/textures.cfg
new file mode 100644
index 00000000000..b126464a767
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/textures.cfg
@@ -0,0 +1,127 @@
+%% BEGIN pstricks.con (for Textures 1.7 and 1.8 driver)
+%%
+%% Configuration file for PSTricks 97: must be renamed `pstricks.con'
+%%
+%% Version 97 (1997/03/01)
+%%
+%% For use with Textures, v1.7 and v1.8.
+
+\def\pstdriver{Textures-V1.7}
+%\def\pstdriver{Textures-V1.8}
+\def\pstunit{1bp}
+\def\pstverb#1{\special{postscript #1 }}
+\def\pstVerb#1{\special{rawpostscript #1}}
+\def\pstverbscale{Mag 72.27 72 div mul dup neg scale}
+\def\pstrotate{CP CP translate 3 -1 roll neg rotate \tx@NET}
+\def\pstheader#1{\special{prePostScriptfile #1}}%
+
+\pstcustomize
+
+\special{prePostScript
+  tx@Dict begin /sps {moveto /Mag ED pop tx@Dict begin} def /eps {} def end}
+\def\pst@Verb#1{%
+  \special{rawpostscript tx@Dict begin}%
+  \special{postscript #1}%
+  \special{rawpostscript end}}
+
+\endinput
+
+%%
+%%%%%%%%%%%%%%%%%%% !! GENERAL INSTRUCTIONS !! %%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+Because there are no standards for dvi-to-PS driver \special's,
+some driver-dependent commands must be defined in this file.
+
+Possibly correct definitions for some dvi drivers are given below.
+Copy the section for the driver you want to use to the indicated place
+near the beginning of the file, replacing any other definitions you
+might find there.
+
+When changing drivers, you may need to remake the header file.
+
+See the PSTricks read-me file for further installation instructions.
+
+Please report good and bad experiences with dvi-to-PS drivers,
+along with the definitions of these commands that worked
+for you, to tvz@Princeton.EDU.  Thanks.
+
+
+%%%%%%%%%%%%%%%% DESCRIPTION OF CONFIGURATION DEFINITIONS %%%%%%%%%%%%%%%
+
+Here are the commands that must be defined in this file:
+
+   \pstverb{}    -  The argument is included as verbatim PostScript,
+                    grouped by save and restore. The coordinate system
+	should be square, not rotated, and with the origin
+	at TeX's currentpoint.
+
+   \pstVerb{}    -  The argument is included as verbatim PostScript, not
+                    grouped by (g)save and (g)restore. The currentpoint
+	should be TeX's currentpoint.
+
+   \pstunit      -  The units used by driver for graphics included with
+                    \pstverb. Probably 1bp or 1sp.
+
+   \pstverbscale - The PostScript code that scales the coordinate system
+                   from that in effect with \pstVerb to that in effect
+                   with \pstverb. Should not translate to the currentpoint.
+
+   \pstrotate    - The PostScript code that takes a number off the stack
+                   and rotates the axes properly. I.e.,
+                   \pstVerb{angle \pstrotate} is used to begin rotations.
+
+   \pstheader{}  - The argument is a header file (e.g., .pro file).
+                   If your driver does not support such a special, then
+                   the command might just remind you to include the header
+                   when printing. You can use PSTricks without a header,
+                   in which case it does not matter how you define
+                   \pstheader. See read-me.pst for details.
+                   If you cannot change the default directory where your
+                   driver looks for header files, and you cannot write to
+                   that directory, then you include the path for your
+                   PSTricks header files.
+                   E.g., \def\pstheader#1{\special{header=~/tex/#1}}.
+
+   \pstdriver    - The name of the driver.
+
+
+%%%%%%%%% !! HOW TO MAKE A TEX FORMAT WITH PSTRICKS PRELOADED !! %%%%%%%%
+
+See your local TeX documentation for instructions on creating a TeX format.
+
+Before making the format, be sure that this configuration file is correct.
+It will be read only when creating the format, and not with every job.
+
+If you are not using header files, there are no more special instructions.
+
+Special instructions when using header files:
+
+ - If you want to include supplementary PSTricks files (e.g., pst-node.tex),
+   add \input commands in the customization section above.
+
+ - If your definition of \pstheader is, e.g.
+
+     \def\pstheader#1{\special{\header=#1}}
+
+   then change it to
+
+     \def\pstheader#1{%
+       \expandafter\everyjob\expandafter{\the\everyjob
+         \special{header=#1}}}
+
+   and put your original definition in the customization section, AFTER
+   any \input commands. E.g., the customization section might look like:
+
+     \pstcustomize
+     \input pst-node.tex
+     \input pst-coil.tex
+     \def\pstheader#1{\special{header=#1}}
+
+ - Input pstricks.tex at the appropriate time when creating the format.
+   E.g., when initex stops running:
+     *\input pstricks
+     *\dump
+
+
+%%
+%% END: pstricks.con
diff --git a/Master/texmf-dist/tex/generic/pstricks/config/vtex.cfg b/Master/texmf-dist/tex/generic/pstricks/config/vtex.cfg
new file mode 100644
index 00000000000..9f20fec6bb3
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/vtex.cfg
@@ -0,0 +1,170 @@
+%% BEGIN: pstricks.con (for VTeX)
+%%
+%% Configuration file for PSTricks 97
+%%
+%% Version 97 patch 5 2003-04-29
+%%
+%% For use with VTeX PostScript driver v 6.61+
+%% [MV, MK, special thanks to Denis Girou for help]
+%%
+%% Requires vtex.def 7.46 or newer, 10-14-01
+%%
+%% For support and possible updates, check
+%%      http://www.micropress-inc.com
+%%
+
+\def\pstdriver{VTeX}
+{\catcode`\"=12\gdef
+\pstverb#1{\special{pS*GS @beginspecial @setspecial #1 @endspecial GR }}
+}%
+\def\pstunit{1bp}%
+\def\pstVerb#1{\special{pS: #1}}%
+\def\pstverbscale{SDict begin normalscale end}
+\ifx\textsuperscript\@undefined
+   \def\pstheader#1{\special{header=#1}}
+\else
+% D.G. modification begin - Apr. 29, 2003 - From Michael Vulis
+%  \ifx\Gin@PS@file@header\@undefined
+%    \def\pstheader#1{\AtBeginDvi{\special{header=#1}}}
+%  \else
+%    \let\pstheader\Gin@PS@file@header
+%  \fi
+  \def\pstheader#1{\AtBeginDvi{\immediate\special{header=#1}}}
+% D.G. modification end
+\fi
+\def\pstrotate{CP CP translate 3 -1 roll neg rotate \tx@NET}
+%%
+%% ****************** END VTeX *****************************
+
+%%%%%%%%%%%%%%%%%%% !! CUSTOMIZATION STUFF GOES HERE: !! %%%%%%%%%%%%%%%%%%
+%% If you want to include your own customizations to pstricks.tex, then
+%% uncomment the \pstcustomize command, and include your modifications
+%% after \pstcustomize. These will be read in after pstricks.tex.
+%
+%  Some customization needed for VTeX since the coordinate system
+%  is different.
+\newif\if@colorstack
+\ifnum\OpMode>-1
+\ifnum\OpMode<3
+\@colorstacktrue
+% D.G. modification begin - Nov. 17, 1999
+\let\vtex@pspicture=\pspicture
+\def\pspicture{\special{G(}\@colorstackfalse\vtex@pspicture}%
+\let\vtex@endpspicture=\endpspicture
+\def\endpspicture{\vtex@endpspicture\@colorstacktrue\special{G)}%
+}
+% D.G. modification end
+\fi
+\fi
+
+\pstcustomize
+\def\tx@RotBegin{neg RotBegin }
+\def\pst@rotlist{mark RAngle /a ED cleartomark a }
+% D.G. modification begin - Oct.  6, 1999
+\def\tx@Rot{neg Rot }
+% D.G. modification end
+\def\psfs@solid{\pst@fill{\pst@usecolor\psfillcolor fill }}
+\def\psfs@eofill{\pst@fill{\pst@usecolor\psfillcolor eofill}}
+
+\endinput
+
+\iffalse
+%%
+%%%%%%%%%%%%%%%%%%% !! GENERAL INSTRUCTIONS !! %%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+Because there are no standards for dvi-to-PS driver \special's,
+some driver-dependent commands must be defined in this file.
+
+Possibly correct definitions for some dvi drivers are given below.
+Copy the section for the driver you want to use to the indicated place
+near the beginning of the file, replacing any other definitions you
+might find there.
+
+When changing drivers, you may need to remake the header file.
+
+See the PSTricks read-me file for further installation instructions.
+
+Please report good and bad experiences with dvi-to-PS drivers,
+along with the definitions of these commands that worked
+for you, to tvz@Princeton.EDU.  Thanks.
+
+
+%%%%%%%%%%%%%%%% DESCRIPTION OF CONFIGURATION DEFINITIONS %%%%%%%%%%%%%%%
+
+Here are the commands that must be defined in this file:
+
+   \pstverb{}    -  The argument is included as verbatim PostScript,
+                    grouped by save and restore. The coordinate system
+	should be square, not rotated, and with the origin
+	at TeX's currentpoint.
+
+   \pstVerb{}    -  The argument is included as verbatim PostScript, not
+                    grouped by (g)save and (g)restore. The currentpoint
+	should be TeX's currentpoint.
+
+   \pstunit      -  The units used by driver for graphics included with
+                    \pstverb. Probably 1bp or 1sp.
+
+   \pstverbscale - The PostScript code that scales the coordinate system
+                   from that in effect with \pstVerb to that in effect
+                   with \pstverb. Should not translate to the currentpoint.
+
+   \pstrotate    - The PostScript code that takes a number off the stack
+                   and rotates the axes properly. I.e.,
+                   \pstVerb{angle \pstrotate} is used to begin rotations.
+
+   \pstheader{}  - The argument is a header file (e.g., .pro file).
+                   If your driver does not support such a special, then
+                   the command might just remind you to include the header
+                   when printing. You can use PSTricks without a header,
+                   in which case it does not matter how you define
+                   \pstheader. See read-me.pst for details.
+                   If you cannot change the default directory where your
+                   driver looks for header files, and you cannot write to
+                   that directory, then you include the path for your
+                   PSTricks header files.
+                   E.g., \def\pstheader#1{\special{header=~/tex/#1}}.
+
+   \pstdriver    - The name of the driver.
+
+
+%%%%%%%%% !! HOW TO MAKE A TEX FORMAT WITH PSTRICKS PRELOADED !! %%%%%%%%
+
+See your local TeX documentation for instructions on creating a TeX format.
+
+Before making the format, be sure that this configuration file is correct.
+It will be read only when creating the format, and not with every job.
+
+If you are not using header files, there are no more special instructions.
+
+Special instructions when using header files:
+
+ - If you want to include supplementary PSTricks files (e.g., pst-node.tex),
+   add \input commands in the customization section above.
+
+ - If your definition of \pstheader is, e.g.
+
+     \def\pstheader#1{\special{\header=#1}}
+
+   then change it to
+
+     \def\pstheader#1{%
+       \expandafter\everyjob\expandafter{\the\everyjob
+         \special{header=#1}}}
+
+   and put your original definition in the customization section, AFTER
+   any \input commands. E.g., the customization section might look like:
+
+     \pstcustomize
+     \input pst-node.tex
+     \input pst-coil.tex
+     \def\pstheader#1{\special{header=#1}}
+
+ - Input pstricks.tex at the appropriate time when creating the format.
+   E.g., when initex stops running:
+     *\input pstricks
+     *\dump
+\fi
+
+%%
+%% END: pstricks.con
diff --git a/Master/texmf-dist/tex/generic/pstricks/config/xdvipdfmx.cfg b/Master/texmf-dist/tex/generic/pstricks/config/xdvipdfmx.cfg
new file mode 100644
index 00000000000..423849dab56
--- /dev/null
+++ b/Master/texmf-dist/tex/generic/pstricks/config/xdvipdfmx.cfg
@@ -0,0 +1,225 @@
+%% BEGIN: pstricks.con (for xdvipdfmx driver)
+%%
+%% Configuration file for PSTricks
+%%
+%% Version 0.02 (2008/06/20)
+%%
+%% For use with xdvipdfmx
+%% Created by SMiyata based on standard pstricks.con from TeXLive distribution.
+%% This file may be distributed, used and modified freely.
+%
+\def\pstdriver{xdvipdfmx}
+\def\pstverb#1{\special{pst: #1}}  % Check catcode of "
+\def\pstunit{1bp}%
+\def\pstVerb#1{\immediate\special{PST: #1}}
+\def\pstverbscale{72.27 72 div dup scale }
+% DG/SR modification begin  - Apr. 28, 1997 (D. Carlisle + S. Rahtz)
+% \def\pstheader#1{\special{header=#1}}
+% We used to check for |\AtBeginDvi|, but that was broken in early release
+% so we now check for the existence of |\textsuperscript| (added 1995/05/16)
+\ifx\textsuperscript\@undefined
+   \def\pstheader#1{\special{header=#1}}
+\else
+  \ifx\Gin@PS@file@header\@undefined
+    \def\pstheader#1{\AtBeginDvi{\special{header=#1}}}
+  \else
+    \let\pstheader\Gin@PS@file@header
+  \fi
+\fi
+% DG/SR modification end
+%%
+%% In the following, CP is short for currentpoint.
+%% The neg is necessary because dvips scales the coordinates by 1 -1.
+%% \tx@NET means neg exch neg exch translate.
+\def\pstrotate{CP CP translate 3 -1 roll neg rotate \tx@NET}
+%%
+%% ****************** END xdvipdfmx *****************************
+
+%%%%%%%%%%%%%%%%%%% !! CUSTOMIZATION STUFF GOES HERE: !! %%%%%%%%%%%%%%%%%%
+%% If you want to include your own customizations to pstricks.tex, then
+%% uncomment the \pstcustomize command, and include your modifications
+%% after \pstcustomize. These will be read in after pstricks.tex.
+\def\c@lor@to@ps#1 #2\@@{\csname c@lor@ps@#1\endcsname#2 \@@}
+\def\c@lor@ps@#1 #2\@@{TeXDict begin #1 end}
+\def\c@lor@ps@rgb#1\@@{#1 setrgbcolor}
+\def\c@lor@ps@hsb#1\@@{#1 sethsbcolor}
+\def\c@lor@ps@cmyk#1\@@{#1 setcmykcolor}
+\def\c@lor@ps@gray#1\@@{#1 setgray}
+\pstcustomize
+\typeout{Using PSTricks configuration for XeTeX+xdvipdfmx}
+\def\@@scalebox{%
+\leavevmode
+\hbox{%
+\ifdim\pst@tempd\p@<\z@
+\pst@dimg=\pst@tempd\ht\pst@hbox
+\pst@dimh=\pst@tempd\dp\pst@hbox
+\dp\pst@hbox=-\pst@dimg
+\ht\pst@hbox=-\pst@dimh
+\else
+\ht\pst@hbox=\pst@tempd\ht\pst@hbox
+\dp\pst@hbox=\pst@tempd\dp\pst@hbox
+\fi
+\pst@dima=\pst@tempc\wd\pst@hbox
+\ifdim\pst@dima<\z@\kern-\pst@dima\fi
+\special{x: bscale \pst@tempc \pst@tempd}%
+\hbox to \z@{\box\pst@hbox\hss}%
+\special{x: escale}%
+\ifdim\pst@dima>\z@\kern\pst@dima\fi}}
+\let\ps@@scalebox\@@scalebox
+\def\ps@rotateleft#1{%
+\leavevmode\hbox{\hskip\ht#1\hskip\dp#1\vbox{\vskip\wd#1%
+\pst@Verb{90 \tx@RotBegin}
+\vbox to \z@{\vss\hbox to \z@{\box#1\hss}\vskip\z@}%
+\pst@Verb{\tx@RotEnd}}}}
+\def\ps@rotateright#1{%
+  \leavevmode\hbox{%
+  \hskip\ht#1\hskip\dp#1\vbox{\vskip\wd#1%
+  \pst@Verb{-90 \tx@RotBegin}
+  \vbox to \z@{\hbox to \z@{\hss\box#1}\vss}%
+  \pst@Verb{\tx@RotEnd}}}}
+\def\ps@rotatedown#1{%
+\hbox{\hskip\wd#1\vbox{\vskip\ht#1\vskip\dp#1%
+\pst@Verb{180 \tx@RotBegin}%
+\vbox to \z@{\hbox to \z@{\box#1\hss}\vss}%
+\pst@Verb{\tx@RotEnd}}}}
+\def\begin@psclip{\special{x: gsave}}
+\def\end@psclip{\special{x: grestore}}
+\def\@newcolor#1#2#3{%
+\expandafter\edef\csname #1\endcsname{\noexpand\pst@color{#2}}%
+\expandafter\edef\csname\string\color@#1\endcsname{#2}%    hv 1.14 2005-12-17
+\expandafter\edef\csname\string\color@xetex@#1\endcsname{#3}%
+\ignorespaces}
+\def\newgray#1#2{%
+  \pst@checknum{#2}\pst@tempg
+  \@newcolor{#1}{\pst@tempg setgray}{gray \pst@tempg}%
+}
+\def\newrgbcolor#1#2{%
+  \pst@expandafter\pst@getnumiii{#2} {} {} {} {}\@nil
+  \@newcolor{#1}{\pst@tempg \pst@temph \pst@tempi setrgbcolor}{rgb \pst@tempg \pst@temph \pst@tempi}%
+}
+\def\newhsbcolor#1#2{%
+  \pst@expandafter\pst@getnumiii{#2} {} {} {} {}\@nil
+  \@newcolor{#1}{\pst@tempg \pst@temph \pst@tempi sethsbcolor}{hsb \pst@tempg \pst@temph \pst@tempi}%
+}
+\def\newcmykcolor#1#2{%
+  \pst@expandafter\pst@getnumiv{#2} {} {} {} {} {}\@nil
+  \@newcolor{#1}{\pst@tempg \pst@temph \pst@tempi \pst@tempj setcmykcolor}%
+                {cmyk \pst@tempg \pst@temph \pst@tempi \pst@tempj}%
+}
+\newgray{black}{0}
+\newgray{darkgray}{.25}
+\newgray{gray}{.5}
+\newgray{lightgray}{.75}
+\newgray{white}{1}
+\newrgbcolor{red}{1 0 0}
+\newrgbcolor{green}{0 1 0}
+\newrgbcolor{blue}{0 0 1}
+\newrgbcolor{yellow}{1 1 0}
+\newrgbcolor{cyan}{0 1 1}
+\newrgbcolor{magenta}{1 0 1}
+
+\@ifundefined{LaTeXe}%
+  {\def\current@@@@color{\csname\string\color@xetex@\psfillcolor\endcsname}}{%
+  \AtBeginDocument{\@ifpackageloaded{xcolor}{\def\current@@@@color{\psfillcolor}}%
+    {\def\current@@@@color{\csname\string\color@\psfillcolor\endcsname}}}}
+\def\pst@starbox{%
+\setbox\pst@hbox\hbox{{%
+  \def\current@color{\current@@@@color}%
+\dimen@\wd\pst@hbox\advance\dimen@2\psframesep\wd\pst@hbox\dimen@%
+\dimen@\ht\pst@hbox\advance\dimen@\psframesep\ht\pst@hbox\dimen@%
+\dimen@\dp\pst@hbox\advance\dimen@\psframesep\dp\pst@hbox\dimen@%
+\@ifundefined{LaTeXe}{\special{color push \current@color}%
+    \rlap{\vrule width\wd\pst@hbox height\ht\pst@hbox depth\dp\pst@hbox}%
+    \special{color pop}}%
+  {\color@block{\wd\pst@hbox}{\ht\pst@hbox}{\dp\pst@hbox}}}%
+\rlap{\hskip\psframesep\unhbox\pst@hbox}}}
+\def\AltClipMode{}
+\def\putoverlaybox#1{%
+\hbox{\special{x: gsave}\special{x: initoverlay #1}\copy\theoverlaybox\special{x: grestore}}}
+\def\pst@overlay#1{\edef\curr@overlay{#1}\special{x: clipoverlay #1}\aftergroup\pst@endoverlay}
+\def\pst@endoverlay{\special{x: clipoverlay \curr@overlay}}
+\def\AltOverlayMode{}
+%The next line is not necessary, if pstricks.sty of [2007/02/18 v0.33] or newer is used.
+\@ifundefined{LaTeXe}{}{\AtBeginDocument{\psset{fillcolor=white}}}
+\endinput
+%
+%
+%%%%%%%%%%%%%%%% DESCRIPTION OF CONFIGURATION DEFINITIONS %%%%%%%%%%%%%%%
+
+Here are the commands that must be defined in this file:
+
+   \pstverb{}    -  The argument is included as verbatim PostScript,
+                    grouped by save and restore. The coordinate system
+		    should be square, not rotated, and with the origin
+		    at TeX's currentpoint.
+
+   \pstVerb{}    -  The argument is included as verbatim PostScript, not
+                    grouped by (g)save and (g)restore. The currentpoint
+		    should be TeX's currentpoint.
+
+   \pstunit      -  The units used by driver for graphics included with
+                    \pstverb. Probably 1bp or 1sp.
+
+   \pstverbscale - The PostScript code that scales the coordinate system
+                   from that in effect with \pstVerb to that in effect
+                   with \pstverb. Should not translate to the currentpoint.
+
+   \pstrotate    - The PostScript code that takes a number off the stack
+                   and rotates the axes properly. I.e.,
+                   \pstVerb{angle \pstrotate} is used to begin rotations.
+
+   \pstheader{}  - The argument is a header file (e.g., .pro file).
+                   If your driver does not support such a special, then
+                   the command might just remind you to include the header
+                   when printing. You can use PSTricks without a header,
+                   in which case it does not matter how you define
+                   \pstheader. See read-me.pst for details.
+                   If you cannot change the default directory where your
+                   driver looks for header files, and you cannot write to
+                   that directory, then you include the path for your
+                   PSTricks header files.
+                   E.g., \def\pstheader#1{\special{header=~/tex/#1}}.
+
+   \pstdriver    - The name of the driver.
+
+
+%%%%%%%%% !! HOW TO MAKE A TEX FORMAT WITH PSTRICKS PRELOADED !! %%%%%%%%
+
+See your local TeX documentation for instructions on creating a TeX format.
+
+Before making the format, be sure that this configuration file is correct.
+It will be read only when creating the format, and not with every job.
+
+If you are not using header files, there are no more special instructions.
+
+Special instructions when using header files:
+
+ - If you want to include supplementary PSTricks files (e.g., pst-node.tex),
+   add \input commands in the customization section above.
+
+ - If your definition of \pstheader is, e.g.
+
+     \def\pstheader#1{\special{\header=#1}}
+
+   then change it to
+
+     \def\pstheader#1{%
+       \expandafter\everyjob\expandafter{\the\everyjob
+         \special{header=#1}}}
+
+   and put your original definition in the customization section, AFTER
+   any \input commands. E.g., the customization section might look like:
+
+     \pstcustomize
+     \input pst-node.tex
+     \input pst-coil.tex
+     \def\pstheader#1{\special{header=#1}}
+
+ - Input pstricks.tex at the appropriate time when creating the format.
+   E.g., when initex stops running:
+     *\input pstricks
+     *\dump
+
+
+%%
+%% END: pstricks.con