NetBSD/gnu/usr.bin/groff
enami 5d9e26fa5b - Use PRINTOBJDIR and .WAIT where appropriate.
- Define PARALLEL in gdb/Makefile since multiple yacc might run.
2001-01-09 08:52:56 +00:00
..
addftinfo
afmtodit
devices
doc
eqn
grodvi
groff
grog
grolj4
grops
grotty
hpftodit
include
indxbib Use mkstemp(3). 2000-01-24 02:03:37 +00:00
libbib
libdriver
libgroff
lkbib
lookbib
man
mm
nroff
pfbtops
pic
psbb
refer
soelim
tbl
tfmtodit
tmac
troff Make the ligature_node operators compile with GCC 2.95.2. 2000-07-24 02:24:43 +00:00
xditview Use ${COPY} instead of -c for ${INSTALL} commands. 2000-09-23 13:53:41 +00:00
BUG-REPORT
ChangeLog
COPYING
Makefile convert to using .WAIT 2001-01-09 03:13:39 +00:00
Makefile.cfg - Use PRINTOBJDIR and .WAIT where appropriate. 2001-01-09 08:52:56 +00:00
NEWS
PROBLEMS
PROJECTS
README.gnu
TODO
VERSION

This is the GNU groff document formatting system.  The version number
is given in the file VERSION.

Included in this release are implementations of troff, pic, eqn, tbl,
refer, the -man macros and the -ms macros, and drivers for PostScript,
TeX dvi format, HP LaserJet 4 printers, and typewriter-like devices.
Also included is a modified version of the Berkeley -me macros, an
enhanced version of the X11 xditview previewer, and an implementation
of the -mm macros contributed by Joergen Haegg (jh@efd.lth.se).

See the file INSTALL for installation instructions.  You will require
a C++ compiler.

The file NEWS describes recent user-visible changes to groff.

Groff is free software. See the file COPYING for copying permission.

The file PROBLEMS describes various problems that have been
encountered in compiling, installing, and running groff.

For the moment, the documentation assumes that you are already
familiar with the Unix versions of troff, -man, -ms and the
preprocessors.

The most recent released version of groff is always available by
anonymous ftp from prep.ai.mit.edu in the directory pub/gnu.

Please report bugs using the form in the file BUG-REPORT; the idea of
this is to make sure that I have all the information I need to fix the
bug.  At the very least, read the BUG-REPORT form and make sure that
you supply all the information that it asks for.  Even if you are not
sure that something is a bug, report it using BUG-REPORT: this will
enable me to determine whether it really is a bug or not.

James Clark
jjc@jclark.com