GNU troff (groff) — a GNU project
Table of Contents
GNU troff is looking for a maintainer. If you’re interested, please take a look at this general information about GNU packages and being a GNU maintainer, and then email email@example.com with a bit about your background and particular interest in this package. Thanks.
Please note that maintaining this package requires assigning copyright to the FSF, and ensuring that any future contributors also execute papers, since that is what past authors and contributors have done.
Groff (GNU troff) is a typesetting system that reads plain text mixed with formatting commands and produces formatted output. Output may be PostScript or PDF, html, or ASCII/UTF8 for display at the terminal. Formatting commands may be either low-level typesetting requests (“primitives”) or macros from a supplied set. Users may also write their own macros. All three may be combined.
Present on most Unix systems owing to its long association with Unix manuals (manpages), groff is capable of producing typographically sophisticated documents while consuming only minimal system resources.
Groff is released under the GNU General Public License.
If you would like to contribute to groff, or are interested to know where groff is headed, have a look at the Mission Statement.
The source code of the currently released versions of groff are available at the GNU host; the current development version is available from a git repository. The current version is 1.22.3 (04-Nov-2014).
To view the git repository in your browser, use Savannah's cgit interface. There you can also download snapshots; simply click on a commit entry line to get the URL.
Additional contributions can be found here.
- Microsoft Windows (version 1.21)
Groff documentation, provided on your system after you install:
- groff --help
- Usage summary of options and arguments.
- man groff
- Extensive explanations and examples of usage.
- info groff
- A textbook explaining how to use groff in every aspect.
- Groff and mom: an overview
- Contains a useful summary of basic groff concepts and workflow
- a paper on grohtml
Please also see the README, and other documents referenced
therein, provided with the groff source (sometimes installed
online manual, and this
Groff has three mailing lists:
- <firstname.lastname@example.org> for general discussing everything related to groff
- <email@example.com> for reporting bugs and following bug reports
- <firstname.lastname@example.org> a read-only list showing changes to the git repository
To subscribe to a groff mailing list, go to the one of the corresponding web pages:
Alternatively, please send an empty mail with a
Subject: header line of subscribe to
xxx-request list. For example, to
subscribe yourself to the main groff list, you would send
with no body and a
Subject: header line of only
Mailing lists archives can be found at the following locations:
Please report bugs using the bug tracker available from the
page. Alternatively, but less preferable, you may use the
form in the file
BUG-REPORT (provided with the groff
source); the idea of this is to make sure that we have all the
information we 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
will enable us to determine whether it really is a bug or not.
Return to the GNU Project home page.
Please send broken links and other corrections (or suggestions) to email@example.com.
Please see the Translations README for information on coordinating and submitting translations of this article.
©1996-1999, 2001, 2003-2014 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110, USA
Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this notice, and the copyright notice, are preserved.
Updated: 2014/11/04 Authors: wl, ps