NetBSD/gnu/usr.bin/groff
mycroft e96e918e60 Use bsd.subdir.mk as appropriate. 1997-10-11 09:34:07 +00:00
..
addftinfo Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
afmtodit Use " includes, rather than <, where appropriate. 1997-05-09 04:46:29 +00:00
devices Eliminate bogus redefinitions of standard targets. 1997-05-09 07:50:03 +00:00
doc Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
eqn Makefile cleanups 1997-03-24 22:02:40 +00:00
grodvi Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
groff Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
grog Use " includes, rather than <, where appropriate. 1997-05-09 04:46:29 +00:00
grolj4 Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
grops Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
grotty Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
hpftodit Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
include Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
indxbib Makefile cleanups 1997-03-24 22:02:40 +00:00
libbib Back out BUILDDIR and NOINSTALL changes. 1997-05-31 21:21:13 +00:00
libdriver Back out BUILDDIR and NOINSTALL changes. 1997-05-31 21:21:13 +00:00
libgroff Back out BUILDDIR and NOINSTALL changes. 1997-05-31 21:21:13 +00:00
lkbib Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
lookbib Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
man Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
mm Use bsd.subdir.mk as appropriate. 1997-10-11 09:34:07 +00:00
nroff Use " includes, rather than <, where appropriate. 1997-05-09 04:46:29 +00:00
pfbtops Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
pic Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
psbb Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
refer Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
soelim Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
tbl Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
tfmtodit Upgrade groff to 1.10 1996-08-13 07:03:54 +00:00
tmac Makefile cleanups 1997-03-24 22:02:40 +00:00
troff Makefile cleanups 1997-03-24 22:02:40 +00:00
xditview Use ${INSTALL}. 1996-10-18 02:52:59 +00:00
BUG-REPORT Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
COPYING Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
ChangeLog Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
Makefile Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
Makefile.cfg Add .MAKE to the .OBJDIR hacks, so they work with `make -n'. 1997-05-07 07:15:34 +00:00
NEWS Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
PROBLEMS Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
PROJECTS Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
README.gnu Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
TODO Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00
VERSION Upgrade groff to 1.10 1996-08-13 06:33:17 +00:00

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