# Using PSTricks with Textures

PSTricks is a collection of TeX macros allowing one to generate Postscript graphics within TeX documents. The entire package is available from your local CTAN server. Those in the US can download the necessary files from the mirror site ftp://ftp.cdrom.com/pub/tex/ctan/graphics/pstricks/

The current maintainers of PSTricks have an information page at http://www.tug.org/applications/PSTricks/.

PSTricks is a generic TeX package that may be called from either Plain TeX and its close relatives, or from Latex. As distributed, the package is set up to be used out of the box by users of standard Tex--dvips distributions, with installation consisting of placing the required .tex and .sty files in the appropriate TeX Input directories, and the .pro header files in locations searched by dvips. The default form of the crucial configuration file pstricks.con assumes that the \special inclusions follow the dvips model.

Users of Textures (a typesetting system for the Macintosh sold by Blue Sky Research) can use almost all features of the PSTricks package provided they have version 1.7 or higher, and they install the package as follows:

• Move all files from the distribution folders `dvips/`, `generic/` and `latex/` into `TeX Inputs`, or a subfolder of `TeX Inputs`.
• Rename the file `pstricks.con` to `pstricks.dvips`, and then rename `textures.con` to `pstricks.con`.
• Make the following change in the file `pstricks.pro`:

```%/STV { SDict begin normalscale end STP  } def
%
%must be changed for Textures to read
%
/STV { Mag 72.27 72 div mul dup neg scale STP  } def
```

## Usage differences

Under standard tex--dvips (as for example on Unix, Windows xx or Oztex), the production cycle is:
1. edit the tex source file containing calls to pstricks macros;
2. tex the file, correcting errors until a dvi file is generated;
3. run dvips over the dvi file to generate a ps file;
4. view the result with ghostview or some other Postscript rendering engine;
5. repeat the above until all is as it should be, then print the ps file.

With Textures, there is no dvips, and the production cycle is as follows, assuming you are using a Postscript printer with Laserwriter 8 or Adobe PSPrinter.

1. edit the tex source file containing calls to pstricks macros;
2. typeset the file, correcting errors as necessary;
3. select the Textures Typeset window, and call File/Print. If paper and printing costs are not a concern, print to the printer, else in the print dialog that follows, select "print to file", with option "include all but standard 13 postscript fonts" to generate a ps file;
4. view the resulting ps file with ghostview or some other Postscript rendering engine;
5. repeat until all is as it should be, then print the Typeset window to a Postscript printer.

• The `pst-text.tex` macros don't correctly generate text along a path using the above methods.
• The color macros don't work under Latex, though they are OK with Plain TeX. There seems to be a problem with the textures.def file distributed as Latex R9P0. A fix is supposedly in the works. [Note added 7/5/00: I just received from technical support at Blue Sky Research an updated version of `textures.def` that seems to fix the Latex problems with color rendition. It's preamble states that it is intended for Textures 2.0 and higher. They also supplied a new `pstricks.con` which improves `pstricks` stability and incorporates the patch to `pstricks.pro` mentioned above. The fixes for both these files are due to Ross Moore. They also supplied an update for `htexture.def` which fixes a number of problems using the `hyperref` package with Textures.]
• In Textures 1.8.1, the Postscript file generated by Textures `\special{postscript ...}` truncates Postscript inclusions of more than about 410 characters with the characters "\ETC." effectively demolishing use of PSTricks in this version of Textures. According to Floyd at BlueSky, this bug in Textures' handling of `\special{postscript ...}` slipped into version 1.8.1 and is fixed in versions 1.8.2 and higher. (This is also partly due to an ungraceful piece of the TeX code, which in the absence of sufficient string space, truncates the strings without warning and inserts \ETC.)