Return to README CVS log

Up to [Research Unix] / researchv10no / cmd / troff

Annotation of researchv10no/cmd/troff/README, revision 1.1.1.1

1.1       root        1: To make troff (actually a.out):
                      2: 
                      3:        make
                      4: 
                      5: You must have an ANSI C compiler for this.  In a pinch, the awk program
                      6: unansi may help you move backwards in time.
                      7: 
                      8: You will also need a driver for your favorite output device.
                      9: d202.c provides a model, although it is specialized to a machine no
                     10: one has.  There are also a variety of postscript drivers that are the
                     11: best thing to use if you have a postscript device.  the default output
                     12: device is "post".
                     13: 
                     14: You will also have to make a DESC file for your typesetter and some
                     15: font description files; see dev202 for examples.  These describe the
                     16: named characters, widths, kerning information, and output codes.
                     17: 
                     18: Nroff is the same program as troff, so you should
                     19: 
                     20:        cp a.out /usr/bin/troff
                     21:        ln /usr/bin/troff /usr/bin/nroff
                     22: 
                     23: or the equivalent.
                     24: 
                     25: You will also need terminal description files for your terminals; see
                     26: tab.37, tab.450 and tab.lp for examples.
                     27: 
                     28: DESC and font description files are normally stored in /usr/lib/font;
                     29: macro packages are in /usr/lib/tmac; nroff tables are in
                     30: /usr/lib/term.  You can edit tdef.h to change these assumptions.
                     31: 
                     32: There have been a few features since the last version, and a number of
                     33: significant internal changes.  Not all are improvements, of course.
                     34: Most of the more recent changes, including bug fixes, are in FIXES,
                     35: which you should read also.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.