1 Copyright (C) 1989-2000, 2001, 2002, 2003, 2004, 2005, 2006, 2008
2 Free Software Foundation, Inc.
4 Copying and distribution of this file, with or without modification,
5 are permitted in any medium without royalty provided the copyright
6 notice and this notice are preserved.
8 This is the GNU `groff' document formatting system. The version
9 number is given in the file VERSION.
11 Included in this release are implementations of `troff', `pic', `eqn',
12 `tbl', `grn', `refer', `-man', `-mdoc', `-mom', and `-ms' macros, and
13 drivers for `PostScript', `TeX dvi' format, `HP LaserJet 4' printers,
14 `Canon CAPSL' printers, `HTML' and `XHTML' formats (beta status), and
15 typewriter-like devices. Also included is a modified version of the
16 Berkeley `-me' macros, the enhanced version `gxditview' of the X11
17 `xditview' previewer, and an implementation of the `-mm' macros
18 contributed by Joergen Haegg (jh@axis.se).
20 See the file `INSTALL' for installation instructions. You require
23 The file `NEWS' describes recent user-visible changes to `groff'.
25 `groff' is free software. See the file `COPYING' for copying
28 The file `PROBLEMS' describes various problems that have been
29 encountered in compiling, installing, and running `groff'.
31 The most recent released version of `groff' is always available by
32 anonymous ftp from `ftp.gnu.org' in the directory `gnu/groff'.
34 The current development version of `groff' is available from a `CVS'
35 repository. You can access it by first selecting a parent directory
36 in which to create a working copy (call it, say, `~/cvswork'), and
37 then executing the commands
40 cvs -d:pserver:anonymous@cvs.savannah.gnu.org/sources/groff -z5 co groff
42 This creates a subdirectory, `~/cvswork/groff', with a `checked
43 out' copy of the `CVS' repository. An update of this working copy may
44 be achieved, at any later time by invoking the commands
49 Please read the `CVS' info pages for further details.
51 Finally, it is possible to access the `CVS' with a web browser by
54 http://savannah.gnu.org/cvs/?group=groff
56 Alternatively, you can download snapshots (which are updated twice a day).
57 The complete `groff' source as a single file is available at
59 http://groff.ffii.org/groff/devel/groff-current.tar.gz
61 A diff file relative to `groff-<version>', the latest official `groff'
62 release is available at
64 http://groff.ffii.org/groff/devel/groff-<version>-current.diff.gz
66 Assuming that `groff-<version>.tar.gz' and
67 `groff-<version>-current.diff.gz' are in the same directory, do the
68 following to apply the diff file:
70 tar xzvf groff-<version>.tar.gz
72 gunzip -c ../groff-<version>-current.diff.gz | patch -p1
74 Depending on your requirements, you may need at least some of the
75 following tools to build `groff' directly from its source:
81 bison >= 1.875b or byacc
83 Note that `texinfo' and `bison' or `byacc' are required only for
84 building from `CVS' sources (either a checked out working copy, or a
85 daily snapshot). They are not required for building from a stable
86 release tarball. Also note that the version numbers stated are the
87 minimum supported. No version of `texinfo' < 4.8 works, and the
88 original release of `bison' 1.875 is known not to work; you *may* find
89 that `bison' releases < 1.875 work, but in case of difficulty,
90 please update to a later version *before* posting a bug report.
92 For *all* sources, you need ghostscript for creation of either `PDF' or
93 `HTML' output; the `netpbm' and `psutils' packages are required only for
94 `HTML' output. If you don't intend to produce output in either of these
95 formats, then these packages are unnecessary.
97 In Linux Debian, the installation of `texinfo' is dangerous. For it
98 creates a file `install-info' that blocks the system installation.
99 So the created `/usr/local/bin/install-info' must be renamed.
101 The `groff' configure script searches for the X11 headers and
102 libraries `Xaw' and `Xmu'. So the corresponding developer packages of
103 your system must be installed, otherwise `groff' does not install
104 `gxditview' and the `-TX*' devices. In Debian, the developer packages
105 are `libxaw7-dev' and `libxmu-dev'.
107 Please report bugs using the form in the file `BUG-REPORT'; the idea of
108 this is to make sure that FSF has all the information it needs to fix
109 the bug. At the very least, read the `BUG-REPORT' form and make sure
110 that you supply all the information that it asks for. Even if you are
111 not sure that something is a bug, report it using `BUG-REPORT': this
112 enables us to determine whether it really is a bug or not.
114 Three mailing lists are available:
116 bug-groff@gnu.org for reporting bugs
117 groff@gnu.org for general discussion of groff
118 groff-commit@gnu.org a read-only list showing commitments
119 to the CVS repository
121 You can post mails directly to the `bug-groff' list, without subscribing;
122 to post mails to the `groff' list you must subscribe to it.
124 To subscribe, send a mail to <list>-request@<domain> (example:
125 groff-request@gnu.org for the `groff' list) with the word `subscribe'
126 in either the subject or body of the email (don't include the quotes).
127 Alternatively, you may subscribe by visiting the web pages at
129 http://lists.gnu.org/mailman/listinfo/bug-groff
130 http://lists.gnu.org/mailman/listinfo/groff
131 http://lists.gnu.org/mailman/listinfo/groff-commit
133 Each of these web pages also provides a link to a browseable archive of
134 postings to the corresponding mailing list.
136 GNU `groff' was written by James Clark <jjc@jclark.com>. It is now
137 maintained by Ted Harding <ted.harding@nessie.mcc.ac.uk> and Werner
138 Lemberg <wl@gnu.org>.