summaryrefslogtreecommitdiff
path: root/systems/msdos/dviware/dvips/readme.pc
diff options
context:
space:
mode:
Diffstat (limited to 'systems/msdos/dviware/dvips/readme.pc')
-rw-r--r--systems/msdos/dviware/dvips/readme.pc113
1 files changed, 113 insertions, 0 deletions
diff --git a/systems/msdos/dviware/dvips/readme.pc b/systems/msdos/dviware/dvips/readme.pc
new file mode 100644
index 0000000000..13e278ce14
--- /dev/null
+++ b/systems/msdos/dviware/dvips/readme.pc
@@ -0,0 +1,113 @@
+Some notes on installing dvips 5.5 on MS-DOS
+by Russell Lang <rjl@monu1.cc.monash.edu.au> 21st January 1993
+
+These notes are not by Tomas Rokicki.
+Tomas Rokicki does not use MS-DOS ( smart person :-) and so will be
+unable to answer questions about MS-DOS problems.
+
+This set of MSDOS files for dvips contains:
+README.pc This file.
+makefile.tc Makefile for Borland C++.
+makefile.emx Makefile for ndmake and emx/gcc.
+config.ps config.ps modified for MSDOS
+maketexp.bat Batch file to make tex pk files.
+maketexp.cmd OS/2 batch file to make tex pk files.
+winmain.c WinMain() routine for Windows dvips.
+dvipswin.rc Windows Resource file containing radical eye icon.
+dvipswin.def Windows defaults file.
+
+If you have the Unix tar file, the steps involved in making
+dvips on a PC are:
+- On Unix, in the dvips directory, give the following commands:
+ make texc.lpro
+ nroff -man dvips.1 > pc/dvips.doc
+ nroff -man afm2tfm.1 > pc/afm2tfm.doc
+- Copy dvips/* and dvips/pc/* directories to the PC.
+- copy PStfms/*.tfm to C:\EMTEX\TFM on the PC
+ (then optionally delete pst*.tfm, rpst*.tfm, pop*.tfm rpop*.tfm,
+ pad*.tfm rpad*.tfm)
+- copy PSvfs/*.vf to C:\TEXFONTS\VF on the PC
+ (then optionally delete pst*.vf, pop*.vf, pad*.vf)
+- edit dvipsmac.tex and replace the line
+ \generictrue
+ with
+ %\generictrue
+
+For Borland C++:
+- edit paths and directories in pc/makefile.tc and pc/config.ps.
+- 'make -fpc/makefile.tc'
+- if that works, try 'make -fpc/makefile.tc install'.
+- change to another directory (to avoid using the Unix config.ps)
+ and then try to run dvips!
+
+For emx/gcc:
+- edit paths and directories in pc/makefile.emx and pc/config.ps.
+- 'ndmake -f pc/makefile.emx'
+- if that works, try 'ndmake -f pc/makefile.emx install'.
+- change to another directory (to avoid using the Unix config.ps)
+ and then try to run dvips32!
+- This version of dvips has not been tested thoroughly.
+ See the EMX documentation for the EMX DOS extender.
+- It is hoped that this version will work under OS/2.
+
+If you have MS-DOS ZIP files, they will contain a compiled version of dvips.
+
+To install this in the emTeX directories on drive C:, use
+ pkunzip -d -o dvips* c:\
+
+The MSDOS version of dvips differs from the description in
+dvips.tex in the following ways:
+- path separators are ';' not ':'
+- directory separators are '\' not '/'
+- The user's initialization file is "dvips.ini" not ".dvipsrc".
+- pipes to printers not supported. Output must go to a file.
+- MakeTeXPk is a batch file. Since MSDOS has insufficient memory
+ to run both dvips and Metafont at the same time, this batch file
+ will typically write out a set of commands for running Metafont
+ later. The maketexp.bat supplied writes out an mfjob file for emTeX.
+ maketexp.bat will probably need customising for your site.
+- To automatically make fonts, use emTeX's dvidrv as follows:
+ dvidrv dvips file.dvi
+ dvidrv sets an option -pj=mfjobfile for dvips, where mfjobfile
+ is the name of a temporary mfjob file.
+ If there are missing fonts, dvips will write this mfjob file
+ and then ask:
+ Exit to make missing fonts now (y/n)?
+ If you answer yes, dvips exits with errorlevel 8 which tells
+ dvidrv to call mfjob to make the fonts, and then to call dvips again.
+ For this to work, dvidrv, dvips, mfjob and mf must be located in
+ the PATH, and the environment variables for mfjob and mf set
+ correctly. A font mode must be set with the 'M' option in config.ps.
+ If the -pj option is set, dvips will not call MakeTeXPk.bat
+- limited emTeX specials. The following ones are supported:
+ \special{em:message xxx}
+ \special{em:point n}
+ \special{em:line a[h|v|p],b[h|v|p] [,width]}
+ \special{em:linewidth width}
+ \special{em:moveto}
+ \special{em:lineto}
+ \special{em:graph xxx[,width[,height]]}
+ The line cut parameters [h|v|p] of the \special{em:line ...} command
+ are ignored. Lines are ended with a rounded cap.
+ A maximum of 1613 different point numbers are permitted on each page.
+ The \special{em:graph xxx} should work with PCX, MSP1, MSP2 and
+ BMP files. Compressed BMP files have not been tested.
+ The graph file may be scaled by giving an optional width and
+ height (expressed in the same way as TeX dimensions).
+ An example: \special{em:graph scrdump.pcx,100mm,75mm}
+
+See the config.ps file for other changes.
+
+If you want to use a different directory arrangement, modify the
+paths in config.ps. If you want to store config.ps or psfonts.map
+in a different place, either recompile dvips or use the environment
+variable TEXCONFIG.
+
+The program dvips can use emTeX font libraries created with the
+fontlib /2 option. PXL fonts within font libraries will be ignored.
+
+Borland C++ gives a large number of 'possible incorrect assignment'
+warnings.
+
+If you run out of memory running dvips, try using the `-Z0 -a' or
+just the `-a' command line options.