home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Frozen Fish 2: PC
/
frozenfish_august_1995.bin
/
bbs
/
d07xx
/
d0796.lha
/
PSTools
/
PSTools.doc
< prev
next >
Wrap
Text File
|
1993-01-10
|
6KB
|
174 lines
DVIPS / PSUTILS
===============
Amiga Port
by
Jonathan Hudson
This is a compilation of PostScript (tm) tools for the AMIGA. It's
split into two areas, DVIPS and PSUTILS.
DVIPS is a program that takes TeX .DVI files and converts them to
PostScript files.
PSUTILS are a collection of programs for manipulating PostScript files,
for example to extract all odd (or even) pages, useful for double sided
printing.
If you haven't got a PostScript printer, you can still take advantage
of the great amount of useful documentation in TeX .dvi or PostScript
.ps format, using the incredibly excellent POST program from the Fish
Disk 669.
DVIPS
=====
Why do you need DVIPS ? Well a lot of AMIGA programs, particularly
development tools, are ported from the Unix environment (as is DVIPS),
where TeX is a commonly used text formatter (or should I say type
setter). Examples are Indent (FF702), Bmake (FF523) and the version of
GNU RCS that I'm currently working on. The quality of the documentation
presentation (to say nothing of the content) is VERY high. If you want
to know how these programs work, you've got to find a way to read the
.dvi files. As the porter of Indent says "as most people don't have
TeX, I've included the .DVI file". Thanks, but maybe most people don't
have a DVI previewer either, this is where DVIPS comes in.
So to get a readable version of a .dvi file, do the following.
1. > dvips file.dvi -o file.ps ; convert .dvi to .ps
2. > post init.ps file.ps to screen ; view the .ps file
3. Optionally split the file into odd and even pages for printing
> psselect -o file.ps oddpages.ps
> psselect -e file.ps evenpages.ps
4. If you've got a DeskJet or LaserJet, print it out using postlj
> postlj init.ps oddpages.ps
(now put page in again, other side up)
> postlj init.ps evenpages.ps
If you've got another preferences printer, use post to output the .ps
file(s), if you've got a PostScript printer, then just print the .ps
file(s). Easy really.
Amiga Implementation
====================
The source came from the 1992 DECUS Europe Symposium CD-ROM. It is as:
(dir) afm Adobe Font Metric Files
(dir) ps Config files used by dvips
(dir) pslatex Latex files ???
(dir) pspks TeX pk (font) files
(dir) pstfms TeX tfm (font) files
(dir) psvfs Tex vf (font) files
(dir) source DVIPS source code
Assign-DVIPS Amiga script file to set up ASSIGNs
needed by DVIPS
dvips The DVIPS Program
dvips.ps The DVIPS documentation, if you
haven't got a PostScript printer,
get POST (FF702).
Logical Name Assignment
=======================
The Assign-DVIPS file makes the following assignments.
assign texfonts: work:dvips/pstfms
assign texvfs: work:dvips/psvfs
assign texpks: work:dvips/pspks
assign texconfig: work:dvips/ps
A similar configuration will suffice most needs. If your document has
PostScript pictures in it, DVIPS will search for it in TEXCONFIG: or
TEXINPUTS:. You can overide or add assignments using environmental
variables. For example, the documentation for BMake is a file mdoc.dvi,
which includes a PostScript drawing logo.ps. To get DVIPS to include
the drawing in the output PostScript file you must either copy logo.ps
to the texconfig: directory or setenv TEXINPUTS to point to it.
Example:
t:docs/mdoc.dvi
t:docs/logo.ps
> setenv TEXINPUTS t:docs/
> dvips t:docs/mdoc -o t:docs/mdoc.ps
The file paths.h describes the paths used by DVIPS. Note that
enviromental variable path descriptions may include a search list, with
paths separated by a semi-colon.
> setenv TEXINPUTS ";t:docs/;work:pstemp"
would search the current directory, t:docs and work:pstemp for any
PostScript figures needed. Directory names amy be specified with or
without a '/', DVIPS will try to cope.
PKFonts & METAFONT
==================
DVIPS frequently needs DVI PKFonts for its output (I say frequently, as
I know NOTHING about TeX, so all this tfm, afm, vk pk etc stuff is lost
on me). A common selection is included the TEXPKS directory. If DVIPS
can't find the font here that it needs, it will try to run METAFONT and
gftopk to make the font. It does this by running the MakeTexPK script
(this file MUST be marked as a script file (>Protect MakeTeXPK +s)). The
distributed version of this script does nothing, as I couldn't get the
mf program on the Fish TeX (611-616) disks to work (nor TeX for that
matter). This is left as an exercise for the reader. To assist in this
there are a the original sources (MakeTeXPK-dist, MakeTeXPK-dist.1
and vms/MAKETEXPK.COM (for those who find DCL more intelligible than
shell). If anyone has a PD version of TeX, METAFONT etc that runs on a
6Mb A3000, I'd like a copy please.
Porting Issues
==============
This program compiles using Matt Dillon's wonderful DICE compiler. The
supplied dmakefile is not too clever (use dmake dvips). DVIPS should
compile under other ANSI compilers, but why bother when Matt `gives
away' the best Amiga compiler for $50 ?
As Unix code goes, this is exceptional in that it's readable and was
very easy to port (kudos to Matt for this too). The changes are
#ifdef'ed _DCC apart from the cases where floats and shorts were
changed to double and int for sscanfs. It also pretends to be SYSV to
avoid adding more #ifdefs.
The programs work just fine on my v36 library'ed A3000 (2+4 mB). They
may (or not) run on v1.3, from floppies (I think not, unless you do a
lot of disk swapping) or with less memory. Enjoy.
We have to use .lpro rather than .pro files, I don't know why, maybe you do ?
PSUTILS
=======
A selection of PostScript tools to manipulate PS files. Minimal
documentation, compiles with DICE.
Author
======
These programs ported by:
Jonathan Hudson,
PO Box 5272,
Ruwi,
Sultanate of Oman,
Middle East.
Tel : +(968) 699407 (Voice & Fax)
I'd be grateful for any bug reports, enhancements etc (and PD
TeX/METAFONT programs :-)