README revision 55839
1This is the GNU groff document formatting system. The version number 2is given in the file VERSION. 3 4Included in this release are implementations of troff, pic, eqn, tbl, 5refer, the -man macros and the -ms macros, and drivers for PostScript, 6TeX dvi format, HP LaserJet 4 printers, HTML format (still alpha), and 7typewriter-like devices. Also included is a modified version of the 8Berkeley -me macros, an enhanced version of the X11 xditview 9previewer, and an implementation of the -mm macros contributed by 10Joergen Haegg (jh@axis.se). 11 12See the file INSTALL for installation instructions. You will require 13a C++ compiler. 14 15The file NEWS describes recent user-visible changes to groff. 16 17Groff is free software. See the file COPYING for copying permission. 18 19The file PROBLEMS describes various problems that have been 20encountered in compiling, installing, and running groff. 21 22For the moment, the documentation assumes that you are already 23familiar with the Unix versions of troff, -man, -ms and the 24preprocessors. 25 26The most recent released version of groff is always available by 27anonymous ftp from ftp.gnu.org in the directory pub/gnu/groff. 28 29A CVS repository is now available, containing the current development 30version of groff. You can access it with the commands 31 32 export CVSROOT=:pserver:anoncvs@anoncvs.ffii.org:/var/cvs 33 cvs login 34 cvs -z9 co groff 35 36(if the prompt for the password appears, just press the enter key). 37After a successful login you no longer need the first two commands; an 38update of a checked out repository should be done with 39 40 cvs -z9 update -d 41 42Please read the info pages of cvs for further details. 43 44Alternatively, you can download snapshots (which are updated twice a 45day) from 46 47 ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz 48 49or a diff file relative to the latest official groff release as 50 51 ftp://ftp.ffii.org/pub/groff/devel/groff-<version>-current.diff.gz 52 53Please report bugs using the form in the file BUG-REPORT; the idea of 54this is to make sure that FSF has all the information it needs to fix 55the bug. At the very least, read the BUG-REPORT form and make sure 56that you supply all the information that it asks for. Even if you are 57not sure that something is a bug, report it using BUG-REPORT: this 58will enable us to determine whether it really is a bug or not. 59 60Three mailing lists are available: 61 62 bug-groff@gnu.org for reporting bugs 63 groff@gnu.org for general discussion of groff 64 groff-commit@ffii.org a read-only list showing logs of 65 commitments to the CVS repository 66 67Note that groff@gnu.org is an alias for groff@ffii.org; you must be 68subscribed to the `groff' and `groff-commit' lists to send mails. 69 70To subscribe, send a mail to <list>-request@<domain> (example: 71groff-request@ffii.org) with the word `subscribe' in either the 72subject or body of the email (don't include the quotes). 73 74GNU groff was written by James Clark <jjc@jclark.com>. It is now 75maintained by Ted Harding <ted.harding@nessie.mcc.ac.uk> and Werner 76Lemberg <wl@gnu.org>. 77