home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
rtsi.com
/
2014.01.www.rtsi.com.tar
/
www.rtsi.com
/
OS9
/
OSK
/
APPS
/
TeX
/
tex_readme
< prev
next >
Wrap
Text File
|
2009-11-06
|
5KB
|
108 lines
This group contains source, compiled binary, and other files
needed to run 'Common TeX'. The binary files were compiled
on an MM/1 - should run on other "OSK" machines. The source was
obviously written to be as portable as possible and should
compile on a lot of different systems.
Note that I am NOT the author of these programs, see
the 'copying' and 'readme' files in ctexdoc.ar for authors
instructions on distribution.
Following is a quick program description and a few notes to help
you decide if you want to download some or all of the files.
To compile the CTeX files, you will need the GNU GCC compiler.
For both CTeX and DVI2TTY you will need the TOPS 'os9lib.l' library
or something similar.
********** TeX **************
TeX is a typesetting program. It reads a text file with embedded
commands and produces a "DeVice Independent" (.DVI) file that will
(with the aid of a suitable device-specific driver program) completely
control the output device. It specifies the position of just about
every single mark on the paper. A second program in this group (DVI2TTY)
will take the DVI file and turn it into something that will display
on a terminal screen or dot-matrix printer.
To run TeX, you will NEED the "TeXBook" by Donald Knuth (I got it at
Waldens). If you can figure out how to use the program without that
book, you are a lot smarter than I am. There is no documentation
for TeX included here.
The TeXbook, Donald E. Knuth ISBN 0-201-13448-9
Source and the makefiles I used on my MM/1 are in ctexsrc.ar. Note
that I could not get the Microware Compiler to swallow this source.
The macros drove it nuts. The GNU (GCC) compiler did fine. More
experienced "C" programmers could probably figure out how to get it
through the MW compiler. I rewrote some of the more complicated
macros and the MW compiler liked it a lot better - but then I discovered
that the GCC compiler would do it and I scrapped my patches. The
only modifications in the source are a few "#ifdef OSK" lines to cover
differences in the names/locations of header files.
If you would rather not compile your own, you will need virtex.bin,
ctexinp.ar and ctextfms.ar. Put all the <font>.tfm files in
/dd/usr/tex/tfms. Put 'plain.fmt' in /dd/usr/tex/formats. Put
<file>.tex files in /dd/usr/tex/inputs. Environment variables
TEXFONTS, TEXFORMATS, AND TEXINPUTS will be read and used for
paths if found. The other .bin file 'initex.bin' is used to produce
'plain.fmt' from 'plain.tex' - you will need it to make customized
format files for your own use. See the TeXbook.
See 'ctex.ins' <in ctexdoc.ar> for more info.
*************** DVI2TTY ****************
This program was written to allow previewing of TeX .DVI files on a
screen or dot-matrix printer. It ignores some of the more complicated
controls in the file and produces a pretty neat output. It can be
improved in some spots with a text editor (or a few strategic PROFF
commands) to polish up the final printed output. All source and docs
are in dvi2tty.ar. This one WILL compile with the Microware Compiler
with no trouble. Again, the only changes in the source were some
little #ifdef OSK (the header is here, not there) type lines. If you
just want to get the binary and run it, 'dvi2tty -?' will give you
a pretty good idea for usage. One undocumented option: '-e<n> will
change the spacing between words. The <n> can be a positive or negative
number. The author (one of them - there are several) warns that you
can lose ALL the spaces if you get carried away - '-e-11' is suggested.
I used -e-15 on the .dvi files that come with the GNU compiler.
John R. Wainwright
CIS: 72517,676 DELPHI: JOHNREED GENIE: J.WAINWRIGHT
----------
ADDITIONAL NOTES:
I have recompiled the sources and added a utility program called
'tex', which simply takes its command line arguments and passes them
along to virtex, along with the argument "&plain". This alleviates the
need to type:
virtex "&plain" foo.tex
every time you want to plain tex a file. This tiresome command line is
thus replaced by:
tex foo.tex
Note, however, that my simple little program 'tex' does not return any
error codes returned by virtex. It probably should, and I believe
there's a simple modification, but at the moment my OS9 C manuals are
packed away waiting to go along with me back to college.
To compile the sources, you will need at least 2 MB of memory.
Compilation on my Gimix Micro-20, 12.5 MHz 68020, took about 45 minutes
or so. To run virtex requires just over 512k of free memory. I'd suggest
running only on systems with greater than 768k.
Russell E. Hoffman
rh2y+@andrew.cmu.edu