From 9e4f6fc5a8c0bb587b302b8c7f1c85767bab67df Mon Sep 17 00:00:00 2001 From: Manuel Pégourié-Gonnard Date: Sun, 22 Jun 2008 10:07:49 +0000 Subject: real pstricks update (oops) 21jun08 git-svn-id: svn://tug.org/texlive/trunk@8922 c570f23f-e606-0410-a88d-b1316a301751 --- .../doc/generic/pstricks/Changes.generic | 83 ++ .../texmf-dist/doc/generic/pstricks/Changes.latex | 28 + Master/texmf-dist/doc/generic/pstricks/Makefile | 105 +- .../texmf-dist/doc/generic/pstricks/defaults.pst | 149 --- .../doc/generic/pstricks/examples/changes.pdf | Bin 0 -> 62337 bytes .../doc/generic/pstricks/examples/changes.tex | 662 ++++++++++ .../doc/generic/pstricks/examples/chartest.pdf | Bin 0 -> 10025 bytes .../doc/generic/pstricks/examples/chartest.tex | 25 + .../doc/generic/pstricks/examples/denis1.pdf | Bin 0 -> 21760 bytes .../doc/generic/pstricks/examples/denis1.tex | 41 + .../doc/generic/pstricks/examples/denis2.pdf | Bin 0 -> 5005 bytes .../doc/generic/pstricks/examples/denis2.tex | 36 + .../doc/generic/pstricks/examples/filetest.dat | 71 ++ .../doc/generic/pstricks/examples/filetest.pdf | Bin 0 -> 12054 bytes .../doc/generic/pstricks/examples/filetest.raw | 6 + .../doc/generic/pstricks/examples/filetest.tex | 84 ++ .../doc/generic/pstricks/examples/pst-test.pdf | Bin 0 -> 16781 bytes .../doc/generic/pstricks/examples/pst-test.tex | 126 ++ .../doc/generic/pstricks/examples/samples.pdf | Bin 0 -> 47029 bytes .../doc/generic/pstricks/examples/samples.tex | 443 +++++++ .../doc/generic/pstricks/examples/tp-test.pdf | Bin 0 -> 16906 bytes .../doc/generic/pstricks/examples/tp-test.tex | 72 ++ Master/texmf-dist/doc/generic/pstricks/psd-3d.tex | 12 - .../texmf-dist/doc/generic/pstricks/psd-basi.tex | 648 ---------- .../texmf-dist/doc/generic/pstricks/psd-cove.tex | 108 -- .../texmf-dist/doc/generic/pstricks/psd-cust.tex | 406 ------- .../texmf-dist/doc/generic/pstricks/psd-esse.tex | 392 ------ .../texmf-dist/doc/generic/pstricks/psd-fill.tex | 12 - .../texmf-dist/doc/generic/pstricks/psd-help.tex | 332 ----- .../texmf-dist/doc/generic/pstricks/psd-node.tex | 1279 -------------------- .../texmf-dist/doc/generic/pstricks/psd-para.tex | 345 ------ .../texmf-dist/doc/generic/pstricks/psd-pict.tex | 500 -------- .../texmf-dist/doc/generic/pstricks/psd-spec.tex | 500 -------- .../texmf-dist/doc/generic/pstricks/psd-text.tex | 260 ---- .../texmf-dist/doc/generic/pstricks/psd-tree.tex | 816 ------------- .../texmf-dist/doc/generic/pstricks/pst-user.cls | 1111 ----------------- .../texmf-dist/doc/generic/pstricks/pst-user.ist | 7 - .../texmf-dist/doc/generic/pstricks/pst-user.tex | 87 -- 38 files changed, 1705 insertions(+), 7041 deletions(-) create mode 100644 Master/texmf-dist/doc/generic/pstricks/Changes.generic create mode 100644 Master/texmf-dist/doc/generic/pstricks/Changes.latex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/defaults.pst create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/changes.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/changes.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/chartest.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/chartest.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/denis1.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/denis1.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/denis2.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/denis2.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/filetest.dat create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/filetest.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/filetest.raw create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/filetest.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/pst-test.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/pst-test.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/samples.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/samples.tex create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/tp-test.pdf create mode 100644 Master/texmf-dist/doc/generic/pstricks/examples/tp-test.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-3d.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-basi.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-cove.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-cust.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-esse.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-fill.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-help.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-node.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-para.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-pict.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-spec.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-text.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/psd-tree.tex delete mode 100644 Master/texmf-dist/doc/generic/pstricks/pst-user.cls delete mode 100644 Master/texmf-dist/doc/generic/pstricks/pst-user.ist delete mode 100644 Master/texmf-dist/doc/generic/pstricks/pst-user.tex (limited to 'Master/texmf-dist/doc/generic/pstricks') diff --git a/Master/texmf-dist/doc/generic/pstricks/Changes.generic b/Master/texmf-dist/doc/generic/pstricks/Changes.generic new file mode 100644 index 00000000000..7f6e9558747 --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/Changes.generic @@ -0,0 +1,83 @@ +pstricks.tex -------- +1.24 2008-06-17 - added \psDEBUG[#1]#2 for better dubugging +1.23 2008-05-23 - add octogon symbol (hv) + - fix bug with D>- and D>, which draws the + sides as betier curves (ArrowD type in pstricks.pro) + - add special coor type (*x f(x)), which invokes the + algebraic parser for f(x) before using the default + (!x y) coor type + - add option linejoin=0,1,or 2 for connecting lines + - add option linecap=0,1,or 2 for line ends + - small tweaks to psellipticarc x y -> xOrig yOrig + - fix introduced bug with \newpsstyle: \pst@tempa->\pst@tempA + - add PS subroutines /UserCoor and /ScreenCoor for easy + transforming into user or screen coordinates + - changed wrong name of \psk@shift to \pst@shift + - fix bug with pst-node and \\[name=...]. It now uses + \ps@ifnextchar for scanning the next token + - fix bug with pst@tempg in \polar@coor. It was already used in + \pst@getangle. + - new option gridfont for the label font of \psgrid + can now be any of the PS-fonts Helvetica (Default), + Times-Roman, Palatino-Roman, ... +1.15a 2007-01-05 - \parabola->\psparabola (old name still valid) (hv) +1.15 2006-12-19 - add support for more dot styles (from Etienne Riga) +1.14c 2006-04-29 - add option linecap for dashed lines +1.14b 2006-04-20 - fix a bug in \psset@linetype +1.14a 2006-02-06 - revert the changes for pslongbox (introduced bug) +1.14 2005-12-17 - make the color part compatible to color/xcolor +1.13 2005-12-15 - fix bug of \psdot* +1.12 2005-10-25 - spurious blank for \multirput + - shift only for an absolute length + - add the missing arrows ]-[)-( +1.11 2005-09-08 - rename \rotateleft | right | down to + \psrotateleft | right | down to be consistant to the + other PSTricks macro names + - new fillstyle options + - move the code for arcs of an ellipse into pstricks.pro +1.10 2005-08-13 - fix bug with \multips (spurious blank) (hv) + - allow empty optional arrow argument \psline[..]{}(2,2) + - redefined \psarc@iv for negative loops of \nccircle + - introduce new options shift and showgrid for the + main pspicture environment + - rename \scalebox and \scaleboxto to + \psscalebox(to) to be consistant to the + other PSTricks macro names +1.08 2005-06-02 fix bug with \multips (spurious blank) (hv) +1.07 2005-05-06 make \nccircle working for counter-clockwise + orientation (hv) +1.06 2005-02-24 fix spurious blank in doublestroke (hv) + + +pst-node.tex -------- +1.00 2007-08-18 - new option pcRef for the first node (hv) + - new option Circle for psmatrix (hv) + - fix bug with pst-node and \\[name=...]. It now uses + \ps@ifnextchar for scanning the next token (defined + in pstricks.tex) + + +pst-plot.tex -------- +1.02 2008-03-21 - added an additional optional argument for \psaxes + which allows to put labels at the end of the axes + [Xtext,Xangle,Ytext,Yangle] +1.01 2008-01-26 - make negative Dx/Dy work (hv) +1.00 2007-06-26 - added two new line style LineToXaxis/LineToYaxis (hv) + + +pst-tree.tex -------- +1.00 2007-01-03 - fix bug with \endpsTree (hv) + + +xdvipdfmx.con ------ +0.01 2007-03-11 - first CTAN version, must be renamed to pstricks.con + when used with XeTeX + +vtex.con ------ +0.02 2008-01-01 - disable transparent color setting diff --git a/Master/texmf-dist/doc/generic/pstricks/Changes.latex b/Master/texmf-dist/doc/generic/pstricks/Changes.latex new file mode 100644 index 00000000000..a1116de2b6d --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/Changes.latex @@ -0,0 +1,28 @@ +pstricks.sty -------- +0.37 2008-01-24 - add option distiller for transparent colors +0.36 2008-01-22 - Better error message, when the document + has the same name than a PSTricks file. (RN) +0.35 2008-01-01 - add message for loading pstalpparser.pro + - add option vtex to disable opacity values +0.34 2007-09-13 - add message for loading pstricks.pro + - and pst-dots.pro (hv) +0.33 2007-02-18 set initial color (hv) +0.32 2006-08-10 message for loading the pro file (hv) +0.31 2005-12-19 one more step to a better color support (hv) +0.30 2005-11-15 drop test for pstcol + fix bug with xcolor (hv) +0.24 2005-08-30 drop support for \sclabox check, it is now renamed + in pstricks.tex (hv) +0.23 2005-06-02 Option DIA to prevent a clash with \scalebox (hv) +0.22 2005-02-25 changes were done in the wrong version +0.21 2005-02-21 fix problem with \newrgbcolor (RN,hv) + +pst-node.sty -------- + 2007-09-13 add message for loading pst-node.pro (hv) + 2006-01-01 message for loading the pro file + +pst-all.sty -------- + 2008-01-01 load pstricks-add + 2007-09-13 change order of the packages + 2006-12-19 do not load pst-char, it is now part of pst-text + \ No newline at end of file diff --git a/Master/texmf-dist/doc/generic/pstricks/Makefile b/Master/texmf-dist/doc/generic/pstricks/Makefile index ce772c9e8cd..38c4f089a4f 100644 --- a/Master/texmf-dist/doc/generic/pstricks/Makefile +++ b/Master/texmf-dist/doc/generic/pstricks/Makefile @@ -1,97 +1,48 @@ -# Rolf Niepraschk, niepraschk@ptb.de, 2003-02-23 +# `Makefile' for `pst-3dplot.pdf', hv, 2007/03/17 -.SUFFIXES : .tex .dvi .ps .pdf .eps +.SUFFIXES : .tex .ltx .dvi .ps .pdf .eps -MAIN = pst-user +PACKAGE = pst-news2008 -# D.G. modification begin - Feb. 28, 2003 -#LATEX = elatex -LATEX = latex -# D.G. modification end -PDFLATEX = pdfelatex -PS2PDF = ps2pdf - -# D.G. modification begin - Feb. 28, 2003 -PS2PDF_OPT1 = -sPAPERSIZE=letter -#PS2PDF_OPT1 = -sPAPERSIZE=a4 -# D.G. modification end -PS2PDF_OPT2 = -sPAPERSIZE=letter - -DVIPSFLAGS1 = -Ppdf -G0 -DVIPSFLAGS2 = -Pwww -E -#GSOPT = GS_OPTIONS=-dAutoRotatePages=/None -GSOPT = GS_OPTIONS=-dPDFSETTINGS=/prepress +MAIN = $(PACKAGE) -PICS := $(PICS:.eps=.pdf) +LATEX = latex -# D.G. modification begin - Mar. 7, 2003 -#ADDINPUTS = pst-user.cls defaults.pst -ADDINPUTS = pst-user.cls defaults.pst \ - psd-cove.tex psd-esse.tex psd-basi.tex psd-para.tex psd-cust.tex \ - psd-pict.tex psd-text.tex psd-node.tex psd-tree.tex psd-fill.tex \ - psd-3d.tex psd-spec.tex psd-help.tex -# D.G. modification end +ARCHNAME = $(MAIN)-$(shell date +%y%m%d) -ARCHNAME = $(MAIN)-$(shell date +%y%m%d).zip +ARCHFILES = $(PACKAGE).sty $(PACKAGE).tex $(PACKAGE).pro $(MAIN).tex README Changes Makefile -# D.G. modification begin - Mar. 7, 2003 -TARNAME = $(MAIN)-$(shell date +%y%m%d).tar -# D.G. modification end +all : doc clean +doc: $(MAIN).pdf -# D.G. modification begin - Feb. 28, 2003 -#all : $(MAIN).pdf $(MAIN)-old.pdf -all : $(MAIN).pdf -# D.G. modification end +$(MAIN).pdf : $(MAIN).ps + GS_OPTIONS=-dAutoRotatePages=/None ps2pdf $< +$(MAIN).ps : $(MAIN).dvi + dvips $< -$(MAIN).dvi : $(MAIN).tex $(ADDINPUTS) +$(MAIN).dvi : $(MAIN).tex + $(LATEX) $< + $(LATEX) $< + if ! test -f $(basename $<).glo ; then touch $(basename $<).glo; fi + if ! test -f $(basename $<).idx ; then touch $(basename $<).idx; fi + makeindex -s gglo.ist -t $(basename $<).glg -o $(basename $<).gls \ + $(basename $<).glo + makeindex -t $(basename $<).ilg -o $(basename $<).ind \ + $(basename $<).idx + bibtex $(basename $<) $(LATEX) $< -# D.G. modification begin - Feb. 28, 2003 -# makeindex -t $(basename $<).ilg $(basename $<) -# D.G. modification end - makeindex -t $(basename $<).ilg -s pst-user.ist $(basename $<) $(LATEX) $< - -$(MAIN).pdf : $(MAIN).ps - $(PS2PDF) $(PS2PDF_OPT1) $< $@ - -%.ps : %.dvi - dvips $(DVIPSFLAGS1) $< -o $@ - -pst-user-old.pdf : pst-user-old.tex pst-usr1.pdf pst-usr2.pdf pst-usr3.pdf \ - pst-usr4.pdf - $(PDFLATEX) $< - -pst-usr%.pdf : pst-usr%.ps.gz - zcat $< | $(PS2PDF) $(PS2PDF_OPT2) - > $@ clean : - $(RM) $(addprefix $(MAIN), .aux .ilg .ind .idx .log .out .tmp .toc) -# D.G. modification begin - Mar. 7, 2003 -# $(RM) $(addprefix $(MAIN)-old, .log .aux) -# $(RM) pst-usr?.pdf -# D.G. modification end + $(RM) $(addprefix $(MAIN), .log .aux .glg .glo .gls .ilg .idx .ind .tmp .toc .out .blg .Roessler .bbl ) + $(RM) $(addprefix $(MAIN), .dvi .ps) veryclean : clean - $(RM) $(addprefix $(MAIN), .ps .dvi .pdf) -# D.G. modification begin - Mar. 7, 2003 -# $(RM) $(MAIN)-old.pdf - $(RM) *.aux -# D.G. modification end + $(RM) $(addprefix $(MAIN), .pdf .bbl .blg) arch : - zip $(ARCHNAME) $(MAIN).tex $(ADDINPUTS) pst-user-old.tex Makefile - @ echo ; echo $(ARCHNAME) ; echo + zip $(ARCHNAME).zip $(ARCHFILES) -# D.G. modification begin - Mar. 7, 2003 -tar: - tar -cf $(TARNAME) $(MAIN).tex $(ADDINPUTS) \ - pst-user.ist pst-user.idx \ - CHANGES VERSIONS TODO \ - Makefile artistic.txt defaults.pst \ - pstricks.tex pst-eps.tex pst-node.tex pst-tree.tex \ - *.sty pst-user.pdf - gzip --force $(TARNAME) - ls -l $(TARNAME).gz -# D.G. modification end +# EOF diff --git a/Master/texmf-dist/doc/generic/pstricks/defaults.pst b/Master/texmf-dist/doc/generic/pstricks/defaults.pst deleted file mode 100644 index 4e3ba5f27f2..00000000000 --- a/Master/texmf-dist/doc/generic/pstricks/defaults.pst +++ /dev/null @@ -1,149 +0,0 @@ -%% defaults.pst -%% Created with unix shell commands: -%% grep ^.psset\@ pstricks.tex > defaults.pst -%% grep ^.psset\@ pst-node.tex >> defaults.pst -%% grep ^.psset\@ pst-grad.tex >> defaults.pst -%% grep ^.psset\@ pst-coil.tex >> defaults.pst -%% grep ^.psset\@ pst-eps.tex >> defaults.pst -%% grep ^.psset\@ pst-plot.tex >> defaults.pst -%% grep ^.psset\@ pst-tree.tex >> defaults.pst -%% Input by pst-user.tex -\psset@swapaxes{false} -\psset@showpoints{false} -\psset@border{0pt} -\psset@bordercolor{white} -\psset@doubleline{false} -\psset@doublesep{1.25\pslinewidth} -\psset@doublecolor{white} -\psset@shadow{false} -\psset@shadowsize{3pt} -\psset@shadowangle{-45} -\psset@shadowcolor{darkgray} -\psset@linewidth{.8pt} -\psset@linecolor{black} -\psset@dash{5pt 3pt} -\psset@dashadjust{true} -\psset@dotsep{3pt} -\psset@linestyle{solid} -\psset@fillcolor{white} -\psset@hatchwidth{.8pt} -\psset@hatchsep{4pt} -\psset@hatchcolor{black} -\psset@hatchangle{45} -\psset@fillstyle{none} -\psset@arrowscale{1} -\psset@arrowsize{1.5pt 2} -\psset@arrowlength{1.4} -\psset@arrowinset{.4} -\psset@tbarsize{2pt 5} -\psset@bracketlength{.15} -\psset@rbracketlength{.15} -\psset@arrows{-} -\psset@liftpen{0} -\psset@linetype{0} -\psset@gangle{0} -\psset@curvature{1 .1 0} -\psset@dotsize{2pt 2} -\psset@dotscale{1} -\psset@dotangle{0} -\psset@dotstyle{*} -\psset@linearc{0pt} -\psset@framearc{0} -\psset@cornersize{relative} -\psset@dimen{outer} -\psset@gridwidth{.8pt} -\psset@griddots{0} -\psset@gridcolor{black} -\psset@subgridwidth{.4pt} -\psset@subgridcolor{gray} -\psset@subgriddots{0} -\psset@subgriddiv{5} -\psset@gridlabels{10pt} -\psset@gridlabelcolor{black} -\psset@framesep{3pt} -\psset@boxsep{true} -\psset@trimode{U} -\psset@arcsep{0} -\psset@radius{.25cm} -\psset@ref{c} -\psset@rot{0} -\psset@labelsep{5pt} -\psset@refangle{0} -\psset@nodealign{false} -\psset@href{0} -\psset@vref{.7ex} -\psset@framesize{10pt} -\psset@nodesep{0pt} -\psset@arm{10pt} -\psset@offset{0pt} -\psset@angle{0} -\psset@arcangle{8} -\psset@ncurv{.67} -\psset@loopsize{1cm} -\psset@boxsize{.4cm} -\psset@nrot{0} -\psset@npos{} -\psset@tpos{.5} -\psset@shortput{none} -\psset@colsep{1.5cm} -\psset@rowsep{1.5cm} -\psset@mcol{c} -\psset@mnodesize{-1pt} -\psset@mnode{R} -\psset@emnode{none} -\psset@gradbegin{gradbegin} -\psset@gradend{gradend} -\psset@gradlines{500} -\psset@gradmidpoint{.9} -\psset@gradangle{0} -\psset@coilwidth{1cm} -\psset@coilheight{1} -\psset@coilarm{.5cm} -\psset@coilaspect{45} -\psset@coilinc{10} -\psset@bbllx{0pt} -\psset@bblly{0pt} -\psset@bburx{0pt} -\psset@bbury{0pt} -\psset@headers{none} -\psset@checkfile{true} -\psset@makeeps{new} -\psset@headerfile{} -\psset@plotstyle{line} -\psset@plotpoints{50} -\psset@ticksize{3pt} -\psset@tickstyle{full} -\psset@ticks{all} -\psset@labels{all} -\psset@Ox{0} -\psset@Dx{1} -\psset@dx{0} -\psset@Oy{0} -\psset@Dy{1} -\psset@dy{0} -\psset@showorigin{true} -\psset@axesstyle{axes} -\psset@treemode{D} -\psset@treeflip{false} -\psset@root{\TC} -\psset@treesep{.75cm} -\psset@xtreesep{0pt} -\psset@treenodesize{-1pt} -\psset@treefit{tight} -\psset@treerep{1} -\psset@showbbox{false} -\psset@levelsep{2cm} -\psset@varlevelsep{false} -\psset@treeshift{0} -\psset@skiplevels{0} -\psset@unary{middle} -\psset@leafalign{false} -\psset@edge{\ncline} -\psset@skipedge{} -\psset@fansize{1cm} -\psset@tnsep{} -\psset@tnyref{} -\psset@tnheight{\ht\strutbox} -\psset@tndepth{\dp\strutbox} -\psset@tnpos{} -\endinput diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/changes.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/changes.pdf new file mode 100644 index 00000000000..7d921997282 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/changes.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/changes.tex b/Master/texmf-dist/doc/generic/pstricks/examples/changes.tex new file mode 100644 index 00000000000..d431a41be2c --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/changes.tex @@ -0,0 +1,662 @@ +%% BEGIN changes.tex +%% +%% Changes listing for PSTricks. +%% Run with LaTeX, with or without the NFSS. +%% +%% Change these for a4 paper: +%\def\paperwidth{8.5in} +%\def\paperheight{11in} + +\def\FileVersion{0.93a} +\def\FileDate{March 12, 1993} + +\documentclass[11pt,a4paper]{article} +\usepackage[T1]{fontenc} + +%% PAGE PARAMETERS + +\usepackage{fancybox} +% Paragraphs are marked by large space rather than indentation: +\parindent 0pt +\parskip 6pt plus 1pt minus 1pt + +% No headers, 1in top margin +\usepackage[dvips]{geometry} +\geometry{tmargin=0pt,bmargin=3.3cm,headheight=0pt,headsep=0pt, +textheight=9in, footskip=.625in} +\usepackage[scaled]{luximono} +\usepackage{mathpazo} + + +% Now adjust for different paper size: +\newdimen\mydim +\mydim=\paperwidth +\advance\mydim-8.5in +\divide\mydim 2 +\advance\oddsidemargin \mydim +\advance\evensidemargin \mydim +\mydim=\paperheight +\advance\mydim-11in +\divide\mydim 2 +\advance\topmargin \mydim + +%% OTHER + +\renewcommand{\EveryVerbatimLine}[2]{} + +% Short meta (works in verbatim. Can't use < for other purposes. +\catcode`\<=13 \def<#1>{{\rm\it #1\/}} % (works in verbatim) + +% Short verbatim. +\catcode`\"=13 +\def"{\verb"} + +\catcode`\@=12 % In case I'm using AmS-LaTeX + +\begin{document} + +\begin{center} +{\large\bfseries Changes listing for PSTricks}\\[6pt] + Version \FileVersion\\ + \FileDate\\[6pt] + Timothy Van Zandt\\ + tvz@Princeton.EDU +\end{center} + + The PSTricks package is still preliminary. The features list + and user interface are unlikely to change much in the short term, but + the internal code is not stable. + +\section{VERSION 0.93 and 0.93a} + + There have been substantial changes (hopefully for the last time). + + This section describes the changes from 0.92 to 0.93a. The only differencea +between 0.93 and 0.93a are that a bug in "\nccircle" was fixed, and the +features in "\pst-old.tex" where either incorporated into the main files +("\Rput", "\Lput", "\Mput", "\Polar" and "\Cartesian") or eliminated entirely +("\NewPsput", "\OldPsput" and the old "\pscustom" commands). What is described +\subsection{Incompatible changes} + + {\bf + These changes may require modification to files prepared with version 0.92. +Sorry about the inconvenience. To avoid letting new changes catch you by +surprise, get on the PSTricks mailing list.} +\begin{enumerate} + +\item + "\SpecialCoor" has changed completely. See User's Guide for details. Most of +these changes were announced shortly after the release of v0.92, but +"pst-beta.tex" users should note that raw PostScript coordinates are now +delimited by "!" rather than by ":". + + {\bfseries How to fix files:} Search for "\SpecialCoor" in your file. Change the +old syntax to the new syntax according to this table: + \begin{center} + \begin{tabular}{ccl} + {\em Old} & {\em New} & {\em Type}\\[2pt] + "(c,)" & "(,)" & Cartesian.\\ + "(p,)" & "(;)" & Polar.\\ + "(n{})" & "()" & Center of .\\ + "(N[]{})" & "([])" & Relative to .\\ + "(m{}{})" & "(|)" & Mixed. + \end{tabular} + \end{center} +In addition, if you used the syntax "(:)" from "pst-beta.tex" for raw +postscript code, search for "(:" and replace by "(!". + +\item + Angles can no longer be specified by "{,}". "\SpecialCoor" lets you +use coordinates as angles, but they must be enclosed in "()". E.g., +"{(,)}". See User's Guide for details. + + {\bfseries How to fix files:} Add the parentheses "()" to angles given by +"{,}" and and precede this usage by "\SpecialCoor". However, there is no +easy way to search for "{,}" (unless you are good at using Unix's +regular expressions). On the other hand, you probably didn't use this features +much, and it will be easier to just wait for the old usage to cause errors. + +\item + The +\begin{LVerbatim} + arrowsize= +\end{LVerbatim} +parameter has been replaced by +\begin{LVerbatim} + arrowsize= + arrowlength= + arrowinset= +\end{LVerbatim} + + {\bfseries How to fix files:} + Search for "arrowsize", and break up your parameter change. You can also +just do nothing, because if you use the old syntax for "arrowsize", and + will simply be ignored. + +\item + The +\begin{LVerbatim} + tbarsize= +\end{LVerbatim} +parameter has been replaced by +\begin{LVerbatim} + tbarsize= + bracketlength= % For square brackets. + rbracketlength= % For round brackets. +\end{LVerbatim} + + {\bfseries How to fix files:} + Search for "tbarsize", and break up your parameter change. You can also just +do nothing, because if you use the old syntax for "tbarsize", will +simply be ignored. + +\item + "\pscustom" has changed substantially. E.g., (i) there is no "(x,y)" +argument, (ii) plots ("\psplot", etc.) no longer run backwards, and (iii) the +treatment of the currentpoint is much different. Also, most of the special +commands for use only within "\pscustom" have changed. See the User's Guide +for details. + + {\bfseries How to fix files:} + You must search for each use of "\pscustom", and make the following changes: + \begin{itemize} + \item Replace "\pscustom"'s old "(,)" argument by "\moveto(,)" +at the beginning of "\pscustom"'s main argument. + + \item Make the following substitutions inside "\pscustom"'s main argument: + \begin{center} + \begin{tabular}{ll} + {\em Old} & {\em New}\\[2pt] + "\pscode" & "\code"\\ + "\pscoor" & "\coor"\\ + "\psdim" & "\dim"\\ + "\psmove" & "\moveto"\\ + "\psclosepath" & "\closepath"\\ + "\psgroup{}" & "\gsave" "\grestore"\\ + "\psstroke" & "\stroke"\\ + "\psfill" & "\fill" + \end{tabular} + \end{center} + You can instead define, e.g., + \begin{quote} + "\def\pscode{\code}" , or\\ + "\newcommand{\pscode}{\code}" + \end{quote} + and + \begin{quote} + "\def\psgroup#1{\gsave #1 \grestore}" , or\\ + "\newcommand{\psgroup}{\gsave #1 \grestore}" + \end{quote} + + \item Check the output from your "\pscustom" command. If, after making the +above changes, things come out differently than inspected, it is probably +because the plot commands run ``forwards'' rather than ``backwards'', or +because of the new way that "\pscustom" treats the current point. Fix these on +a case-by-case basis. + \end{itemize} + +\item + "\listplot", "\psplot" and "\parametricplot" no longer have an "(,)" +argument. Use the "origin" parameter instead. + + {\bfseries How to fix files:} + Search for "\listplot", "\psplot" and "\parametricplot". Replace any +"(,)" argument by the parameter change "[origin={,}]". + +\item + To suppress labels with "\psaxes", use "labels=none/x/y", rather than +setting "Dx" and "Dy" to empty values. + + {\bfseries How to fix files:} + Search for "=}", "=," and "=]". Remove the "Dx=," and other such parameter +settings you find, and replace instead by "labels=none/x/y", depending on +whether you want no labels, labels on the x-axes only, or labels on the y-axis +only. + +\item + The "\scalebox" macro should use a space rather than a comma to separate the +x and y scaling factors, when two scaling factors are given. + + {\bfseries How to fix files:} + Wait to get error about bad numbers, or search for "\scalebox" and replace +"\scalebox{,}" by "\scalebox{ }". + +\item + The "dblframewidth" parameter is gone, because "\psdblframebox" is now just +a variant of "\psframebox" with "doubleline=true". The width of each frame is +now just "linewidth" + + {\bfseries How to fix files:} + Search for "dblframewidth" and replace the parameter setting be a +"linewidth" parameter setting. + +\item + The "\OldPsput" and "\Newpsput" commands are gone. These were originally +devised to retain compatibility with an older version of PSTricks that had a +"\psput" command instead of "\rput". + + {\bfseries How to fix files:} + If you used "\psput" with the new syntax, then search for "\psput" and +replace by "\rput". + + If you used "\psput" with the old syntax, then either search for "\psput" +commands and replace with "\rput" commands with the new syntax, or put the +following in a file so that the "\OldPsput" command defines "\psput" with the +old syntax: +\begingroup\catcode`\<=12 +\begin{LVerbatim} + \def\old@psput{\begingroup\old@psput@} + \def\old@psput@{% + \def\refpoint@x{.5}\def\refpoint@y{.5}% + \pst@ifstar{\@ifnextchar[% + {\old@psput@i}{\def\pst@rot{}\old@psput@ii}}} + \def\old@psput@i[#1]{\pst@getangle{#1}\pst@rot\old@psput@ii} + \def\old@psput@ii{\@ifnextchar<{\old@psput@iii}{\old@psput@iv}} + \def\old@psput@iii<#1>{\pst@@getref\old@psput@iv[#1]} + \def\old@psput@iv{% + \@ifnextchar({\end@psput\rput@i}{\end@psput\rput@i(0,0)}} + \def\OldPsput{\let\psput\old@psput} + \def\NewPsput{\let\psput\rput} +\end{LVerbatim} +\endgroup + +\end{enumerate} + + +\subsection{New files with old stuff} + +Remember to input these files when needed. To have these files loaded +automatically, put an "\input" command after "\customization" in the +configuration file ("pstricks.con"). + +\begin{description} + +\item[pst-node] + All the node stuff has been put in "pst-node.tex" / "pst-node.sty". + +\item[pst-plot] + The plot commands ("\psplot", etc.) and the "\psaxes" command have been put +in "pst-plot.tex" / "pst-plot.sty". ("pst-plot.tex" automatically loads +"multido.tex", which is required by the axes macros.) There are also some +variants of "\listplot", "\fileplot" and "\dataplot", that are less likely to +exceed PostScript operand stack limits. + +\item[colortab] + The table coloring commands have been put in "colortab.tex" / +"colortab.sty". This is no longer PSTricks specific, but most of the old stuff +works the same as before. The only exception is that "\omit{}" is not needed +when a column is not to be colored. The documentation for "colortab.tex" is in +"colortab.doc". There are also some new features: +\begin{itemize} +\item + "\SP" and "\RP": These let "\LCC" ... "\ECC" work with nested arrays or +"\multicolumns" when using Mittelbach's array.sty. See "colortab.doc" for +details. + +\item + "LColors", "\LC", "\LCi", "\LCii", "\LCiii", "\LCz", for shading the cells +in the "longtable" environment. See "colortab.doc" for details. + +umns when using Mittelbach's array.sty. See "colortab.doc" for details. + +\item + "LColors", "\LC", "\LCi", "\LCii", "\LCiii", "\LCz", for shading the cells +in the "longtable" environment. See "colortab.doc" for details. +\end{itemize} + +\end{description} + +\subsection{Obsolete but retained features} + + The features listed below are obsolete and are documented in footnotes. + +\begin{itemize} +\item + "\Polar": Use "\SpecialCoor" and "(r;a)" instead. + +\item + "\Cartesian(x,y)" Use "\psset{xunit=x,yunit=y}" instead. + +\item + "\Rput": Use "\uput" instead. + +\item + "\Lput" and "\Mput": Use "\aput", "\bput", "\Aput" and "\Bput" instead. + +\end{itemize} + +\subsection{New features} + +This is a partial listing. See also the next section on new files. + +\begin{itemize} + +\item + "\uput": Replaces "\Rput". + +\item + "\aput", "\bput", "\Aput", "\Bput": Replace "\Lput" and "\Mput". + +\item + "\clipbox" has optional argument "[]" that sets the clippath distance + from box. E.g., "\clipbox[1pt]{foo}". + +\item + "\newpsstyle": E.g., +\begin{LVerbatim} + \newpsstyle{foo}{linewidth=5pt,linestyle=dashed} + \psline[style=foo](4,5) +\end{LVerbatim} + +\item + "\PSTricksOff" suppresses the PostScript. Useful for printing or previewing +drafts of your document with a non-PostScript driver. + +\item + New arrow styles: {\catcode`\<=12 \tt + >-<, <<->>, >>-<<. |*-|* }. + +\item + Many new features for the "\pscustom" command. + +\item + "dimen" parameter (for controlling whether dimensions for "\psframe", +"\pscircle", "\pswedge" and "\psellipse" refer to the inside, outside or +middle of the boundary. + +\item + "bordercolor" parameter. + +\item + "doubleline", "doublesep" and "doublecolor" parameters. + +\item + "ticks" and "labels" parameters, for suppressing ticks and labels with +"\psaxes". + +\item + "shadow" and "shadowangle" parameters. + +\item + Shadow parameters now apply to all graphics objects. + +\item + "\psmathboxtrue", "\psmathboxfalse", for controling whether box + macros preserve math mode. + +\item + "\pslongbox": For making box environment out of box commands. + +\item + "\psverbboxtrue", "\psverbboxfalse": For controlling whether verbatim + text is allowed in box commands. + +\end{itemize} + +\subsection{New files with new stuff} + +\begin{description} + +\item[pst-coil] + Contains "\pscoil", "\psCoil", "\pszigzag", "\nccoil" and "\nczigzag". Uses +"pst-coil.pro" (optionally). + +\item[pst2eps] + Contains "\TeXtoEPS", to make it easier to convert \TeX\ boxes to EPS files +with dvips, and "\PSTtoEPS", for creating EPS files directly from PSTricks +graphics. + +\item[textpath] + Contains "\pstextpath" command, for typesetting text along a path. Use +"textpath.pro". + +\item[gradient] + "gradient" fillstyle. Uses "gradient.pro". + +\item[charpath] + Contains "\pscharpath" command, for stroking and filling character paths. +Also, "\pscharclip" ... "\endpscharclip" sets clipping path as well. + +\item[piecharts.sh] + A sh/awk script by Denis Girou for converting data to PSTricks piecharts. + +\end{description} + +\subsection{Bug fixes} + +This list is incomplete. + +\begin{itemize} + +\item + "\scalebox" and "\scaleboxto" now work when the vertical scaling factor + is less than 1. + +\item + "\lput" and company now work with dvips 4.90 and later. + +\item + "\multips" can now be nested. + +\item + "\psclip" fixed. + +\item + "\clipbox" and clip option for "\pspicture" fixed. + +\end{itemize} + +\subsection{Other changes} + +In some cases, there is a small chance these will require that you modify old +files. + +\begin{itemize} + +\item + Specifying "\rput"'s argument as, e.g., "[.3,1]" rather than +"[br]" is now an undocumented feature. + +\item + All arguments to "\psplot", "\listplot" and "\parametric" plot are passed +on directly as PostScript. + +\item + Dictionaries when including raw PostScript have changed. See appendix of +User's Guide for details. + +\item + "\psset{unit=dim}" always changes "\psunit", "\psxunit" and "\psyunit". To +change only "\psunit", use "runit=dim". + +\item + "border" parameter affects closed curves. + +\item The "hatchsep" parameter now refers to the width of the space between +the lines, rather than the distance between the middle of the lines. +\end{itemize} + +\renewcommand{\EveryVerbatimLine}{} +\renewcommand{\VerbatimFont}{\small\tt} +\renewcommand{\VerbatimFuzz}{2cm} + +\section{VERSION 0.92} + +\subsection{Incompatible changes} + +\begin{Verbatim} + ! V0.91 had two curve interpolation algorithsm: \pscurve and \psdoodle + (and variants). These have been merged into a single algorithm retaining + the names \pscurve, etc. Now the three curvature parameter has three + numbers: + num1 num2 num3 + When num3 is 0 (the default), you get the old \psdoodle algorithm, and + and num1 and num2 act just like the old doodature parameter. When + num3=-1, you get the old \pscurve algorithm, but positive values are + usually nicer. + + If you have used \pscurve or its variants, the shape of the curves + will change under 0.92. If you have also used the curvature + parameter, you will get errors because the old curvature parameter is + a single number and the new curvature parameter consists of 3 numbers. + + If you have used \psdoodle or its variants, then you can either search + and replace doodle->curve and your use of doodature (which had 2 numbers) + to curvature (which has 3 number), or you can put the following in the + customization section of pstricks.con: + \let\psdoodle\pscurve + \let\psedoodle\psecurve + \let\pscdoodle\psccurve + \def\psset@doodature#1{\psset@curvature{#1 0}} + + ! In \psdblframebox: The inner frame now has \pslinewidth, and the outer + frame now has width (dblframewidth x \pslinewidth), where dblframewidth is + a new graphics parameter whose default value is 2. + + ! The angle, angleA and angleB parameters no longer apply to + \ncarc, and the default values have been changed to 0. For + \ncarc, the angle is now controlled by the arcangle, arcangleA + and arcangleB parameters. The default is still 8. + + ! \multido has been off-loaded to the file multido.tex. The syntax has + been changed to make it consistent with \psmultiput and LaTeX's + \multiput: The variable declarations are now the first argument + and the number of repetitions are now the second argument. Also, + for number variables, the initial value and increment must now + have the same number of digits to the right of the decimal, + unless the initial value is an integer. There is no * version. + Instead, the contents is never grouped, and there is even a variant + that doesn't group the whole macro. See multido.ps, which is distributed + with PSTricks, for details. + + ! 'diamond', 'diamond*', and 'x' dotstyles are gone. Use dotangle + parameter instead. +\end{Verbatim} + +\subsection{New features} + +\begin{Verbatim} + + New dot style: |. + + + New graphics objects: \pscustom. + + + New box framing macros: \psovalbox, \pscirclebox. + + + New box scaling macro: \scaleboxto. + + + New nodes: \ovalnode, \circlenode. + + + New node connection: \ncdiagg. + + + New loop macro: \multips. + + + New graphics parameters: dotscale, dotangle, dblframewidth. + + + New arrow styles: c and C. + + + \SpecialCoor allows using nodes as coordinates and mixing + coordinates. +\end{Verbatim} + +\subsection{Other changes} + +\begin{Verbatim} + * arrowscale parameter allows non-square scaling. + + * Documentation has been greatly improved. + + * A bug that caused problems with Arbortext's dvips (previously + listed in pstricks.bug) was fixed. + + * Memory stats with LaTeX's article style: + 43290 words of memory + 2895 multiletter control sequences +\end{Verbatim} + +\section{VERSION 0.91} + +\subsection{Incompatible changes} + +\begin{Verbatim} + ! \dbox and \rotate eliminated. + + ! \psput replaced by \rput, with new syntax: + OLD: \psput[angle](x,y){stuff} + NEW: \rput[ref point]{angle}(x,y){stuff} + \OldPsput sets up \psput with the old syntax (this may disappear some + day; keep it in a safe place if you expect to need it for a long time). + + ! System for specifying angles for nested rotations with \psput has changed. + OLD: p0{angle}, p1{angle}, p2{angle}, etc. + NEW: *angle works like p0{angle}; p1{angle} capability eliminated. + N, S, E and W have same meaning as before. + + ! enddotsize parameter changed to dotsize. + + ! For specifying the origin as the baseline for the \pspicture + environment, leave the optional argument [] empty (rather than + [o]). + + ! B is not allowed as the y-coordinate when setting the reference point + in \rput using coordinates. E.g., [Bl] and [B] are OK, but [.3,B] is + not. + +\end{Verbatim} + +\subsection{New features} + +\begin{Verbatim} + + cornersize parameter added, for specifying whether radius of corners + in \psframe and related box macros is given in relative terms (using + framearc) or absolute terms (using linearc). + + + \psclip and \clipbox macros added. + + + \Cartesian and \Polar commands added, for switching coordinate + systems. + + + border=dim parameter added, for giving appearance of one line + crossing over another. + + + showpoints=bool parameter added. If true, a dot is placed at appropriate + coordinates. + + + \psdots graphics object added. + + + \psarc graphics object added. + + + \parabola graphics object added. + + + \pscurve, \psccurve, \psecurve, \psdoodle, \psedoodle, and \pscdoodle + graphics objects added. + + + \qline and \qdisk graphics objects added. + + + \psplot, \parametericplot and \listplot graphics objects added. + + + node connection (e.g., tree) macros added!! +\end{Verbatim} + +\subsection{Other changes} + +\begin{Verbatim} + * \sunpatch not needed anymore. + + * PostScript header file (if being used) is included at the beginning, + rather than on demand. + + * In spite of the many new features, the input file is smaller in bytes, + and runs significantly faster (at least if used with a header file). + The macros use up slightly more words of memory, and significantly + more command sequences. Here are the stats with LaTeX's article + style: + 41586 words of memory + 2966 multiletter control sequences +\end{Verbatim} + +\section{VERSION 0.9} + +Much internal code was changed, and additional features were added. + +\end{document} +%% END changes.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/chartest.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/chartest.pdf new file mode 100644 index 00000000000..d42fc926130 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/chartest.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/chartest.tex b/Master/texmf-dist/doc/generic/pstricks/examples/chartest.tex new file mode 100644 index 00000000000..cf9a608161a --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/chartest.tex @@ -0,0 +1,25 @@ +%% BEGIN chartest.tex +%% PSTricks test file for charpath.tex. +%% Run with Plain TeX. + +\input pstricks +\input pst-text + +% phvb should be name of Helvetica-Bold tfm or vf file: +\font\bighelv=phvb at 70pt +\bighelv + +\vskip 1in + +\pscharpath[linestyle=dotted]{Denis Girous} + +\vskip 1in + +\pscharpath[fillstyle=crosshatch]{Denis Girous} + +\vskip 1in + +\pscharpath[fillstyle=solid,fillcolor=red]{Denis Girous} + +\bye +%% END chartest.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/denis1.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/denis1.pdf new file mode 100644 index 00000000000..c356d7af123 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/denis1.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/denis1.tex b/Master/texmf-dist/doc/generic/pstricks/examples/denis1.tex new file mode 100644 index 00000000000..2818fcb74f0 --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/denis1.tex @@ -0,0 +1,41 @@ +%% BEGIN denis1.tex +% PSTricks sample that combines +% \pscharpath, \pstextpath, and gradient fillstyle. + +% Run with Plain TeX. + +% Takes a long time to print. + +\hsize 9in +\vsize 6.5in +\special{landscape} % works with Rokicki's dvips. + +\input pstricks +\input pst-text +\input pst-grad + +% phvb should be name of Helvetica-Bold tfm or vf file: +\font\bighelv=phvb at 5in +\font\smallhelv=ptmr at 8pt + +\newcount\mycount +\parindent 0pt + +\null +\vfill + +\pstextpath(0,-8pt)% + {\pscharpath*[linestyle=none,fillstyle=gradient, + gradangle=45,gradmidpoint=.5]{\bighelv D G}}% + {\smallhelv + \mycount=70 + \loop + \advance\mycount -1 + \ifnum\mycount>0 + Denis Girou + \repeat} + +\vfill + +\bye +%% END denis1.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/denis2.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/denis2.pdf new file mode 100644 index 00000000000..b24a0dcde42 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/denis2.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/denis2.tex b/Master/texmf-dist/doc/generic/pstricks/examples/denis2.tex new file mode 100644 index 00000000000..0c5a4f3a4ba --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/denis2.tex @@ -0,0 +1,36 @@ +%% BEGIN denis2.tex +% PSTricks sample that combines +% \pscharpath and \psclip. + +% Run with Plain TeX. + +\hsize 9in +\vsize 6.5in +\special{landscape} % works with Rokicki's dvips. + +\input pstricks +\input pst-text + +% phvb should be name of Helvetica-Bold tfm or vf file: +\font\bighelv=phvb at 5.5in +\font\smallrm=ptmr at 10pt + +\newcount\mycount +\parindent 0pt + +\vglue 1in + +\pscharclip[linewidth=2pt]{\rput[tl](0,0){\bighelv DG}} + \rput[t]{45}(0,0){\vbox{% + \hsize 12in + \smallrm + \mycount=1000 + \loop + \advance\mycount -1 + \ifnum\mycount>0 + Denis Girou + \repeat}} +\endpscharclip + +\bye +%% END denis2.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/filetest.dat b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.dat new file mode 100644 index 00000000000..68945e6e95e --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.dat @@ -0,0 +1,71 @@ +%% BEGIN filetest.dat +[ +{{0, 0}, {0.1, 0.489217}, {0.2, 0.914933}, + + {0.3, 1.21952}, {0.4, 1.35655}, {0.5, 1.29517}, + + {0.6, 1.02301}, {0.7, 0.547479}, {0.8, -0.104732}, + + {0.9, -0.889868}, {1., -1.75088}, {1.1, -2.62238}, + + {1.2, -3.4364}, {1.3, -4.12831}, {1.4, -4.64256}, + + {1.5, -4.93756}, {1.6, -4.98935}, {1.7, -4.7937}, + + {1.8, -4.36653}, {1.9, -3.74246}, {2., -2.97178}, + + {2.1, -2.11599}, {2.2, -1.24239}, {2.3, -0.418164}, + + {2.4, 0.295512}, {2.5, 0.84882}, {2.6, 1.2076}, + + {2.7, 1.35627}, {2.8, 1.29903}, {2.9, 1.0593}, + + {3., 0.677496}, {3.1, 0.207184}, {3.2, -0.289882}, + + {3.3, -0.749475}, {3.4, -1.11083}, {3.5, -1.32228}, + + {3.6, -1.34604}, {3.7, -1.16179}, {3.8, -0.768677}, + + {3.9, -0.185544}, {4., 0.550574}, {4.1, 1.38761}, + + {4.2, 2.263}, {4.3, 3.1091}, {4.4, 3.85919}, + + {4.5, 4.45329}, {4.6, 4.84347}, {4.7, 4.99808}, + + {4.8, 4.90456}, {4.9, 4.5705}, {5., 4.02303}, + + {5.1, 3.30639}, {5.2, 2.47802}, {5.3, 1.60352}, + + {5.4, 0.750856}, {5.5, -0.0156125}, {5.6, -0.640751}, + + {5.7, -1.08345}, {5.8, -1.32014}, {5.9, -1.34676}, + + {6., -1.17893}, {6.1, -0.850365}, {6.2, -0.409711}, + + {6.3, 0.084022}, {6.4, 0.566914}, {6.5, 0.97605}, + + {6.6, 1.25533}, {6.7, 1.36069}, {6.8, 1.2642}, + + {6.9, 0.956782}, {7., 0.449173}, {7.1, -0.228866}, + + {7.2, -1.03104}, {7.3, -1.89854}, {7.4, -2.76511}, + + {7.5, -3.56294}, {7.6, -4.22854}, {7.7, -4.70839}, + + {7.8, -4.96365}, {7.9, -4.97357}, {8., -4.73734}, + + {8.1, -4.27417}, {8.2, -3.62157}, {8.3, -2.83204}, + + {8.4, -1.96848}, {8.5, -1.09857}, {8.6, -0.288905}, + + {8.7, 0.400909}, {8.8, 0.92342}, {8.9, 1.24743}, + + {9., 1.36064}, {9.1, 1.27057}, {9.2, 1.00372}, + + {9.3, 0.602995}, {9.4, 0.123725}, {9.5, -0.371511}, + + {9.6, -0.818656}, {9.7, -1.1581}, {9.8, -1.34019}, + + {9.9, -1.32988}, {10., -1.11003}} +] +%% END filetest.dat diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/filetest.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.pdf new file mode 100644 index 00000000000..dac3755ff38 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/filetest.raw b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.raw new file mode 100644 index 00000000000..69a459f7e7d --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.raw @@ -0,0 +1,6 @@ +%% BEGIN filetest.raw +% test of \rawfile, with testfile.tex +0 0 moveto +100 100 lineto +100 0 lineto +%% END filetest.raw diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/filetest.tex b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.tex new file mode 100644 index 00000000000..52ac7732d2b --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/filetest.tex @@ -0,0 +1,84 @@ +%% BEGIN filetest.tex +% +% This is test file for some of the PSTricks commands that +% read from and write to files. +% +% Run with plain tex. +% +% You must have the epsf.tex macros, which are distributed with +% Rokicki's dvips, and change the reference to \epsf below. +% +% This inputs filetest.raw, filetest.dat and filetest.eps. +% It also write filetest.eps. +% +% If using Rokicki's dvips v5.47 or later, try +% +% dvips filetest -E-o +% +% to create an eps file filetest.ps from the whole picture. + +\input pstricks +\input pst-eps +\input pst-plot +\input epsf + +\TeXtoEPS % Make an EPS picture out of .dvi file, with dvips -E. + \pspicture(-5,-10)(10,10) + + % Test two similar ways to use data from a file: + % \fileplot + \AltClipMode + \psclip{\psframe[linestyle=none](0,-10)(10,10)} + \pscustom{% + \fileplot{filetest.dat} + \gsave + \lineto(100,100) + \lineto(0,100) + \closedshadow + \grestore} + \endpsclip + + \psaxes(0,0)(-5,-10)(10,10) + + % And \readdata and \dataplot: + \readdata\mydata{filetest.dat} + \dataplot[plotstyle=dots,swapaxes=true]{\mydata} + + % Save some data: + + \savedata{\total}[ + {{0,163},{1,187},{2,166},{3,232},{4,237},{5,201},{6,196},{7,203}}] + \savedata{\general}[ + {7,193}{6,182}{5,167}{4,153}{3,129}{2,108}{1,101}{0,104}] + + % Now make an EPS file from the graphics objects: + \PSTtoEPS[bbury=5cm,bburx=10.5cm, + bblly=2cm,bbllx=0cm,makeeps=all]{filetest.eps}{% + + % Now when I concatenate \total and \general, I get the points that + % delineate the boundary for the area you want to fill. + + \psyunit=.02cm + \psxunit=1.5cm + + \pscustom[plotstyle=curve,linestyle=none,fillstyle=solid, + fillcolor=gray]{\listplot{\general}\listplot[liftpen=1]{\total}} + \psset{plotstyle=curve,showpoints=true,dotscale=1.5} + \listplot[dotstyle=pentagon*]{\total} + \listplot[dotstyle=triangle]{\general} + } % end \PSTtoEPS + + % Now use the EPS file just created: + \rput[bl](-1,-10){\psdblframebox{\epsffile{filetest.eps}}} + + % Now try inputting raw ps code with \pscustom: + \pscustom[shadowsize=5pt,origin={5,4}]{% + \file{filetest.raw} + \closepath + \closedshadow} + + \endpspicture +\endTeXtoEPS + +\bye +%% END filetest.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/pst-test.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/pst-test.pdf new file mode 100644 index 00000000000..947988f698c Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/pst-test.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/pst-test.tex b/Master/texmf-dist/doc/generic/pstricks/examples/pst-test.tex new file mode 100644 index 00000000000..890af15b8fc --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/pst-test.tex @@ -0,0 +1,126 @@ +%%%%%%%%%%%%%%%%%%% pst-test.tex %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% Test file for pstricks.tex, v0.93 and maybe later versions. +%% +%% Run with Plain TeX. +%% +%% PAGE 1: Pure graphics objects. These us \pstunit and \pstverb. +%% +\input pstricks +\input pst-node + +\newpsobject{mygrid}{psgrid}{subgriddiv=1,griddots=10,gridlabels=7pt} +\hbox{}\vfill + +\pspicture(-1,-1)(9,2)\mygrid +\psline[linewidth=1.5pt,linestyle=dotted]{**-)}(2.5,1.5) +\psline[linewidth=2pt,linestyle=dashed, + linearc=.5,linecolor=gray]{|->}(3,-.5)(5.5,1.8)(7,-1) +\qline(9,-1)(8,2) +\endpspicture + +\vfill + +\pspicture(-1,-1)(9,2)\mygrid +\qdisk(0,0){1} +\pswedge[linecolor=gray,fillstyle=solid]{.8}{0}{70} +\pscircle[linewidth=2pt,linestyle=dashed](4,.5){1.5} +\psellipse[fillstyle=crosshatch*,fillcolor=lightgray] + (7.5,.5)(1,1.5) +\endpspicture + +\vfill + +\pspicture(-1,-1)(9,3)\mygrid +\parabola*(0,0)(1,3) +\parabola[xunit=.01]{<->}(900,3)(600,-1) +\endpspicture + +\vfill + +\eject + +%% PAGE 2: Color (using \pstVerb) and rotation (using \pstVerb and \pstrotate). + +\hbox{}\vfill + +Here is {\gray some gray text } + +\vskip 1cm +Here is a lightgray line:{\lightgray \hrulefill} + +\vskip 1cm +And a dark gray blob: + +{\darkgray \hrule height 1cm width 5 cm } +\vfill + +\centerline{ +\rotateleft{Left} \rotatedown{Down} \rotateright{Right} +\psscalebox{2}{Big} \psscalebox{1 -1}{Flip}} + +\vfill + +\rput[l]{-45}{This runs diagonally down and to the right} +\rput{45}(2in,0){This runs up to the right} + +\vfill + +\eject + +%% PAGE 3: Nodes and node connections. These use \pstVerb, \pstverbscale, +%% and maybe \pstrotate. + +\null +\vfill + +$$ +\matrix{% + &\rnode{a}{A}\cr + \noalign{\vskip 2cm}% + \rnode{b}{B}\qquad&\rnode{c}{C}\cr} +\psset{nodesep=3pt} +\everypsbox{\scriptstyle} +\ncline{->}{a}{b}\Bput{f} +\ncline{->}{a}{c}\Aput{g} +\ncline[linestyle=dotted]{->}{b}{c}\Aput{h} +$$ + +\vfill + +\vskip 2cm + +\cnode*(0,0){3pt}{A} +\cnode*(4,2){3pt}{B} +\ncline[nodesep=3pt]{A}{B} +\mput*{1} + +\vfill + +\pspicture(0.4,.2)(9.8,6.2) + \rput(2,6){\rnode{G}{\psframebox{GOAT}}} + \rput(2,.5){\rnode{I}{\psframebox{GOAT}}} + \ncangles[angleA=90, angleB=180, nodesepB=3pt, linearc=3pt, + armA=2cm]{<-**}{I}{G} + \lput*(2.5){Doom} + \aput(.5){Zoom} + \SpecialCoor + \rput{10}(7;30){\rnode{A}{\psframebox{Polar Coor}}} + \rput(5;10){\rnode{B}{\psframebox{Polar Coor}}}% + \ncline{->}{A}{B} + \mput{\pnode{Y}} + \cnodeput[linewidth=1.5pt](9.5,6){H}{H} + \cnodeput[linewidth=1.5pt](8,1){M}{M} + \newpsobject{myarc}{ncarc}{nodesep=3pt,offset=2pt,arrows=->} + \myarc{H}{M} + \mput*{r} + \myarc{M}{H} + \mput*{l} + \lput(.75){\pnode{Z}} + \nccurve[angle=135, ncurv=1.8]{Y}{Z} + \aput{:U}{Doom} +\endpspicture + +\vfill + +\bye +%% END pst-test.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/samples.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/samples.pdf new file mode 100644 index 00000000000..18cf8a44824 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/samples.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/samples.tex b/Master/texmf-dist/doc/generic/pstricks/examples/samples.tex new file mode 100644 index 00000000000..57b8ad0d8ac --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/samples.tex @@ -0,0 +1,443 @@ +%% samples.pst : PSTricks samples. Run with LaTeX. +%% Last edited: 93/03/03 + +\documentclass[11pt,a4paper]{article} + +\makeatletter + +%% INPUT FANCYBOX.STY HERE TO CHECK FILE VERSION. + +\usepackage[T1]{fontenc} +\usepackage[dvips]{geometry} +\geometry{tmargin=2cm,bmargin=3.3cm,headheight=20pt,headsep=10pt, +textheight=9in, footskip=.625in} +\usepackage[scaled]{luximono} +\usepackage{mathpazo} +\usepackage{pstricks,pst-node,pst-coil,fancybox} + +\let\Ldots\ldots +\def\ldots{\mbox{$\Ldots$}} % In case we're using AmS-LaTeX. +\makeatletter +\def\ps@samples{% + \def\@oddhead{\bf PSTricks samples \hfill \thepage}% + \def\@oddfoot{}} +\makeatother +\pagestyle{samples} + +\newbox\sample + +\def\example{\setbox\sample\vbox\bgroup} +\def\endexample{% + \egroup + \vbox{\vskip 1cm + \hbox{\psframebox[boxsep=false,linewidth=2pt,linearc=.5cm,framesep=.5cm, + cornersize=absolute]{\box\sample}} + \vskip 1cm}} +\def\rquote#1{{\begin{quote}\vskip-\topsep + \raggedright\hskip -2em#1\end{quote}}} +\def\creator#1{\rquote{{\bf Creator:}\hskip 1em#1}} +\def\title#1{\rquote{{\bf Description:}\hskip 1em#1}} + +\def\N#1{{\tt\string#1}} + +\begin{document} + +\begin{example} + \creator{Gisli Ottarsson \tt } + \title{Calvin and Hobbes} + + $$ + \pspicture(-3.,29)(3.,38) + \def\anglei{5} + \def\angleii{-5} + \psset{linewidth=1pt,hatchwidth=0.8pt} + \def\tower#1{% + \psline[linewidth=2pt](0,0)(0,7) + \psset{fillstyle=solid,dimen=middle,linewidth=1.5pt} + \cnode(0,2){.5}{A#1} + \cnode(0,5){.8}{B#1} + \cnode(0,7){.5}{C#1} + \psset{linestyle=solid,linewidth=1pt} + \psline{->}(0,1)(2,1) + \SpecialCoor + \rput([angle=90]B#1){\psline{->}(2,0)} + \rput([angle=90]C#1){\psline{->}(2,0)}}% + \pscustom[linewidth=2pt]{% + \psarc(0,0){30}{80}{100} + \gsave + \psarcn(0,0){29.25}{100}{80} + \fill[fillstyle=vlines] + \grestore} + \rput{\anglei}{\rput(0,30){% + \psset{fillcolor=lightgray} + \tower{1}}} + \rput{\angleii}{\rput(0,30){% + \psset{linestyle=dashed} + \tower{2}}} + \psset{linewidth=1.5pt,coilwidth=.45} + \nczigzag{B1}{A2} + \aput[.25](.85){$k_{c_3}$} + \ncline[linecolor=white,linewidth=.6]{A1}{B2} + \nczigzag{A1}{B2} + \bput[.3](.85){$k_{c_3}$} + \nczigzag{A1}{A2} + \bput[.3](.5){$k_{c_1}$} + \nczigzag{B1}{B2} + \aput[.3](.5){$k_{c_2}$} + \endpspicture + $$ +\end{example} + +\begin{example} + \creator{\tt{leecheng@liapunov.eecs.umich.edu}} + \title{Dripping faucet model.} + + \psset{unit=.4cm} + \begin{center} + \begin{pspicture}(0,-2)(31,12) + \rput(1.5,0){% + \psellipse[linewidth=1pt](8,7)(1,3) + \psframe[linecolor=white,fillstyle=solid,fillcolor=white] + (6.4,6.5)(8,7.5) + \psline[linearc=.3,linewidth=1pt](8,8)(8,7.5)(4,7.5) + \psbezier[linewidth=1pt](4,7.5)(3,7.5)(3,6.5)(3,5.5) + \psline[linearc=.3,linewidth=1pt](8,6)(8,6.5)(5,6.5) + \psbezier[linewidth=1pt](5,6.5)(4,6.5)(4,6.5)(4,5.5) + \psline[linewidth=1pt](3,5.5)(4,5.5) + \psline[linearc=.3,linewidth=1pt](5,7.5)(5,8)(6,8)(6,7.5) + \psframe[linewidth=1pt](5.3,8)(5.7,8.7) + \psframe[linewidth=1pt,framearc=1,fillstyle=solid, + fillcolor=white](4,8.7)(7,9) + \multirput(3.5,4.8)(0,-1){4}{% + \psbezier[linewidth=.5pt](0,0)(.25,-.4)(-.25,-.4)(0,0)} + \rput[t](5.5,0){Dripping Faucet}} + \rput(20,5){% + \pspolygon[linecolor=white,fillstyle=vlines, + fillcolor=darkgray,hatchsep=.2](1,4.5)(1,4)(4,4)(4,4.5) + \psline[linewidth=2pt](1,4)(4,4) + \psline[linewidth=1.5pt](2.5,4)(2.5,3.5)(2.9,3.3)(2.1,2.9) + (2.9,2.5)(2.1,2.1)(2.9,1.7)(2.1,1.3)(2.5,1.1)(2.5,0.6) + \psframe[linecolor=black,linewidth=1.5pt,fillstyle=solid, + fillcolor=lightgray](1.8,-1)(3.2,.6) + \rput(2.5,-.2){$M$} + \psline{<->}(3.7,-.9)(3.7,.5) + \psframe[linecolor=black,linewidth=1.5pt,fillstyle=solid, + fillcolor=lightgray](1.8,-3.5)(3.2,-1.9) + \rput(2.5,-2.7){$m$} + \psline{->}(5,1)(5,-1) + \rput[l](5.5,0){$g$} + \psline{->}(3.7,-2)(3.7,-3.4) + \rput[t](2.5,-4){Mathematical Model for} + \rput[t](2.5,-5){a Dripping Faucet} + \rput(-6,-2){% + \psset{linewidth=2pt} + \psline(0,.5)(2,.5) + \psline(0,-.5)(2,-.5) + \psline(1.5,1)(2.5,0)(1.5,-1)}} + \psframe[linewidth=2pt,framearc=.05,linecolor=gray](0,-2.5)(31,12) + \end{pspicture} + \end{center} +\end{example} + +\begin{example} + \creator{\tt{Christian Schytt }} + \title{Primal and dual.} + + \hbox to \hsize{% + % DUAL + \psset{linewidth=0.5pt} + \pspicture(-2,-1)(6,5) + \psline{->}(5,0)\psline{->}(0,4) + % + \qdisk(2,0){2pt} + \rput(2,0){\pnode{Z}} + \uput[dl](2,0){$c_{ij}$} + % + \uput[d](5,0){$p_i-p_j$} + \uput[r](0,4){\parbox{2cm}{Dual cost \\ of arc $(i,j)$}} + \uput[l](0,4){$q_{ij}(p_i-p_j)$} + % + \rput(.5,1.5){\pnode{U}} + \rput(2.5,-1.5){\pnode{V}} + \ncline{Z}{U}\mput{\pnode{X}} + \ncline{Z}{V}\mput{\pnode{Y}} + % + \rput[b](2,2){\rnode{A}{Slope: ${}-l_{ij}$}} + \ncline{->}{A}{X} + \rput[b](0,-0.75){\rnode{B}{Slope: ${}-u_{ij}$}} + \ncline{->}{B}{Y} + \endpspicture\hfill + % PRIMAL + \pspicture(0,-1)(6,5) + \psline{->}(5,0)\psline{->}(0,4) + \qdisk(1.5,0){2pt} + \qdisk(3.5,0){2pt} + \uput[d](1.5,0){$l_{ij}$} + \uput[d](3.5,0){$u_{ij}$} + \uput[d](5,0){$f_{ij}$} + \uput[r](0,4){\parbox{2cm}{\raggedright Primal cost \\ of arc $(i,j)$}} + % + \rput(1.5,1){\pnode{A}} + \rput(3.5,2){\pnode{B}} + \ncline{-}{A}{B}\mput{a\pnode{Y}} + % + \psline[linestyle=dashed]{-}(1.5,0)(1.5,3) + \psline[linestyle=dashed]{-}(3.5,0)(3.5,3) + % + \rput[l](4,1){\rnode{X}{Slope: $c_{ij}$}} + \ncline{->}{X}{Y} + \endpspicture + }\medskip +\end{example} + +\begin{example} + \creator{Gisli Ottarsson \tt } + + \begin{center} + \psset{unit=1in,linewidth=1pt,hatchwidth=0.8pt} + \pspicture(1,0)(5.,3) + \psline[linewidth=2pt,arrowscale=1.5]{->}(1.5,2.4)(3.5,2.4) + \psellipse[fillcolor=darkgray,fillstyle=solid](1.5,1.5)(.5,1.3) + \psellipse[fillcolor=white,fillstyle=solid](1.4,1.5)(.5,1.3) + \psline(1.5,2.8)(1.4,2.8) + \psline(1.5,0.2)(1.4,0.2) + \psline[linewidth=1.5pt,linestyle=dashed](1.3,2.4)(1.7,2.4) + \pscircle*(1.3,2.4){3pt} + \rput(1.3,2.2){$(r_o,\theta_o)$} + \rput(3.3,2.65){$u(r_o,\theta_o)$} + \psline[linewidth=2pt,arrowscale=1.5]{|->}(2.5,0.65)(4.5,0.65) + \rput(4.5,0.85){$w(x_o)$} + \psline{<->}(1.93,1.0)(2.5,.65) + \rput(2.2,.65){$x_o$} + \pscircle[fillcolor=lightgray,fillstyle=solid](1.93,1.2){0.05} + \pspolygon[fillcolor=lightgray,fillstyle=solid,linecolor=lightgray] + (1.935,1.24)(3.5,.38)(3.5,.22)(1.935,1.16) + \pscircle[fillcolor=lightgray,fillstyle=solid](2.53,0.855){0.058} + \pscircle[fillcolor=lightgray,fillstyle=solid,linecolor=lightgray] + (2.545,0.845){0.056} + \pscircle[fillcolor=gray,fillstyle=solid](3.5,.3){0.08} + \psline(1.93,1.245)(3.5,.38) + \psline(3.5,.22)(1.92,1.156) + \endpspicture + \end{center} +\end{example} + + +\begin{example} +\creator{tvz} +\title{Another example of \N\pspolygon. The coordinates where determined + using \N\psgrid, after making the table.\label{ex-pspolygon}} + +\begin{center} + \def\arraystretch{2}\tabcolsep=10pt\small\bf + {\em Result is true for values in shaded region:}\\[5pt] + \pspolygon[linearc=.4,fillcolor=lightgray,fillstyle=solid] + (3,2)(5.9,2)(5.9,0)(7.4,0)(7.4,-2)(1.45,-2)(1.45,0)(3,0) + \begin{tabular}{cccccc} + X11 & X12 & X13 & X14 & X15 & X16\\ + X21 & X22 & X23 & X24 & X25 & X26\\ + X31 & X32 & X33 & X34 & X35 & X36\\ + X41 & X42 & X43 & X44 & X45 & X46 +\end{tabular} +\end{center} + +\end{example} + + +\begin{example} + \creator{tvz} + \title{Nodes.\label{ex-nodes1}} + + \begin{center} + \begin{pspicture}(0,-1)(8,3) + \psset{arrows=->, nodesep=6pt} + \rput(3,3){\rnode{A}{Returns to Scale}} + \rput(1,1){\rnode{B}{Production}} + \rput(5,1){\rnode{C}{Managing}} + \rput(3,-1){\rnode{D}{Supervision}} + \rput(7,-1){\rnode{E}{Information Processing}} + \ncline{A}{B} \ncline{A}{C} \ncline{C}{D} \ncline{C}{E} + \end{pspicture} + \end{center} +\end{example} + + +\begin{example} + \creator{tvz} + \title{Another example of nodes.\label{ex-nodes3}} + + \begin{center} + \begin{pspicture}(0,-1)(7.5,1) + \pnode{a} + \cnodeput(1.5,0){b}{0} + \cnodeput(3,0){c}{1} + \cnodeput(4.5,0){d}{2} + \cnodeput(6,0){e}{3} + \scriptsize + \psset{arrows=->,nodesep=0} + \pslabelsep=3pt + \ncline{a}{b}\Aput{start} + \ncline{b}{c}\Bput{a} + \ncline{c}{d}\Aput{b} + \ncline{d}{e}\Aput{b} + \psset{arm=.6,linearc=.4,angleA=0,angleB=90} + \ncangles{b}{b}\Aput{b} + \ncangles{e}{b}\Aput{b} + \psset{angleB=-90} + \ncangles{c}{c}\Bput{a} + \ncangles{d}{c}\Bput{a} + \ncangles{e}{c}\Bput{a} + \end{pspicture} + \end{center} +\end{example} + +\begin{example} + \creator{tvz} + \title{Nonsense examples of nodes.\label{ex-nodes4}} + + The tempestuous \rnode{E}{Maggie} and her alcoholic husband + \rnode{A}{Brick} \ldots + \vskip 2cm + \cnode*{3pt}{D}\hskip 1em Much Ado about \rnode{B}{Nothing}. + \vskip 1in + and \rnode{J}{\psframebox{another}} another + \rnode{K}{\psframebox{another}} another another \rnode{C}{book} + \ncline[linecolor=darkgray,linewidth=1.5pt,nodesep=3pt]{->}{A}{B} + \ncline[nodesep=3pt,linestyle=dashed,border=3pt]{->}{C}{E} + \ncangle[nodesep=1pt,angleA=-90,angleB=150, armB=3cm]{D}{C} + \ncbar[angle=90]{<-oo}{J}{K} +\end{example} + + +\begin{example} + \creator{tvz} + \title{More node nonsense.\label{ex-nodes5}} + + \begin{center} + \begin{pspicture}(0.4,.2)(9.8,6.2) + \rput(2,6){\rnode{G}{\psframebox{GOAT}}} + \rput(2,.5){\rnode{I}{\psframebox{GOAT}}} + \ncangles[angleA=90, angleB=180, nodesepB=3pt, linearc=3pt, + armA=2cm]{<-**}{I}{G} + \lput*(2.5){Doom} + \bput(.5){Zoom} + \SpecialCoor + \rput{10}(7;30){\rnode{A}{\psframebox{Polar Coor}}} + \rput(5;10){\rnode{B}{\psframebox{Polar Coor}}} + \ncline{->}{A}{B} + \mput{\pnode{Y}} + \cnodeput[linewidth=1.5pt](9.5,6){H}{H} + \cnodeput[linewidth=1.5pt](8,1){M}{M} + \newpsobject{myarc}{ncarc}{nodesep=3pt,offset=2pt,arrows=->} + \myarc{H}{M}\mput*{r} + \myarc{M}{H}\mput*{l}\lput(.75){\pnode{Z}} + \nccurve[angleA=135, angleB=135, ncurv=1.8]{Z}{Y}\bput{:D}{Doom} + \end{pspicture} + \end{center} +\end{example} + +\begin{example} + \creator{tvz} + \title{} + + \[ + \def\arraystretch{3.5} + \arraycolsep .7cm + \begin{array}{ccc} + \rnode{a}{U}\\ + & \rnode{b}{X\times_Z Y} & \rnode{c}{X}\\ + & \rnode{d}{Y} & \rnode{e}{Z} + \end{array} + \psset{arrows=->,nodesep=3pt} + \pslabelsep 3pt + \everypsbox{\scriptstyle} + \ncLine{a}{b}\Bput{y} + \ncLine{a}{c}\Aput{x} + \ncLine{b}{d}\Bput{q} + \ncLine{b}{c}\Bput{p} + \ncLine{c}{e}\Aput{f} + \ncLine{d}{e}\Bput{g} + \] +\end{example} + +\begin{example} + \creator{tvz} + \title{Several ways to connect nodes to themselves} + + \def\arrow(#1,#2){\ncline{->}{#1}{#2}} + $$ + \begin{array}{c@{\hskip 1.5cm}c@{\hskip 1.5cm}c} + \rnode{a}{\bullet} & \rnode{b}{\bullet} & \rnode{c}{\bullet}\\[1cm] + \end{array} + \everypsbox{\scriptstyle} + \psset{nodesep=5pt,arm=.6,linearc=.4,angleA=0,angleB=90} + \ncangles{->}{a}{a} + \ncangles{->}{b}{b} + \ncangles{->}{c}{c} + \arrow(a,b) + \arrow(b,c) + \ncarc[arcangleA=-30, arcangleB=-30]{->}{a}{c} + $$ + $$ + \everypsbox{\scriptstyle} + \def\cn#1#2{% + \cnode*{2pt}{#1} + \ncloop[arm=.4,linearc=.39,loopsize=.8,nodesep=5pt,angleB=180] + {->}{#1}{#1} + \Bput{#2}} + \begin{array}{c@{\hskip 1.5cm}c@{\hskip 1.5cm}c} + \cn{a}{1} & \cn{b}{2} & \cn{c}{3}\\[1cm] + \end{array} + \psset{nodesep=5pt,arm=.6,linearc=.4}\arrow(a,b) + \arrow(b,c) + \ncarc[arcangleA=-30, arcangleB=-30]{->}{a}{c} + $$ + $$ + \everypsbox{\scriptstyle} + \def\cn#1#2{% + \cnode*{2pt}{#1} + \nccircle[nodesep=5pt]{->}{#1}{.5} + \Bput{#2}} + \begin{array}{c@{\hskip 1.5cm}c@{\hskip 1.5cm}c} + \cn{a}{1} & \cn{b}{2} & \cn{c}{3}\\[1cm] + \end{array} + \psset{nodesep=5pt,arm=.6,linearc=.4}\arrow(a,b) + \arrow(b,c) + \ncarc[arcangleA=-30, arcangleB=-30]{->}{a}{c} + $$ +\end{example} + +\begin{example} + \creator{tvz} + \title{} + +\centerline{% + \rnode{a}{\psframebox{\Huge A connection}}% + \hskip 1.6cm + \rnode{b}{\psframebox{\Huge Unto another}}} +\ncloop[loopsize=-1cm,arm=.8cm,linearc=.3]{->}{a}{b} +\end{example} + + +\begin{example} + \creator{tvz} + \title{} + + \newbox\mybox + \setbox\mybox=\hbox{% + \psset{unit=4pt} + \pspicture(-2.8,0)(2.8,7.75) + \psset{linewidth=.1} + \psline(-.3,0)(-.3,3) + \psline(.3,0)(.3,3) + \psline(-2,0)(2,0) + \rput{45}(0,2){% + \psframe[framearc=.1,fillstyle=solid](0,0)(4,4) + \psline[linewidth=.4,linearc=.2](1.5,.4)(.4,2.5)(3.6,1.5)(2.5,3.6)} + \psdots[dotstyle=square,dotsize=.4 0](0,7.5) + \endpspicture}% + \centerline{\copy\mybox\hskip 1pt\copy\mybox} +\end{example} + +\end{document} + diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/tp-test.pdf b/Master/texmf-dist/doc/generic/pstricks/examples/tp-test.pdf new file mode 100644 index 00000000000..2e2db9df0e5 Binary files /dev/null and b/Master/texmf-dist/doc/generic/pstricks/examples/tp-test.pdf differ diff --git a/Master/texmf-dist/doc/generic/pstricks/examples/tp-test.tex b/Master/texmf-dist/doc/generic/pstricks/examples/tp-test.tex new file mode 100644 index 00000000000..355851eee33 --- /dev/null +++ b/Master/texmf-dist/doc/generic/pstricks/examples/tp-test.tex @@ -0,0 +1,72 @@ +%% BEGIN tp-test.tex +%% +%% LaTeX test file for textpath.tex/textpath.sty. +%% +%% To use PostScript fonts with the New Font Selection Scheme: +%% - Include the style option "npsfont". +%% - You may have to change the font file names given below. +%% - "npsfont.sty" is distributed with PSTricks. + +\documentclass[11pt,a4paper]{article} + +\makeatletter + +%% INPUT FANCYBOX.STY HERE TO CHECK FILE VERSION. + +\usepackage{fancybox} +\usepackage[T1]{fontenc} +\usepackage[dvips]{geometry} +\geometry{tmargin=2cm,bmargin=3.3cm,headheight=20pt,headsep=10pt, +textheight=9in, footskip=.625in} +\usepackage[scaled]{luximono} +\usepackage{mathptmx} +\usepackage{pstricks,pst-text} + +\begin{document} +The first sample shows that math works. I let the line be drawn to make the sample clearer. +\begin{verbatim} + \large + \pstextpath[c]% + {\pscurve[linecolor=gray](0,1)(4,3)(6,2)(9,0)(12,1)(15,1)}% + {$S_\alpha=\Omega(\gamma_\beta)$ is a connected snarf and + $B=(\otimes,\rightarrow,\theta)$ is Boolean left subideal.} +\end{verbatim} + +\vskip 3.5cm + +\begin{large} + \pstextpath[c]% + {\pscurve[linecolor=gray](0,1)(4,3)(6,2)(9,0)(12,1)(15,1)}% + {$S_\alpha=\Omega(\gamma_\beta)$ is a connected snarf and + $B=(\otimes,\rightarrow,\theta)$ is Boolean left subideal.} +\end{large} + +\vskip 1cm + +\begin{verbatim} + \psset{linestyle=none} + \pstextpath[c]{\psarcn(0,0){73pt}{180}{0}}% + {Centre National de la} + \pstextpath[c]{\psarc(0,0){73pt}{180}{0}}% + {Recherche Scientifique} +\end{verbatim} + +\begin{center} + \vskip 2cm + \Huge + \psset{linestyle=none} + \pstextpath[c]{\psarcn(0,0){73pt}{180}{0}}% + {Centre National de la} + \pstextpath[c]{\psarc(0,0){73pt}{180}{0}}% + {Recherche Scientifique} + \vskip 2cm +\end{center} + +\begin{center} + \pstextpath[c](0,0){\psarcn[linestyle=none](0,-6){4}{180}{0}}% + {\parbox{3.5in}{In principle, it is possible to use + parbox, but let's see what really happens. It seems + hard to believe that someone would want to do this.}} +\end{center} +\end{document} +%% END tp-test.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/psd-3d.tex b/Master/texmf-dist/doc/generic/pstricks/psd-3d.tex deleted file mode 100644 index 9837db6e91f..00000000000 --- a/Master/texmf-dist/doc/generic/pstricks/psd-3d.tex +++ /dev/null @@ -1,12 +0,0 @@ -%% BEGIN psd-3d.tex - -\part{Three Dimensional Graphics\label{P-threeD}} - -\Section{Overview} - -\File{pst-3d} -The... - -\endinput - -%% END psd-3d.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/psd-basi.tex b/Master/texmf-dist/doc/generic/pstricks/psd-basi.tex deleted file mode 100644 index 0d9f5ccea8b..00000000000 --- a/Master/texmf-dist/doc/generic/pstricks/psd-basi.tex +++ /dev/null @@ -1,648 +0,0 @@ -%% BEGIN psd-basi.tex - -\part{Basic graphics objects\label{P-graphics}} - -\Section{Lines and polygons\label{S-lines}} - -The objects in this section also use the following parameters: -\begin{description} - \pitem[linearc=dim] The radius of arcs drawn at the corners of lines by the - \n\psline{} and \n\pspolygon{} graphics objects. should be positive. - \pitem[framearc=num] In the \n\psframe{} and the related box framing macros, - the radius of rounded corners is set, by default, to one-half times - the width or height of the frame, whichever is less. should be between - 0 and 1. - \pitem[cornersize=relative/absolute] If \p{cornersize} is "relative", then - the \p{framearc} parameter determines the radius of the rounded corners for - \n\psframe, as described above (and hence the radius depends on the size of - the frame). If \p{cornersize} is "absolute", then the \p{linearc} parameter - determines the radius of the rounded corners for \n\psframe{} (and hence the - radius is of constant size). -\end{description} - - -Now here are the lines and polygons: -\begin{description} - -\oitem \psline`{arrows}(\x0,\y0)'(\x1,\y1)`\ldots(\x n,\y n)' - - This draws a line through the list of coordinates. For example: -\begin{MEx*}(4,2) - \psline[linewidth=2pt,linearc=.25]{->}(4,2)(0,1)(2,0) -\end{MEx*} - -\mitem \qline(coor0)(coor1) - - This is a streamlined version of \n\psline{} that does not pay attention to -the \p{arrows} parameter, and that can only draw a single line segment. Note -that both coordinates are obligatory, and there is no optional argument for -setting parameters (use \n\psset{} if you need to change the \p{linewidth}, or -whatever). For example: -\begin{MEx*}(2,1) - \qline(0,0)(2,1) -\end{MEx*} - -\oitem \pspolygon`(\x0,\y0)'(\x1,\y1)(\x2,\y2)`\ldots(\x n,\y n)' - - This is similar to \n\psline, but it draws a closed path. For example: -\begin{MEx*}(4,2) - \pspolygon[linewidth=1.5pt](0,2)(1,2) - \pspolygon*[linearc=.2,linecolor=darkgray](1,0)(1,2)(4,0)(4,2) -\end{MEx*} - -\oitem \psframe`(\x0,\y0)'(\x1,\y1) - - \n\psframe{} draws a rectangle with opposing corners \c0 and \c1. For -example: -\begin{MEx*}(4,2) - \psframe[linewidth=2pt,framearc=.3,fillstyle=solid, - fillcolor=lightgray](4,2) - \psframe*[linecolor=white](1,.5)(2,1.5) -\end{MEx*} - -\oitem \psdiamond`\c0'\c1 - - \n\psdiamond{} draws a diamond centered at \c0, and with the half width and -height equal to \x1\ and \y1, respectively. -\begin{MEx*}(4,2) - \psdiamond[framearc=.3,fillstyle=solid, - fillcolor=lightgray](2,1)(1.5,1) -\end{MEx*} - -The diamond is rotated about the center by -\begin{Ex} - \Par{gangle=gangle} -\end{Ex} - -\oitem \pstriangle`\c0'\c1 - - \n\pstriangle{} draws an isosceles triangle with the base centered at \c0, -and with width (base) and height equal to \x1{} and \y1, respectively. -\begin{MEx*}(4,2) - \pstriangle*[gangle=10](2,.5)(4,1) -\end{MEx*} - -\end{description} - -\Section{Arcs, circles and ellipses} - -\begin{description} - -\oitem \pscircle`(\x0,\y0)'{radius} - -This draws a circle whose center is at \c0 and that has radius . For -example: -\begin{MEx*}[-1,-1](2,2) - \pscircle[linewidth=2pt](.5,.5){1.5} -\end{MEx*} - -\mitem \qdisk(coor){radius} - - This is a streamlined version of \n{\pscircle*}. Note that the two arguments -are obligatory and there is no parameters arguments. To change the color of -the disks, you have to use \n\psset: -\begin{MEx}[1.9,2.9](2.1,3.1) - \psset{linecolor=gray} - \qdisk(2,3){4pt} -\end{MEx} - -\oitem \pswedge`(\x0,\y0)'{radius}{angle1}{angle2} - - This draws a wedge whose center is at \c0, that has radius , and -that extends counterclockwise from to . The angles must be -specified in degrees. For example: -\begin{MEx*}(2,2) - \pswedge[linecolor=gray,linewidth=2pt,fillstyle=solid]{2}{0}{70} -\end{MEx*} - -\oitem \psellipse`(\x0,\y0)'(\x1,\y1) - -\c0 is the center of the ellipse, and \x1 and \y1 are the horizontal and -vertical radii, respectively. For example: -% D.G. modification begin - Mar. 3, 2003 -%\begin{MEx*}[-1,-1.5](2,1) -% D.G. modification end -\begin{MEx*}[-1,-1](2,1) - \psellipse[fillcolor=lightgray](.5,0)(1.5,1) -\end{MEx*} - -\oitem \psarc`{arrows}\c~'{radius}{angleA}{angleB} - - This draws an arc from to , going counter clockwise, for a -circle of radius and centered at \c{}. You must include either the -{arrows} argument or the \c{} argument. For example: -\begin{MEx*}(3,2) - \psarc*[showpoints=true](1.5,1.5){1.5}{215}{0} -\end{MEx*} -See how \p{showpoints=true} draws a dashed line from the center to the arc; -this is useful when composing pictures. - -\n\psarc{} also uses the parameters: -\begin{description} - -\pitem[arcsepA=dim](0pt) - - is adjusted so that the arc would just touch a line of width -that extended from the center of the arc in the direction of . - -\pitem[arcsepB=dim](0pt) This is like \p{arcsepA}, but is adjusted. - -\pitem[arcsep=dim] This just sets both \p{arcsepA} and \p{arcsepB}. -\end{description} -These parameters make it easy to draw two intersecting lines and then use -\n\psarc{} with arrows to indicate the angle between them. For example: -\begin{MEx*}(4,3) - \SpecialCoor - \psline[linewidth=2pt](4;50)(0,0)(4;10) - \psarc[arcsepB=2pt]{->}{3}{10}{50} -\end{MEx*} - -\oitem \psarcn`{arrows}\c~'{radius}{angleA}{angleB} - - This is like \n\psarc, but the arc is drawn \emph{clockwise}. You can achieve -the same effect using \n\psarc{} by switching and and the -arrows.\footnote{% -However, with \n\pscustom{} graphics object, described in Part \ref{P-custom}, -\n\psarcn{} is not redundant.} - -\oitem \psellipticarc`{arrows}(\x0,\y0)'(\x1,\y1){angleA}{angleB} - - This draws an elliptic from to , going counter clockwise, -with \c0 the center of the ellipse and \x1 and \y1 the horizontal and -vertical radii, respectively. For example: -\begin{MEx*}[-1,-1](2,1) - \psellipticarc[showpoints=true,arrowscale=2]{->}(.5,0)(1.5,1){215}{0} -\end{MEx*} -See how \p{showpoints=true} draws a dashed line from the center to the arc; -this is useful when composing pictures. - -Like \n\psarc, \n\psellipticarc{} use the \p{arcsep}/\p{arcsepA}/\p{arcsepB} -parameters. - -Unlike \n\psarc, \n\psellipticarc use the -\p{dimen}=\p{inner}/\p{middle}/\p{outer} parameter. - -\oitem \psellipticarcn`{arrows}(\x0,\y0)'(\x1,\y1){angleA}{angleB} - - This is like \n\psellipticarc, but the arc is drawn \emph{clockwise}. You can -achieve the same effect using \n\psellipticarc{} by switching and - and the arrows.\footnote{% -However, with \n\pscustom{} graphics object, described in Part \ref{P-custom}, -\n\psellipticarcn{} is not redundant.} - -\end{description} - - -\Section{Curves} - -\begin{description} - -\oitem \psbezier`{arrows}(\x0,\y0)'(\x1,\y1)(\x2,\y2)(\x3,\y3) - - \n\psbezier{} draws a bezier curve with the four control points. The curve -starts at the first coordinate, tangent to the line connecting to the second -coordinate. It ends at the last coordinate, tangent to the line connecting to -the third coordinate. The second and third coordinates, in addition to -determining the tangency of the curve at the endpoints, also ``pull'' the -curve towards themselves. For example: -\begin{MEx}(4,4) - \psbezier[linewidth=2pt,showpoints=true]{->}(0,0)(1,4)(2,1)(4,3.5) -\end{MEx} -\p{showpoints=true} puts dots in all the control points, and connects them by -dashed lines, which is useful when adjusting your bezier curve. - -\oitem \parabola`{arrows}'\c0\c1 - - Starting at \c0, \n\parabola{} draws the parabola that passes through \c0 and -whose maximum or minimum is \c1. For example: -\begin{MEx*}(4,3) - \parabola*(1,1)(2,3) - \psset{xunit=.01} - \parabola{<->}(400,3)(200,0) -\end{MEx*} -\end{description} - -The next three graphics objects interpolate an open or closed curve through -the given points. The curve at each interior point is perpendicular to the -line bisecting the angle ABC, where B is the interior point, and A and C are -the neighboring points. Scaling the coordinates \emph{does not} cause the curve -to scale proportionately. - -The curvature is controlled by the following parameter: -\begin{description} -\pitem[curvature=num1 num2 num3] - - You have to just play around with this parameter to get what you want. -Individual values outside the range -1 to 1 are either ignored or are for -entertainment only. Below is an explanation of what each number does. A, B and -C refer to three consecutive points. - - Lower values of make the curve tighter. - - Lower values of tighten the curve where the angle ABC is greater than -45 degrees, and loosen the curve elsewhere. - - determines the slope at each point. If =0, then the curve is -perpendicular at B to the bisection of ABC. If =-1, then the curve at B -is parallel to the line AC. With this value (and only this value), scaling the -coordinates causes the curve to scale proportionately. However, positive -values can look better with irregularly spaced coordinates. Values less than --1 or greater than 2 are converted to -1 and 2, respectively. -\end{description} - -Here are the three curve interpolation macros: -\begin{description} - -\oitem \pscurve`{arrows}'\c1`\ldots\cn' - - This interpolates an open curve through the points. For example: -\begin{MEx*}(4,2) - \pscurve[showpoints=true]{<->}(0,1.3)(0.7,1.8) - (3.3,0.5)(4,1.6)(0.4,0.4) -\end{MEx*} -Note the use of \p{showpoints=true} to see the points. This is helpful when -constructing a curve. - -\oitem \psecurve`{arrows}'\c1`\ldots\cn'] - - This is like \n\pscurve, but the curve is not extended to the first and last -points. This gets around the problem of trying to determine how the curve -should join the first and last points. The "e" has something to do with -``endpoints''. For example: -% D.G. modification begin - Mar. 3, 2003 -%\begin{MEx*}[0,-.9](4,4) -% D.G. modification end -\begin{MEx*}(4,4) - \psecurve[showpoints=true](.125,8)(.25,4)(.5,2) - (1,1)(2,.5)(4,.25)(8,.125) -\end{MEx*} - -\oitem \psccurve`{arrows}'\c1`\ldots\cn' - -This interpolates a closed curve through the points. "c" stands for -``closed''. For example: -\begin{MEx*}(4,1) - \psccurve[showpoints=true] - (.5,0)(3.5,1)(3.5,0)(.5,1) -\end{MEx*} -\end{description} - -\Section{Dots\label{S-dots}} - -The graphics objects -\begin{Ex} - \object \psdot`*[par](\x1,y1)' - \object \psdots`*[par]'(\x1,\y1)`(\x2,\y2)\ldots(\x n,\y n)' -\end{Ex} -put a dot at each coordinate. - -What a ``dot'' is depends on the value of the -\begin{Ex} - \Par{dotstyle=style} -\end{Ex} -parameter. This also determines the dots you get when \p{showpoints=true}. - -The dot styles are also pretty intuitive:% -\newbox\dottable -\setbox\dottable=\hbox{% - \psset{fillcolor=lightgray} - \def\mydots#1{% - \psdots[dotstyle=#1](.1,1ex)(.55,1ex)(1,1ex)(1.45,1ex)(1.9,1ex)}% - \hfill - \begin{tabular}{cl}% - \emph{Style} & \hbox to 2cm{\emph{Example}\hss} \\[2pt] - "*" & \mydots{*}\\ - "o" & \mydots{o}\\ - "Bo" & \mydots{Bo}\\ - "x" & \mydots{x}\\ - "+" & \mydots{+}\\ - "B+" & \mydots{B+}\\ - "asterisk" & \mydots{asterisk}\\ - "Basterisk" & \mydots{Basterisk}\\ - "oplus" & \mydots{oplus}\\ - "otimes" & \mydots{otimes}\\ - "|" & \mydots{|}\\ - "B|" & \mydots{B|} - \end{tabular}% - \hfill - \begin{tabular}{cl} - \emph{Style} & \hbox to 2cm{\emph{Example}\hss} \\[2pt] - "square" & \mydots{square}\\ - "Bsquare" & \mydots{Bsquare}\\ - "square*" & \mydots{square*}\\ - "diamond" & \mydots{diamond}\\ - "diamond*" & \mydots{diamond*}\\ - "triangle" & \mydots{triangle}\\ - "Btriangle" & \mydots{Btriangle}\\ - "triangle*" & \mydots{triangle*}\\ - "pentagon" & \mydots{pentagon}\\ - "Bpentagon" & \mydots{Bpentagon}\\ - "pentagon*" & \mydots{pentagon*}\\ - \end{tabular}% - \hfill}% -\addtoquickref{center}{% - {\large\textbf{Dot styles}}\par - \leavevmode\hbox to \hsize{\unhbox\dottable}} -\begin{center} - \leavevmode - \hbox to \hsize{\unhcopy\dottable}% -\end{center} - -Except for "diamond", the center of dot styles with a hollow center is colored -\p{fillcolor}. - -Here are the parameters for changing the size and orientation of the dots: -\begin{description} - -\pitem[dotsize=dim `num'] - The diameter of a circle or disc is plus times \p{linewidth} -(if the optional is included). The size of the other dots styles is -similar (except for the size of the "|" dot style, which is set by the -\p{tbarsize} parameter described on page \pageref{p+tbarsize}). - -\pitem[dotscale=num1 `num2'] -The dots are scaled horizontally by and vertically by . If you -only include , the arrows are scaled by in both directions. - -\pitem[dotangle=angle] - After setting the size and scaling the dots, the dots are rotated by . - -\end{description} - - -\Section{Grids\label{S-grids}} - -PSTricks has a powerful macro for making grids and graph paper: - \Mac \psgrid`(\x0,\y0)(\x1,\y1)(\x2,\y2)' -\n\psgrid{} draws a grid with opposing corners \c1 and \c2. The intervals are -numbered, with the numbers positioned at \x0 and \y0. The coordinates are -always interpreted as Cartesian coordinates. For example: -\begin{MEx}[-1,-1](3,2) - \psgrid(0,0)(-1,-1)(3,2) -\end{MEx} -(Note that the coordinates and label positioning work the same as with -\n\psaxes.) - -The main grid divisions occur on multiples of \p{xunit} and \p{yunit}. -Subdivisions are allowed as well. Generally, the coordinates would be given as -integers, without units. - -If the \c0 coordinate is omitted, \c1 is used. The default for \c1 is "(0,0)". -If you don't give any coordinates at all, then the coordinates of the current -\n\pspicture{} environment are used or a 10x10 grid is drawn. Thus, you can -include a \n\psgrid{} command without coordinates in a \n\pspicture\ -environment to get a grid that will help you position objects in the picture. - -The main grid divisions are numbered, with the numbers drawn next to the -vertical line at \x0 (away from \x2) and next to the horizontal line at \x1 -(away from \y2). \c1 can be any corner of the grid, as long as \c2 is the -opposing corner, you can position the labels on any side you want. For -example, compare -\begin{MEx}(4,1) - \psgrid(0,0)(4,1) -\end{MEx} -and -\begin{MEx}(4,1) - \psgrid(4,1)(0,0) -\end{MEx} - -The following parameters apply only to \n\psgrid: -\begin{description} - -\pitem[gridwidth=dim] - The width of grid lines. - -\pitem[gridcolor=color] - The color of grid lines. - -\pitem[griddots=num] - If is positive, the grid lines are dotted, with dots per -division. - -\pitem[gridlabels=dim] - The size of the numbers used to mark the grid. - -\pitem[gridlabelcolor=color] - The color of the grid numbers. - -\pitem[subgriddiv=int] - The number of grid subdivisions. - -\pitem[subgridwidth=dim] - The width of subgrid lines. - -\pitem[subgridcolor=color] - The color of subgrid lines. - -\pitem[subgriddots=num] - Like \p{griddots}, but for subdivisions. - -\end{description} - -Here is a familiar looking grid which illustrates some of the parameters: -\begin{MEx}[-1,-1](3,1) - \psgrid[subgriddiv=1,griddots=10,gridlabels=7pt](-1,-1)(3,1) -\end{MEx} - -Note that the values of \p{xunit} and \p{yunit} are important parameters for -\n\psgrid, because they determine the spacing of the divisions. E.g., if the -value of these is "1pt", and then you type -\begin{LVerb} - \psgrid(0,0)(10in,10in) -\end{LVerb} -you will get a grid with 723 main divisions and 3615 subdivisions! (Actually, -\n\psgrid{} allows at most 500 divisions or subdivisions, to limit the damage -done by this kind of mistake.) Probably you want to set \p{unit} to ".5in" or -"1in", as in -\begin{LVerb} - \psgrid[unit=.5in](0,0)(20,20) -\end{LVerb} - - -\Section{Plots} - -\File{pst-plot} -The plotting commands described in this part are defined in -"pst-plot.tex" / "pst-plot.sty", which you must load first. - -The \n\psdots, \n\psline, \n\pspolygon, \n\pscurve, \n\psecurve{} and -\n\psccurve{} graphics objects let you plot data in a variety of ways. However, -first you have to generate the data and enter it as coordinate pairs \c{}. -The plotting macros in this section give you other ways to get and use the -data. (Section \ref{S-axes} tells you how to generate axes.) - -To parameter -\begin{Ex} - \Par{plotstyle=style} -\end{Ex} -determines what kind of plot you get. Valid styles are "dots", "line", -"polygon", "curve", "ecurve", "ccurve". E.g., if the \p{plotstyle} is -"polygon", then the macro becomes a variant of the \n\pspolygon{} object. - -You can use arrows with the plot styles that are open curves, but there is no -optional argument for specifying the arrows. You have to use the \p{arrows} -parameter instead. - -\begin{Warning} -No PostScript error checking is provided for the data arguments. Read Appendix -\ref{S-raw} before including PostScript code in the arguments. - -There are system-dependent limits on the amount of data \TeX{} and PostScript -can handle. You are much less likely to exceed the PostScript limits when you -use the "line", "polygon" or "dots" plot style, with \p{showpoints=false}, -\p{linearc=0pt}, and no arrows. -\end{Warning} - -Note that the lists of data generated or used by the plot commands cannot -contain units. The values of \n\psxunit{} and \n\psyunit{} are used as the unit. - - -\begin{description} - -\oitem \fileplot{file} - -\n\fileplot{} is the simplest of the plotting functions to use. You just need a -file that contains a list of coordinates (without units), such as generated by -Mathematica or other mathematical packages. The data can be delimited by curly -braces "{"~"}", parentheses "("~")", commas, and/or white space. Bracketing -all the data with square brackets "[ ]" will significantly speed up the rate -at which the data is read, but there are system-dependent limits on how much -data \TeX{} can read like this in one chunk. (The "[" \emph{must} go at the -beginning of a line.) The file should not contain anything else (not even -"\endinput"), except for comments marked with "%". - -\n\fileplot{} only recognizes the "line", "polygon" and "dots" plot styles, and -it ignores the \p{arrows}, \p{linearc} and \p{showpoints} parameters. The -\n\listplot{} command, described below, can also plot data from file, without -these restrictions and with faster \TeX{} processing. However, you are less -likely to exceed PostScript's memory or operand stack limits with \n\fileplot. - -If you find that it takes \TeX{} a long time to process your \n\fileplot\ -command, you may want to use the \n\PSTtoEPS{} command described on page -\pageref{+PSTtoEPS}. This will also reduce \TeX's memory requirements. - -\oitem \dataplot{commands} - -\n\dataplot{} is also for plotting lists of data generated by other programs, -but you first have to retrieve the data with one of the following commands: -\begin{Ex} - \object \savedata{command}[data] - \object \readdata{command}{file} -\end{Ex} - or the data in should conform to the rules described above for -the data in \n\fileplot{} (with \n\savedata, the data must be delimited by -"["~"]", and with \n\readdata, bracketing the data with "["~"]" speeds things -up). You can concatenate and reuse lists, as in -\begin{LVerb} - \readdata{\foo}{foo.data} - \readdata{\bar}{bar.data} - \dataplot{\foo\bar} - \dataplot[origin={0,1}]{\bar} -\end{LVerb} - -The \n\readdata{} and \n\dataplot{} combination is faster than \n\fileplot{} -if you reuse the data. \n\fileplot{} uses less of \TeX's memory than -\n\readdata{} and \n\dataplot{} if you are also use \n\PSTtoEPS. - -Here is a plot of "Integral(sin(x))". The data was generated by Mathematica, -with -\begin{LVerb} - Table[{x,N[SinIntegral[x]]},{x,0,20}] -\end{LVerb} -and then copied to this document. -\begin{MEx}(4,3) - \psset{xunit=.2cm,yunit=1.5cm} - \savedata{\mydata}[ - {{0, 0}, {1., 0.946083}, {2., 1.60541}, {3., 1.84865}, {4., 1.7582}, - {5., 1.54993}, {6., 1.42469}, {7., 1.4546}, {8., 1.57419}, - {9., 1.66504}, {10., 1.65835}, {11., 1.57831}, {12., 1.50497}, - {13., 1.49936}, {14., 1.55621}, {15., 1.61819}, {16., 1.6313}, - {17., 1.59014}, {18., 1.53661}, {19., 1.51863}, {20., 1.54824}}] - \dataplot[plotstyle=curve,showpoints=true, - dotstyle=triangle]{\mydata} - \psline{<->}(0,2)(0,0)(20,0) -\end{MEx} - -\oitem \listplot{list} - -\n\listplot{} is yet another way of plotting lists of data. This time, -should be a list of data (coordinate pairs), delimited only by white space. - is first expanded by \TeX{} and then by PostScript. This means that - might be a PostScript program that leaves on the stack a list of data, -but you can also include data that has been retrieved with \n\readdata{} and -\n\dataplot. However, when using the "line", "polygon" or "dots" plotstyles -with \p{showpoints=false}, \p{linearc=0pt} and no arrows, \n\dataplot{} is much -less likely than \n\listplot{} to exceed PostScript's memory or stack limits. -In the preceding example, these restrictions were not satisfied, and so the -example is equivalent to when \n\listplot{} is used: -\begin{LVerb} - ... - \listplot[plotstyle=curve,showpoints=true, - dotstyle=triangle]{\mydata} - ... -\end{LVerb} - -\oitem \psplot{$x_!\min@$}{$x_!\max@$}{function} - - \n\psplot{} can be used to plot a function $f(x)$, if you know a little -PostScript. should be the PostScript code for calculating $f(x)$. -Note that you must use $x$ as the dependent variable. PostScript is not -designed for scientific computation, but \n\psplot{} is good for graphing -simple functions right from within \TeX. E.g., -\begin{LVerb} - \psplot[plotpoints=200]{0}{720}{x sin} -\end{LVerb} -plots $\sin(x)$ from 0 to 720 degrees, by calculating $\sin(x)$ roughly every -3.6 degrees and then connecting the points with \n\psline. Here are plots of -$\sin(x)\cos((x/2)^2)$ and $\sin^2(x)$: -\begin{MEx}[0,-1](4,1) - \psset{xunit=1.2pt} - \psplot[linecolor=gray,linewidth=1.5pt,plotstyle=curve]% - {0}{90}{x sin dup mul} - \psplot[plotpoints=100]{0}{90}{x sin x 2 div 2 exp cos mul} - \psline{<->}(0,-1)(0,1) - \psline{->}(100,0) -\end{MEx} - -\oitem \parametricplot{$t_!\min@$}{$t_!\max@$}{function} - -This is for a parametric plot of $(x(t),y(t))$. is the PostScript -code for calculating the pair $x(t)$ $y(t)$. - -For example, -\begin{MEx*}(3,3) - \parametricplot[plotstyle=dots,plotpoints=13]% - {-6}{6}{1.2 t exp 1.2 t neg exp} -\end{MEx*} -plots 13 points from the hyperbola $xy=1$, starting with $(1.2^{-6},1.2^6)$ -and ending with $(1.2^6,1.2^{-6})$. - -Here is a parametric plot of $(\sin(t),\sin(2t))$: -\begin{MEx}[-2,-1](2,1) - \psset{xunit=1.7cm} - \parametricplot[linewidth=1.2pt,plotstyle=ccurve]% - {0}{360}{t sin t 2 mul sin} - \psline{<->}(0,-1.2)(0,1.2) - \psline{<->}(-1.2,0)(1.2,0) -\end{MEx} - -\end{description} - -The number of points that the \n\psplot{} and \n\parametricplot{} commands -calculate is set by the -\begin{Ex} - \Par{plotpoints=int} -\end{Ex} -parameter. Using "curve" or its variants instead of "line" and increasing the -value of \p{plotpoints} are two ways to get a smoother curve. Both ways -increase the imaging time. Which is better depends on the complexity of the -computation. (Note that all PostScript lines are ultimately rendered as a -series (perhaps short) line segments.) Mathematica generally uses "lineto" to -connect the points in its plots. The default minimum number of plot points for -Mathematica is 25, but unlike \n\psplot{} and \n\parametricplot, Mathematica -increases the sampling frequency on sections of the curve with greater -fluctuation. - -\endinput - -%% END psd-basi.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/psd-cove.tex b/Master/texmf-dist/doc/generic/pstricks/psd-cove.tex deleted file mode 100644 index 177e0bff2c1..00000000000 --- a/Master/texmf-dist/doc/generic/pstricks/psd-cove.tex +++ /dev/null @@ -1,108 +0,0 @@ -%% BEGIN psd-cove.tex - -\begingroup -\evensidemargin \paperwidth\relax -\advance\evensidemargin -2in -\advance\evensidemargin -\textwidth -\divide\evensidemargin 2 -\oddsidemargin\evensidemargin - -\begin{titlepage} - -\let\footnotesize\small -\let\footnoterule\relax -\setcounter{page}{0} - -\null -\vfil -\vskip 25pt -\begin{center} - {\LARGE\textbf{PSTricks}}:\\[5pt] - {\large\textbf{PostScript macros for Generic TeX}.}\\ -\end{center} - -\bigskip\bigskip -\hbox to \hsize{% - \hss - \psset{unit=.4cm} - \begin{pspicture}(0,-2)(31,12) - \catcode`\<=12 - \rput(1.5,0){% - \psellipse[linewidth=1pt](8,7)(1,3) - \psframe[linecolor=white,fillstyle=solid,fillcolor=white] - (6.4,6.5)(8,7.5) - \psline[linearc=.3,linewidth=1pt](8,8)(8,7.5)(4,7.5) - \psbezier[linewidth=1pt](4,7.5)(3,7.5)(3,6.5)(3,5.5) - \psline[linearc=.3,linewidth=1pt](8,6)(8,6.5)(5,6.5) - \psbezier[linewidth=1pt](5,6.5)(4,6.5)(4,6.5)(4,5.5) - \psline[linewidth=1pt](3,5.5)(4,5.5) - \psline[linearc=.3,linewidth=1pt](5,7.5)(5,8)(6,8)(6,7.5) - \psframe[linewidth=1pt](5.3,8)(5.7,8.7) - \psframe[linewidth=1pt,framearc=1,fillstyle=solid, - fillcolor=white](4,8.7)(7,9) - \multirput(3.5,4.8)(0,-1){4}{% - \psbezier[linewidth=.5pt](0,0)(.25,-.4)(-.25,-.4)(0,0)} - \rput[t](5.5,0){Dripping Faucet}} - \rput(20,5){% - \pspolygon[linecolor=white,fillstyle=vlines, - fillcolor=darkgray,hatchsep=.2](1,4.5)(1,4)(4,4)(4,4.5) - \psline[linewidth=2pt](1,4)(4,4) - \psline[linewidth=1.5pt](2.5,4)(2.5,3.5)(2.9,3.3)(2.1,2.9) - (2.9,2.5)(2.1,2.1)(2.9,1.7)(2.1,1.3)(2.5,1.1)(2.5,0.6) - \psframe[linecolor=black,linewidth=1.5pt,fillstyle=solid, - fillcolor=lightgray](1.8,-1)(3.2,.6) - \rput(2.5,-.2){$M$} - \psline{<->}(3.7,-.9)(3.7,.5) - \psframe[linecolor=black,linewidth=1.5pt,fillstyle=solid, - fillcolor=lightgray](1.8,-3.5)(3.2,-1.9) - \rput(2.5,-2.7){$m$} - \psline{->}(5,1)(5,-1) - \rput[l](5.5,0){$g$} - \psline{->}(3.7,-2)(3.7,-3.4) - \rput[t](2.5,-4){Mathematical Model for} - \rput[t](2.5,-5){a Dripping Faucet} - \rput(-6,-2){% - \psset{linewidth=2pt} - \psline(0,.5)(2,.5) - \psline(0,-.5)(2,-.5) - \psline(1.5,1)(2.5,0)(1.5,-1)}} - \psframe[linewidth=2pt,framearc=.05,linecolor=gray](0,-2.5)(31,12) - \uput[l]{90}(0,4.75){\texttt{leecheng}} - \end{pspicture}% - \hss} -\bigskip -\bigskip - -\begin{center} -{\LARGE\textbf{User's Guide}}\par -\vskip 3em -{\large \lineskip .75em Timothy Van Zandt}\par -\vskip 1.5em -{\large \thefiledate\\[2pt] - Version \Version% - \footnote{Documentation edited and repacked at \today\ by Rolf Niepraschk - \url{niepraschk@gmx.de} - and Herbert Vo\ss\ \url{voss@pstricks.de}.}}\par -% \Verb[codes={\catcode`\<=12}]++ -% and Herbert Voß \Verb[codes={\catcode`\<=12}]++.}}\par -\end{center} -\vfil -\small -Author's address:\\ - Department of Economics and Political Science\\ - INSEAD\\ - Boulevard de Constance\\ - 77305 Fontainebleau Cedex\\ - France\\[3mm] - Internet: \Verb[codes={\catcode`\<=12}]++ -\end{titlepage} - -\endgroup - -\setcounter{footnote}{0} -\tableofcontents -\pagenumbering{arabic} - -\endinput - -%% END psd-cove.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/psd-cust.tex b/Master/texmf-dist/doc/generic/pstricks/psd-cust.tex deleted file mode 100644 index 03441baca4f..00000000000 --- a/Master/texmf-dist/doc/generic/pstricks/psd-cust.tex +++ /dev/null @@ -1,406 +0,0 @@ -%% BEGIN psd-cust.tex - -\part{Custom graphics\label{P-custom}} - -\Section{The basics} - -PSTricks contains a large palette of graphics objects, but sometimes you need -something special. For example, you might want to shade the region between two -curves. The - \Mac \pscustom`*[par]'{commands} -command lets you ``roll you own'' graphics object. - -Let's review how PostScript handles graphics. A \emph{path} is a line, in the -mathematical sense rather than the visual sense. A path can have several -disconnected segments, and it can be open or closed. PostScript has various -operators for making paths. The end of the path is called the \emph{current -point}, but if there is no path then there is no current point. To turn the -path into something visual, PostScript can \emph{fill} the region enclosed by -the path (that is what \p{fillstyle} and such are about), and \emph{stroke} the -path (that is what \p{linestyle} and such are about). - -At the beginning of \n\pscustom, there is no path. There are various commands -that you can use in \n\pscustom{} for drawing paths. Some of these (the open -curves) can also draw arrows. \n\pscustom{} fills and strokes the path at the -end, and for special effects, you can fill and stroke the path along the way -using \n\fill{} and \n\stroke{} (see below). - -\begin{drivers} -\n\pscustom{} uses \n\pstverb{} and \n\pstunit. There are system-dependent -limits on how long the argument of "\special" can be. You may run into this -limit using \n\pscustom{} because all the PostScript code accumulated by -\n\pscustom{} is the argument of a single "\special" command. -\end{drivers} - -\Section{Parameters} - -You need to keep the separation between drawing, stroking and filling paths in -mind when setting graphics parameters. The \p{linewidth} and \p{linecolor} -parameters affect the drawing of arrows, but since the path commands do not -stroke or fill the paths, these parameters, and the \p{linestyle}, -\p{fillstyle} and related parameters, do not have any other effect (except -that in some cases \p{linewidth} is used in some calculations when drawing the -path). \n\pscustom{} and \n\fill{} make use of \p{fillstyle} and related -parameters, and \n\pscustom{} and \n\stroke{} make use of p{linestyle} and -related parameters. - -For example, if you include -\begin{LVerbatim} - \psline[linewidth=2pt,linecolor=blue,fillstyle=vlines]{<-}(3,3)(4,0) -\end{LVerbatim} -in \n\pscustom, then the changes to \p{linewidth} and \p{linecolor} will -affect the size and color of the arrow but not of the line when it is stroked, -and the change to \p{fillstyle} will have no effect at all. - -The \p{shadow}, \p{border}, \p{doubleline} and \p{showpoints} parameters are -disabled in \n\pscustom, and the \p{origin} and \p{swapaxes} parameters only -affect \n\pscustom{} itself, but there are commands (described below) that let -you achieve these special effects. - -The \p{dashed} and \p{dotted} line styles need to know something about the -path in order to adjust the dash or dot pattern appropriately. You can give -this information by setting the -\begin{Ex} - \Par{linetype=int} -\end{Ex} -parameter. If the path contains more than one disconnected segment, there is -no appropriate way to adjust the dash or dot pattern, and you might as well -leave the default value of \p{linetype}. Here are the values for simple paths: -\begin{center} -\begin{tabular}{cl} - \emph{Value} & \emph{Type of path}\\ - 0 & Open curve without arrows.\\ - -1 & Open curve with an arrow at the beginning.\\ - -2 & Open curve with an arrow at the end.\\ - -3 & Open curve with an arrow at both ends.\\ - 1 & Closed curve with no particular symmetry.\\ - $n$\textgreater 1 & Closed curve with $n$ symmetric segments. -\end{tabular} -\end{center} - -\Section{Graphics objects} - -You can use most of the graphics objects in \n\pscustom. These draw paths and -making arrows, but do not fill and stroke the paths. - -There are three types of graphics objects: -\begin{description} -\item[Special] - Special graphics objects include \n\psgrid, \n\psdots, \n\qline{} and -\n\qdisk. You cannot use special graphics objects in \n\pscustom. - -\item[Closed] - You are allowed to use closed graphics objects in \n\pscustom, but their -effect is unpredictable.\footnote{% -The closed objects never use the current point as an coordinate, but typically -they will close any existing paths, and they might draw a line between the -currentpoint and the closed curved.} -Usually you would use the open curves plus \n\closepath{} (see below) to draw -closed curves. - -\item[Open]The open graphics objects are the most useful commands for drawing -paths with \n\pscustom. By piecing together several open curves, you can draw -arbitrary paths. The rest of this section pertains to the open graphics -objects. -\end{description} - - By default, the open curves draw a straight line between the current point, -if it exists, and the beginning of the curve, except when the curve begins -with an arrow. For example -\begin{MEx*}(3,3) - \pscustom{% - \psarc(0,0){1.5}{5}{85} - \psarcn{->}(0,0){3}{85}{5}} -\end{MEx*} - -Also, the following curves make use of the current point, if it exists, as a -first coordinate: -\begin{quote} - \n\psline{} and \n\pscurve.\\ - The plot commands, with the "line" or "curve" \p{plotstyle}.\\ - \n\psbezier\, if you only include three coordinates.\\ -\end{quote} -For example: -\begin{MEx*}(4,3) - \pscustom[linewidth=1.5pt]{% - \psplot[plotstyle=curve]{.67}{4}{2 x div} - \psline(4,3)} -\end{MEx*} -We'll see later how to make that one more interesting. Here is another example -\begin{MEx*}(4,3) - \pscustom{% - \psline[linearc=.2]{|-}(0,2)(0,0)(2,2) - \psbezier{->}(2,2)(3,3)(1,0)(4,3)} -\end{MEx*} - -However, you can control how the open curves treat the current point with the -\begin{Ex} - \Par{liftpen=0/1/2} -\end{Ex} -parameter. - -If \p{liftpen=0}, you get the default behavior described above. For example -\begin{MEx*}(4,3) - \pscustom[linewidth=2pt,fillstyle=solid,fillcolor=gray]{% - \pscurve(0,2)(1,2.5)(2,1.5)(4,3) - \pscurve(4,1)(3,0.5)(2,1)(1,0)(0,.5)} -\end{MEx*} - -If \p{liftpen=1}, the curves do not use the current point as the first -coordinate (except \n\psbezier, but you can avoid this by explicitly including -the first coordinate as an argument). For example: -\begin{MEx*}(4,3) - \pscustom[linewidth=2pt,fillstyle=solid,fillcolor=gray]{% - \pscurve(0,2)(1,2.5)(2,1.5)(4,3) - \pscurve[liftpen=1](4,1)(3,0.5)(2,1)(1,0)(0,.5)} -\end{MEx*} - -If \p{liftpen=2}, the curves do not use the current point as the first -coordinate, and they do not draw a line between the current point and the -beginning of the curve. For example -\begin{MEx*}(4,3) - \pscustom[linewidth=2pt,fillstyle=solid,fillcolor=gray]{% - \pscurve(0,2)(1,2.5)(2,1.5)(4,3) - \pscurve[liftpen=2](4,1)(3,0.5)(2,1)(1,0)(0,.5)} -\end{MEx*} - -Later we will use the second example to fill the region between the two -curves, and then draw the curves. - -\Section{Safe tricks} - -The commands described under this heading, which can only be used in -\n\pscustom, do not run a risk of PostScript errors (assuming your document -compiles without \TeX{} errors). - -Let's start with some path, fill and stroke commands: -\begin{description} - -\mitem \newpath - -Clear the path and the current point. - -\mitem \moveto(coor) - - This moves the current point to \c{}. - -\mitem \closepath - - This closes the path, joining the beginning and end of each piece (there may -be more than one piece if you use \n\moveto).\footnote{% -Note that the path is automatically closed when the region is filled. Use -\n\closepath{} if you also want to close the boundary.} - -\mitem \stroke`[par]' - - This strokes the path (non-destructively). \n\pscustom{} automatically -strokes the path, but you might want to stroke it twice, e.g., to add a -border. Here is an example that makes a double line and adds a border (this -example is kept so simple that it doesn't need \n\pscustom{} at all): -\begin{MEx*}(4,3) - \psline(0,3)(4,0) - \pscustom[linecolor=white,linewidth=1.5pt]{% - \psline(0,0)(4,3) - \stroke[linewidth=5\pslinewidth] - \stroke[linewidth=3\pslinewidth,linecolor=black]} -\end{MEx*} - -\mitem \fill`[par]' - - This fills the region (non-destructively). \n\pscustom{} automatically fills -the region as well. - -\mitem \gsave - - This saves the current graphics state (i.e., the path, color, line width, -coordinate system, etc.) \n\grestore{} restores the graphics state. \n\gsave{} -and \n\grestore{} must be used in pairs, properly nested with respect to \TeX{} -groups. You can have have nested \n\gsave-\n\grestore{} pairs. - -\mitem \grestore - - See above. - -Here is an example that fixes an earlier example, using \n\gsave{} and -\n\grestore: -\begin{MEx}(4,3) - \psline{<->}(0,3)(0,0)(4,0) - \pscustom[linewidth=1.5pt]{ - \psplot[plotstyle=curve]{.67}{4}{2 x div} - \gsave - \psline(4,3) - \fill[fillstyle=solid,fillcolor=gray] - \grestore} -\end{MEx} -Observe how the line added by "\psline(4,3)" is never stroked, because it is -nested in "\gsave" and "\grestore". - -Here is another example: -\begin{MEx*}(4,3) - \pscustom[linewidth=1.5pt]{ - \pscurve(0,2)(1,2.5)(2,1.5)(4,3) - \gsave - \pscurve[liftpen=1](4,1)(3,0.5)(2,1)(1,0)(0,.5) - \fill[fillstyle=solid,fillcolor=gray] - \grestore} - \pscurve[linewidth=1.5pt](4,1)(3,0.5)(2,1)(1,0)(0,.5) -\end{MEx*} -Note how I had to repeat the second \n\pscurve{} (I could have repeated it -within \n\pscustom, with \p{liftpen=2}), because I wanted to draw a line -between the two curves to enclose the region but I didn't want this line to be -stroked. -\end{description} - -The next set of commands modify the coordinate system. -\begin{description} - -\mitem \translate(coor) - - Translate coordinate system by \c{}. This shifts everything that comes later -by \c{}, but doesn't affect what has already been drawn. - -\mitem \scale{num1 `num2'} - - Scale the coordinate system in both directions by , or horizontally by - and vertically by . - -\mitem \rotate{angle} - - Rotate the coordinate system by . - -\mitem \swapaxes - - Switch the x and y coordinates. This is equivalent to -\begin{LVerb} - \rotate{-90} - \scale{-1 1 scale} -\end{LVerb} - -\mitem \msave - - Save the current coordinate system. You can then restore it with -\n\mrestore. You can have nested \n\msave-\n\mrestore{} pairs. \n\msave{} and -\n\mrestore{} do not have to be properly nested with respect to \TeX{} groups or -\n\gsave{} and \n\grestore. However, remember that \n\gsave{} and \n\grestore -also affect the coordinate system. \n\msave-\n\mrestore{} lets you change the -coordinate system while drawing part of a path, and then restore the old -coordinate system without destroying the path. \n\gsave-\n\grestore, on the -other hand, affect the path and all other componments of the graphics state. - -\mitem \mrestore - - See above. -\end{description} - -And now here are a few shadow tricks: -\begin{description} -\mitem \openshadow`[par]' - -Strokes a replica of the current path, using the various shadow parameters. - -\mitem \closedshadow`[par]' - -Makes a shadow of the region enclosed by the current path as if it were opaque -regions. - -\mitem \movepath(coor) - -Moves the path by \c{}. Use \n\gsave-\n\grestore{} if you don't want to lose -the original path. -\end{description} - -\Section{Pretty safe tricks} - -The next group of commands are safe, \emph{as long as there is a current -point}! - -\begin{description} -\mitem \lineto(coor) - - This is a quick version of "\psline()". - -\mitem \rlineto(coor) - - This is like \n\lineto, but \c{} is interpreted relative to the current -point. - -\mitem \curveto\c1\c2\c3 - - This is a quick version of "\psbezier"\c1\c2\c3. - -\mitem \rcurveto\c1\c2\c3 - - This is like \n\curveto, but \c1, \c2 and \c3 are interpreted relative to -the current point. -\end{description} - -\Section{For hackers only} - -For PostScript hackers, there are a few more commands. Be sure to read -Appendix \ref{S-raw} before using these. Needless to say: -\begin{Warning} -Misuse of the commands in this section can cause PostScript errors. -\end{Warning} - - The PostScript environment in effect with \n\pscustom{} has one unit equal to -one \TeX{} "pt". - -\begin{description} - -\mitem \code{code} - Insert the raw PostScript code. - -\mitem \dim{dim} - - Convert the PSTricks dimension to the number of "pt"'s, and inserts it in -the PostScript code. - -\mitem \coor\c1`\c2...\cn' - -Convert one or more PSTricks coordinates to a pair of numbers (using "pt" -units), and insert them in the PostScript code. - -\mitem \rcoor\c1`\c2...\cn' - -Like \n\coor, but insert the coordinates in reverse order. - -\mitem \file{file} - - This is like \n\code, but the raw PostScript is copied verbatim (except -comments delimited by "%") from . - -\mitem \arrows{arrows} - - This defines the PostScript operators "ArrowA" and "ArrowB" so that -\begin{LVerb} - x2 y2 x1 y1 ArrowA - x2 y2 x1 y1 ArrowB -\end{LVerb} -each draws an arrow(head) with the tip at \c1 and pointing from \c2. "ArrowA" -leaves the current point at end of the arrowhead, where a connect line should -start, and leaves \c2 on the stack. "ArrowB" does not change the current -point, but leaves -\begin{LVerb} - x2 y2 x1' y1' -\end{LVerb} -on the stack, where \c{1'} is the point where a connecting line should join. -To give an idea of how this work, the following is roughly how PSTricks draws -a bezier curve with arrows at the end: -\begin{MEx*}(4,3) - \pscustom{ - \arrows{|->} - \code{ - 80 140 5 5 ArrowA - 30 -30 110 75 ArrowB - curveto}} -\end{MEx*} - -\mitem \setcolor{color} - - Set the color to . - -\end{description} - -\endinput - -%% END psd-cust.tex diff --git a/Master/texmf-dist/doc/generic/pstricks/psd-esse.tex b/Master/texmf-dist/doc/generic/pstricks/psd-esse.tex deleted file mode 100644 index a76636d0d3b..00000000000 --- a/Master/texmf-dist/doc/generic/pstricks/psd-esse.tex +++ /dev/null @@ -1,392 +0,0 @@ -%% BEGIN psd-esse.tex - -\part*{Welcome to PSTricks} - -PSTricks is a collection of PostScript-based \TeX{} macros that is compatible -with most \TeX{} macro packages, including Plain \TeX, \LaTeX{} and \ConTeXt, -PSTricks gives you color, graphics, rotation, trees and overlays. PSTricks -puts the icing (PostScript) on your cake (\TeX)! - -To install PSTricks, follow the instructions in the file "read-me.pst" that -comes with the PSTricks package. Even if PSTricks has already been installed -for you, give "read-me.pst" a look over. - -This \emph{User's Guide} verges on being a reference manual, meaning that it is -not designed to be read linearly. Here is a recommended strategy: Finish -reading this brief overview of the features in PSTricks. Then thumb through -the entire \emph{User's Guide} to get your own overview. Return to -Part~\ref{P-essentials} (Essentials) and read it carefully. Refer to the -remaining sections as the need arises. - -When you cannot figure out how to do something or when trouble arises, check -out the appendices (Help). You just might be lucky enough to find a solution. -There is also a \LaTeX{} file "samples.pst" of samples that is distributed with -PSTricks. Look to this file for further inspiration. - -This documentation is written with \LaTeX. Some examples use \LaTeX{} specific -constructs and some don't. However, there is nothing \LaTeX{} specific about -any of the macros, nor is there anything that does not work with \LaTeX. This -package has been tested with Plain \TeX, \LaTeX{} and \ConTeXt{} and -should work with other \TeX{} macro packages as well. - -\File{pstricks} -The main macro file is "pstricks.tex"/"pstricks.sty". Each of the PSTricks -macro files comes with a ".tex" extension and a ".sty" extension; these are -equivalent, but the ".sty" extension means that you can include the file name -as a \LaTeX{} package. - -There are numerous supplementary macro files. A file, like the one above and -the left, is used in this \emph{User's Guide} to remind you that you must input -a file before using the macros it contains. - -For most PSTricks macros, even if you misuse them, you will not get PostScript -errors in the output. However, it is recommended that you resolve any \TeX{} -errors before attempting to print your document. A few PSTricks macros pass on -PostScript errors without warning. Use these with care, especially if you are -using a networked printer, because PostScript errors can cause a printer to -bomb. Such macros are pointed out in strong terms, using a warning like this -one: - -\begin{Warning} -Use macros that do not check for PostScript errors with care. PostScript -errors can cause a printer to bomb! -\end{Warning} - -Keep in mind the following typographical conventions in this User's Guide. -\begin{itemize} - \item All literal input characters, i.e., those that should appear verbatim - in your input file, appear in upright "Helvetica" and {\UsageFont - Helvetica-Bold} fonts. - \item Meta arguments, for which you are supposed to substitute a value - (e.g., ) appear in slanted and - {\UsageFont\MetaFont Helvetica-BoldOblique} fonts. - \item The main entry for a macro or parameter that states its syntax appears - in a large bold font, \emph{except for the optional arguments, which are in - medium weight}. This is how you can recognize the optional arguments. - \item References to PSTricks commands and parameters within paragraphs are - set in {\UsageFont Helvetica-Bold}. - -\end{itemize} - -\part{The Essentials\label{P-essentials}} - - -\section{Arguments and delimiters} - -Here is some nitty-gritty about arguments and delimiters that is really -important to know. - -The PSTricks macros use the following delimiters: -\begin{center} -%% DG: to do -% Begin modification RN, 2002-12-29 -\iffalse -\begin{tabular}{rl} -Curly braces & "{}" \\ -Brackets (only for optional arguments) & "[]" \\ -Parentheses and commas for coordinates & \c{} \\ -"=" and "," for parameters & "=," \ldots\\ -\end{tabular} -\fi -\begin{tabular}{rl} -Curly braces & "{""}" \\ -Brackets (only for optional arguments) & "[""]" \\ -Parentheses and commas for coordinates & \c{} \\ -"=" and "," for parameters & "=""," \ldots\\ -\end{tabular} -% End modification RN -\end{center} -Spaces and commas are also used as delimiters within arguments, but in this -case the argument is expanded before looking for the delimiters. - -Always use a period rather than a comma to denote the decimal point, so that -PSTricks doesn't mistake the comma for a delimiter. - -The easiest mistake to make with the PSTricks macros is to mess up the -delimiters. This may generate complaints from \TeX{} or PSTricks about bad -arguments, or other unilluminating errors such as the following: -\begin{description}\itemsep=0pt\parsep=0pt -\item[] "! Use of \get@coor doesn't match its definition." -\item[] "! Paragraph ended before \pst@addcoor was complete." -\item[] -"! Forbidden control sequence found while scanning use of \check@arrow." -\item[] "! File ended while scanning use of \lput." -\end{description} -Delimiters are generally the first thing to check when you get errors with a -PSTricks macro. - -Since PSTricks macros can have many arguments, it is useful to know that you -can leave a space or new line between any arguments, except between arguments -enclosed in curly braces. If you need to insert a new line between arguments -enclosed in curly braces, put a comment character "%" at the end of the line. - -As a general rule, the first non-space character after a PSTricks macro should -not be a "[" or "(". Otherwise, PSTricks might think that the "[" or "(" is -actually part of the macro. You can always get around this by inserting a pair -"{}" of braces somewhere between the macro and the "[" or "(". - - -\Section{Color\label{S-color}} - -The grayscales -\begin{quote} - "black", "darkgray", "gray", "lightgray", and "white", -\end{quote} -and the colors -\begin{quote} - "red", "green", "blue", "cyan", "magenta", and "yellow" -\end{quote} -are predefined in PSTricks. - -This means that these names can be used with the graphics objects that are -described in later sections. This also means that the command \n\gray{} (or -\n\red, etc.) can be used much like "\rm" or "\tt", as in -\begin{Ex} - \gray\Large"{\gray This stuff should be gray.}" -\end{Ex} -The commands \n\gray, \n\red, etc. can be nested like the font commands as -well. There are a few important ways in which the color commands differ from -the font commands: -\begin{enumerate} - \item The color commands can be used in and out of math mode (there are no - restrictions, other than proper \TeX{} grouping). - \item The color commands affect whatever is in their scope (e.g., lines), - not simply characters. - \item The scope of the color commands does not extend across pages. - \item The color commands are not as robust as font commands when used inside - box macros. See page \pageref{colorboxproblems} for details. You can avoid - most problems by explicitly grouping color commands (e.g., enclosing the - scope in braces "{}") whenever these are in the argument of another - command.\footnote{% -However, this is not necessary with the PSTricks LR-box commands, expect when -\n\psverbboxtrue{} is in effect. See Section \ref{S-boxes}.} - -\end{enumerate} - -You can define or redefine additional colors and grayscales with the following -commands. In each case, is a number between 0 and 1. Spaces are used as -delimiters---don't add any extraneous spaces in the arguments. - -\begin{description} - -\mitem \newgray{color}{num} - - is the gray scale specification, to be set by PostScript's "setgray" -operator. 0 is black and 1 is white. For example: -\begin{LVerb} - \newgray{darkgray}{.25} -\end{LVerb} - -\mitem \newrgbcolor{color}{num1 num2 num3} - - is a \emph{red-green-blue} specification, to be set by -PostScript's "setrgbcolor" operator. For example, -\begin{LVerb} - \newrgbcolor{green}{0 1 0} -\end{LVerb} - -\mitem \newhsbcolor{color}{num1 num2 num3} - - is an \emph{hue-saturation-brightness} specification, to be -set by PostScript's "sethsbcolor" operator. For example, -\begin{LVerb} - \newhsbcolor{mycolor}{.3 .7 .9} -\end{LVerb} - -\mitem \newcmykcolor{color}{num1 num2 num3 num4} - - is a \emph{cyan-magenta-yellow-black} specification, to -be set by PostScript's "newcmykcolor" operator. For example, -\begin{LVerb} - \newcmykcolor{hercolor}{.5 1 0 .5} -\end{LVerb} - -\end{description} - -For defining new colors, the \emph{rbg} model is a sure thing. \emph{hsb} is not -recommended. \emph{cmyk} is not supported by all Level 1 implementations of -PostScript, although it is best for color printing. For more information on -color models and color specifications, consult the \emph{PostScript Language -Reference Manual}, 2nd Edition (Red Book), and a color guide. - -\begin{drivers} The command \n\pstVerb{} must be defined.\end{drivers} - - -\Section{Setting graphics parameters\label{S-par}} - -PSTricks uses a key-value system of graphics parameters to customize the -macros that generate graphics (e.g., lines and circles), or graphics combined -with text (e.g., framed boxes). You can change the default values of -parameters with the command \n\psset, as in -\begin{LVerb} - \psset{fillcolor=yellow} - \psset{linecolor=blue,framearc=.3,dash=3pt 6pt} -\end{LVerb} -The general syntax is: - \Mac \psset{par1=value1`,par2=value2,\ldots'} -As illustrated in the examples above, spaces are used as delimiters for some -of the values. Additional spaces are allowed only following the comma that -separates "=" pairs (which is thus a good place to start a new -line if there are many parameter changes). E.g., the first example is -acceptable, but the second is not: -\begin{LVerb} - \psset{fillcolor=yellow, linecolor=blue} - \psset{fillcolor= yellow,linecolor =blue } -\end{LVerb} -The parameters are described throughout this \emph{User's Guide}, as they are -needed. - -Nearly every macro that makes use of graphics parameters allows you to include -changes as an optional first argument, enclosed in square brackets. -For example, -\begin{LVerb} - \psline[linecolor=green,linestyle=dotted](8,7) -\end{LVerb} -draws a dotted, green line. It is roughly equivalent to -\begin{LVerb} - {\psset{linecolor=green,linestyle=dotted}\psline(8,7)} -\end{LVerb} - -For many parameters, PSTricks processes the value and stores it in a peculiar -form, ready for PostScript consumption. For others, PSTricks stores the value -in a form that you would expect. In the latter case, this \emph{User's Guide} -will mention the name of the command where the value is stored. This is so -that you can use the value to set other parameters. E.g., -\begin{LVerb} - \psset{linecolor=\psfillcolor,doublesep=.5\pslinewidth} -\end{LVerb} -However, even for these parameters, PSTricks may do some processing and -error-checking, and you should always set them using \n\psset{} or as optional -parameter changes, rather than redefining the command where the value is -stored. - -\Section{Dimensions, coordinates and angles\label{S-coor}} - -Whenever an argument of a PSTricks macro is a dimension, the unit is optional. -The default unit is set by the -\begin{Ex} - \Par{unit=dim} (1cm) -\end{Ex} -parameter. For example, with the default value of "1cm", the following are -equivalent: -\begin{LVerb} - \psset{linewidth=.5cm} - \psset{linewidth=.5} -\end{LVerb} -By never explicitly giving units, you can scale graphics by changing the value -of \p{unit}. - -You can use the default coordinate when setting non-PSTricks dimensions as -well, using the commands -\begin{Ex} - \object \pssetlength{cmd}{dim} - \object \psaddtolength{cmd}{dim} -\end{Ex} -where is a dimension register (in \LaTeX{} parlance, a ``length''), and - is a length with optional unit. These are analogous to \LaTeX's -"\setlength" and "\addtolength". - -Coordinate pairs have the form \c{}. The origin of the coordinate system is at -\TeX's currentpoint. The command \n\SpecialCoor{} lets you use polar -coordinates, in the form "(;)", where is the radius (a dimension) -and is the angle (see below). You can still use Cartesian coordinates. For -a complete description of \n\SpecialCoor, see Section \ref{S-SpecialCoor}. - -The \p{unit} parameter actually sets the following three parameters: -\begin{Ex} - \Par{xunit=dim} (1cm) - \Par{yunit=dim} (1cm) - \Par{runit=dim} (1cm) -\end{Ex} -These are the default units for x-coordinates, y-coordinates, and all other -coordinates, respectively. By setting these independently, you can scale the x -and y dimensions in Cartesian coordinate unevenly. After changing \p{yunit} to -"1pt", the two \n\psline's below are equivalent: -\begin{LVerb} - \psset{yunit=1pt} - \psline(0cm,20pt)(5cm,80pt) - \psline(0,20)(5,80) -\end{LVerb} - -The values of the \p{runit}, \p{xunit} and \p{yunit} parameters are stored in -the dimension registers \n\psunit{} (also \n\psrunit), \n\psxunit{} and -\n\psyunit. - -Angles, in polar coordinates and other arguments, should be a number giving -the angle in degrees, by default. You can also change the units used for -angles with the command - \Mac \degrees`[num]' - should be the number of units in a circle. For example, you might use -\begin{LVerb} - \degrees[100] -\end{LVerb} -to make a pie chart when you know the shares in percentages. \n\degrees{} -without the argument is the same as -\begin{LVerb} - \degrees[360] -\end{LVerb} -The command - \Mac \radians -is short for -\begin{Ex} - "\degrees[6.28319]" -\end{Ex} -\n\SpecialCoor{} lets you specify angles in other ways as well. - -\Section{Basic graphics parameters} - -The width and color of lines is set by the parameters: -\begin{Ex} - \Par{linewidth=dim} - \Par{linecolor=color} -\end{Ex} -The \p{linewidth} is stored in the dimension register \n\pslinewidth, and the -\p{linecolor} is stored in the command \n\pslinecolor. - -The regions delimited by open and closed curves can be filled, as determined -by the parameters: -\begin{Ex} - \p{fillstyle=