NetBSD/gnu/usr.bin/groff
mycroft 49031b1376 const poisoning. 1998-07-26 16:56:51 +00:00
..
addftinfo
afmtodit
devices ${TMAC,FONT}{OWN,GRP,MODE} default to $FILE{OWN,GRP,MODE} 1998-02-09 04:22:14 +00:00
doc
eqn
grodvi
groff
grog
grolj4
grops
grotty
hpftodit
include const poisoning. 1998-07-26 16:56:51 +00:00
indxbib
libbib
libdriver
libgroff
lkbib
lookbib
man
mm Oops, this is Swedish. 1998-07-21 21:57:35 +00:00
nroff
pfbtops
pic
psbb
refer
soelim Add -Idirectory option to search for .so files in a path. 1997-12-21 14:54:06 +00:00
tbl
tfmtodit
tmac ${TMAC,FONT}{OWN,GRP,MODE} default to $FILE{OWN,GRP,MODE} 1998-02-09 04:22:14 +00:00
troff
xditview
BUG-REPORT
COPYING
ChangeLog
Makefile
Makefile.cfg note bogon in the .y.cc rule which doesn't cause problems here, but 1998-04-14 20:30:27 +00:00
NEWS
PROBLEMS
PROJECTS
README.gnu
TODO
VERSION

README.gnu

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