[3433] in SIPB bug reports
HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
daemon@ATHENA.MIT.EDU (Lones A. Smith)
Sat Jan 16 16:59:57 1993
Date: Sat, 16 Jan 93 16:59:07 -0500
From: Lones A. Smith <lones@lones.mit.edu>
To: bug-sipb@Athena.MIT.EDU, olc@Athena.MIT.EDU
Hi,
I have pointed out a VERY USEFUL and FREE drawing LaTeX
drawing package that has been placed in tex-contrib:
PSTricks. Both my student and some PhD econ students
*require* this. I am using it on my NeXT, and my student must
be compatible with me on athena.
Why does this concern sipb? PSTricks needs to have some files
input by dvips. For TeX, I can use a setenv TEXINPUTS command
and tell my LaTeX to look in tex-contrib. But for dvips I
know of know other way than to ask you to figure out what
this means for dvips. (I DO NOT KNOW ANYTHING ABOUT DVIPS OR
UNIX IN GENERAL.) Furthermore, athena-OLC refuses to help me
saying that dvips is your domain.
1. Along the lines of a "setenv TEXINPUTS" command, is there
a simple "PSINPUTS" command that I can put in my .cshrc.mine
file that will tell dvips to *also* look for input files in a
place I specify?
2. Even if so, I would genuinely appreciate it if *you* could
follow the EXPLICIT list of steps that that is taken from
readme.pst in /mit/tex-contrib/pstricks. Note that because
special knowledge about postscript drivers is required in
step 2, I *cannot* (thoug I wish I could) just send you the
files that need to put in sipb. For your convenience, they
are (and you will have to take a look at pstricks in
/mit/tex-contrib to fully appreciate them):
INSTALLATION FOR USERS OF OTHER DVI-TO-PS DRIVERS:
PSTricks should be adaptable to other drivers with similar
capabilities.
Feel free to contact me for help.
1. Use pstricks.doc as your input file for now (rather than
pstricks.tex).
2. Examine the configuration file pstricks.con. Uncomment
the \iffalse...\fi surrounding the commands for
Rokicki's dvips.
Try to define the required commands appropriately for
you driver,
but don't use a header file yet (i.e., leave \pstheader
undefined).
3. Run pst-test.tex through Plain TeX until you get things
to work
as well as possible. You may not be able to use all of
PSTricks features,
but if you can define \pstverb and \pstunit, you at
least can use
all the graphics objects.
4. Decide whether your driver supports inclusion of a
PostScript
header file. (PSTricks runs much more efficiently with a
header,)
If so, define \pstheader appropriately in pstricks.con.
5. Run pst-make through Plain TeX or LaTeX. This generates
pstricks.tex and possibly pstricks.pro.
6. Follow the instructions above for Rokicki's dvips, using
the pstricks.tex and pstricks.pro files that you
generated
rather than the ones that came with the package.
INSTALLATION FOR USERS OF ROKICKI'S DVIPS:
1. Put the input files where your TeX looks for inputs.
2. Put the file pstricks.pro where dvips looks for headers.
Probably /usr/lib/tex/ps on unix systems.
3. Typeset the LaTeX file samples.pst as a test and to see
the samples.
Hoping aginst hope that someone can get me started,
Prof. Lones A. Smith
Department of Economics
MIT E52-252C
v-mail: (617) 253-0914
e-mail: lones@lones.mit.edu (NeXT mail or the garden variety
stuff)
lasmith@athena.mit.edu (if all else fails)
