NetBSD/gnu/usr.bin/groff
jtc 908c02bfc8 LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
..
addftinfo ANSI C++ says that typedefs must specify a type (i.e. can't just 1995-09-27 14:03:23 +00:00
afmtodit specify man pages the new way. 1994-12-22 09:44:45 +00:00
devices Clean up deleted files. 1995-03-01 00:00:00 +00:00
doc Clean up deleted files. 1993-07-14 20:43:46 +00:00
eqn Explicitly remove file before creating it. 1995-06-10 20:37:55 +00:00
grodvi LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
groff LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
grog Avoid trailing garbage (from Mike Long; PR#1527). 1995-09-27 09:43:21 +00:00
grops LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
grotty LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
include Add RCS identifiers, remove some completely useless RCS logs and patchkit 1993-08-02 17:38:43 +00:00
indxbib LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
libbib No interest in PIC code here. 1993-10-05 21:39:08 +00:00
libdriver No interest in PIC code here. 1993-10-05 21:39:08 +00:00
libgroff Clean up deleted files. 1995-03-01 00:00:00 +00:00
lkbib LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
lookbib LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
man Clean up deleted files. 1995-03-01 00:00:00 +00:00
mm specify man pages the new way. 1994-12-22 09:44:45 +00:00
nroff specify man pages the new way. 1994-12-22 09:44:45 +00:00
pfbtops Add RCS identifiers, remove some completely useless RCS logs and patchkit 1993-08-02 17:38:43 +00:00
pic LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
psbb Add RCS identifiers, remove some completely useless RCS logs and patchkit 1993-08-02 17:38:43 +00:00
refer LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
soelim Add RCS identifiers, remove some completely useless RCS logs and patchkit 1993-08-02 17:38:43 +00:00
tbl LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
tfmtodit LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
tmac specify man pages the new way. 1994-12-22 09:44:45 +00:00
troff LIBMATH -> LIBM; (PR #1689) 1995-10-26 00:58:49 +00:00
xditview Install app-defaults file with the correct name. 1994-02-14 17:27:49 +00:00
BUG-REPORT initial import of 386bsd-0.1 sources 1993-03-21 09:45:37 +00:00
COPYING Update groff to release 1.08 1993-07-14 20:36:42 +00:00
ChangeLog Update groff to release 1.08 1993-07-14 20:36:42 +00:00
Makefile NetBSD RCS Id format 1995-04-23 07:58:27 +00:00
Makefile.cfg Parallel make fixes 1995-10-22 21:58:21 +00:00
NEWS Update groff to release 1.08 1993-07-14 20:36:42 +00:00
PROBLEMS Update groff to release 1.08 1993-07-14 20:36:42 +00:00
PROJECTS Update groff to release 1.08 1993-07-14 20:36:42 +00:00
README.gnu Update groff to release 1.08 1993-07-14 20:36:42 +00:00
TODO Update groff to release 1.08 1993-07-14 20:36:42 +00:00
VERSION Update groff to release 1.08 1993-07-14 20:36:42 +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, 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.  As well as
bug reports, I welcome suggestions for improvements to groff (no
matter how small).

James Clark
jjc@jclark.com