head	1.1;
branch	1.1.1;
access;
symbols
	RELENG_8_4:1.1.1.7.0.30
	RELENG_9_1_0_RELEASE:1.1.1.7
	RELENG_9_1:1.1.1.7.0.28
	RELENG_9_1_BP:1.1.1.7
	RELENG_8_3_0_RELEASE:1.1.1.7
	RELENG_8_3:1.1.1.7.0.26
	RELENG_8_3_BP:1.1.1.7
	RELENG_9_0_0_RELEASE:1.1.1.7
	RELENG_9_0:1.1.1.7.0.24
	RELENG_9_0_BP:1.1.1.7
	RELENG_9:1.1.1.7.0.22
	RELENG_9_BP:1.1.1.7
	RELENG_7_4_0_RELEASE:1.1.1.7
	RELENG_8_2_0_RELEASE:1.1.1.7
	RELENG_7_4:1.1.1.7.0.20
	RELENG_7_4_BP:1.1.1.7
	RELENG_8_2:1.1.1.7.0.18
	RELENG_8_2_BP:1.1.1.7
	RELENG_8_1_0_RELEASE:1.1.1.7
	RELENG_8_1:1.1.1.7.0.16
	RELENG_8_1_BP:1.1.1.7
	RELENG_7_3_0_RELEASE:1.1.1.7
	RELENG_7_3:1.1.1.7.0.14
	RELENG_7_3_BP:1.1.1.7
	RELENG_8_0_0_RELEASE:1.1.1.7
	RELENG_8_0:1.1.1.7.0.12
	RELENG_8_0_BP:1.1.1.7
	RELENG_8:1.1.1.7.0.10
	RELENG_8_BP:1.1.1.7
	RELENG_7_2_0_RELEASE:1.1.1.7
	RELENG_7_2:1.1.1.7.0.8
	RELENG_7_2_BP:1.1.1.7
	RELENG_7_1_0_RELEASE:1.1.1.7
	RELENG_6_4_0_RELEASE:1.1.1.6.14.1
	RELENG_7_1:1.1.1.7.0.6
	RELENG_7_1_BP:1.1.1.7
	RELENG_6_4:1.1.1.6.14.1.0.8
	RELENG_6_4_BP:1.1.1.6.14.1
	RELENG_7_0_0_RELEASE:1.1.1.7
	RELENG_6_3_0_RELEASE:1.1.1.6.14.1
	RELENG_7_0:1.1.1.7.0.4
	RELENG_7_0_BP:1.1.1.7
	RELENG_6_3:1.1.1.6.14.1.0.6
	RELENG_6_3_BP:1.1.1.6.14.1
	RELENG_7:1.1.1.7.0.2
	RELENG_7_BP:1.1.1.7
	RELENG_6_2_0_RELEASE:1.1.1.6.14.1
	RELENG_6_2:1.1.1.6.14.1.0.4
	RELENG_6_2_BP:1.1.1.6.14.1
	RELENG_5_5_0_RELEASE:1.1.1.6
	RELENG_5_5:1.1.1.6.0.18
	RELENG_5_5_BP:1.1.1.6
	RELENG_6_1_0_RELEASE:1.1.1.6.14.1
	RELENG_6_1:1.1.1.6.14.1.0.2
	RELENG_6_1_BP:1.1.1.6.14.1
	RELENG_6_0_0_RELEASE:1.1.1.6
	v1_19_2:1.1.1.7
	RELENG_6_0:1.1.1.6.0.16
	RELENG_6_0_BP:1.1.1.6
	RELENG_6:1.1.1.6.0.14
	RELENG_6_BP:1.1.1.6
	RELENG_5_4_0_RELEASE:1.1.1.6
	RELENG_5_4:1.1.1.6.0.12
	RELENG_5_4_BP:1.1.1.6
	RELENG_4_11_0_RELEASE:1.1.1.3.2.3
	RELENG_4_11:1.1.1.3.2.3.0.8
	RELENG_4_11_BP:1.1.1.3.2.3
	RELENG_5_3_0_RELEASE:1.1.1.6
	RELENG_5_3:1.1.1.6.0.10
	RELENG_5_3_BP:1.1.1.6
	RELENG_5:1.1.1.6.0.8
	RELENG_5_BP:1.1.1.6
	RELENG_4_10_0_RELEASE:1.1.1.3.2.3
	RELENG_4_10:1.1.1.3.2.3.0.6
	RELENG_4_10_BP:1.1.1.3.2.3
	RELENG_5_2_1_RELEASE:1.1.1.6
	RELENG_5_2_0_RELEASE:1.1.1.6
	RELENG_5_2:1.1.1.6.0.6
	RELENG_5_2_BP:1.1.1.6
	RELENG_4_9_0_RELEASE:1.1.1.3.2.3
	RELENG_4_9:1.1.1.3.2.3.0.4
	RELENG_4_9_BP:1.1.1.3.2.3
	RELENG_5_1_0_RELEASE:1.1.1.6
	RELENG_5_1:1.1.1.6.0.4
	RELENG_5_1_BP:1.1.1.6
	v1_19:1.1.1.6
	RELENG_4_8_0_RELEASE:1.1.1.3.2.3
	RELENG_4_8:1.1.1.3.2.3.0.2
	RELENG_4_8_BP:1.1.1.3.2.3
	RELENG_5_0_0_RELEASE:1.1.1.6
	RELENG_5_0:1.1.1.6.0.2
	RELENG_5_0_BP:1.1.1.6
	v1_18_1:1.1.1.6
	RELENG_4_7_0_RELEASE:1.1.1.3.2.2
	RELENG_4_7:1.1.1.3.2.2.0.8
	RELENG_4_7_BP:1.1.1.3.2.2
	RELENG_4_6_2_RELEASE:1.1.1.3.2.2
	RELENG_4_6_1_RELEASE:1.1.1.3.2.2
	RELENG_4_6_0_RELEASE:1.1.1.3.2.2
	RELENG_4_6:1.1.1.3.2.2.0.6
	RELENG_4_6_BP:1.1.1.3.2.2
	RELENG_4_5_0_RELEASE:1.1.1.3.2.2
	RELENG_4_5:1.1.1.3.2.2.0.4
	RELENG_4_5_BP:1.1.1.3.2.2
	RELENG_4_4_0_RELEASE:1.1.1.3.2.2
	RELENG_4_4:1.1.1.3.2.2.0.2
	RELENG_4_4_BP:1.1.1.3.2.2
	v1_17_2:1.1.1.5
	RELENG_4_3_0_RELEASE:1.1.1.3.2.1
	RELENG_4_3:1.1.1.3.2.1.0.2
	RELENG_4_3_BP:1.1.1.3.2.1
	v1_17:1.1.1.5
	v1_16_1:1.1.1.4
	RELENG_4_2_0_RELEASE:1.1.1.3
	RELENG_4_1_1_RELEASE:1.1.1.3
	PRE_SMPNG:1.1.1.3
	RELENG_4_1_0_RELEASE:1.1.1.3
	RELENG_3_5_0_RELEASE:1.1.1.1.4.2
	RELENG_4_0_0_RELEASE:1.1.1.3
	RELENG_4:1.1.1.3.0.2
	RELENG_4_BP:1.1.1.3
	v1_15:1.1.1.3
	RELENG_3_4_0_RELEASE:1.1.1.1.4.1
	RELENG_3_3_0_RELEASE:1.1.1.1.4.1
	RELENG_3_2_PAO:1.1.1.1.4.1.0.2
	RELENG_3_2_PAO_BP:1.1.1.1.4.1
	RELENG_3_2_0_RELEASE:1.1.1.1.4.1
	v1_11:1.1.1.2
	RELENG_3_1_0_RELEASE:1.1.1.1
	RELENG_3:1.1.1.1.0.4
	RELENG_3_BP:1.1.1.1
	RELENG_2_2_8_RELEASE:1.1.1.1
	RELENG_3_0_0_RELEASE:1.1.1.1
	RELENG_2_2_7_RELEASE:1.1.1.1
	RELENG_2_2_6_RELEASE:1.1.1.1
	RELENG_2_2_5_RELEASE:1.1.1.1
	RELENG_2_2_2_RELEASE:1.1.1.1
	RELENG_2_2_1_RELEASE:1.1.1.1
	RELENG_2_2_0_RELEASE:1.1.1.1
	RELENG_2_2:1.1.1.1.0.2
	RELENG_2_2_BP:1.1.1.1
	v1_10:1.1.1.1
	FSF:1.1.1;
locks; strict;
comment	@# @;


1.1
date	96.09.07.16.17.57;	author pst;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	96.09.07.16.17.57;	author pst;	state Exp;
branches
	1.1.1.1.4.1;
next	1.1.1.2;

1.1.1.2
date	99.03.15.08.35.22;	author obrien;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	2000.01.12.09.48.13;	author asmodai;	state Exp;
branches
	1.1.1.3.2.1;
next	1.1.1.4;

1.1.1.4
date	2000.12.05.18.49.20;	author ru;	state Exp;
branches;
next	1.1.1.5;

1.1.1.5
date	2001.04.17.12.11.29;	author ru;	state Exp;
branches;
next	1.1.1.6;

1.1.1.6
date	2002.10.11.08.52.00;	author ru;	state Exp;
branches
	1.1.1.6.14.1;
next	1.1.1.7;

1.1.1.7
date	2005.10.20.10.45.16;	author ru;	state Exp;
branches
	1.1.1.7.30.1;
next	;

1.1.1.1.4.1
date	99.03.18.00.03.49;	author obrien;	state Exp;
branches;
next	1.1.1.1.4.2;

1.1.1.1.4.2
date	2000.03.09.20.06.05;	author asmodai;	state Exp;
branches;
next	;

1.1.1.3.2.1
date	2000.12.07.09.48.11;	author ru;	state Exp;
branches;
next	1.1.1.3.2.2;

1.1.1.3.2.2
date	2001.04.26.17.32.39;	author ru;	state Exp;
branches;
next	1.1.1.3.2.3;

1.1.1.3.2.3
date	2003.02.14.15.21.44;	author ru;	state Exp;
branches;
next	;

1.1.1.6.14.1
date	2005.11.15.22.06.18;	author ru;	state Exp;
branches;
next	;

1.1.1.7.30.1
date	2005.10.20.10.45.16;	author svnexp;	state dead;
branches;
next	1.1.1.7.30.2;

1.1.1.7.30.2
date	2013.03.28.13.01.12;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@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
@


1.1.1.1
log
@Virgin import of FSF groff v1.10
@
text
@@


1.1.1.1.4.1
log
@MFC: upgrade to ver 1.11.
@
text
@d29 1
a29 1
this is to make sure that FSF has all the information it needs to fix the
d33 1
a33 1
enable us to determine whether it really is a bug or not.
d35 2
a36 1
GNU groff was written by James Clark <jjc@@jclark.com>.
@


1.1.1.1.4.2
log
@MFC: groff 1.15
@
text
@d6 4
a9 5
TeX dvi format, HP LaserJet 4 printers, HTML format (still alpha), 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@@axis.se).
d16 1
a16 1
Groff is free software.  See the file COPYING for copying permission.
d26 1
a26 1
anonymous ftp from ftp.gnu.org in the directory pub/gnu/groff.
d28 6
a33 14
A CVS repository is now available, containing the current development
version of groff.  You can access it with the commands

  export CVSROOT=:pserver:anoncvs@@anoncvs.ffii.org:/var/cvs
  cvs login
  cvs -z9 co groff

(if the prompt for the password appears, just press the enter key).
After a successful login you no longer need the first two commands; an
update of a checked out repository should be done with

  cvs -z9 update -d

Please read the info pages of cvs for further details.
d35 1
a35 33
Alternatively, you can download snapshots (which are updated twice a
day) from

  ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz

or a diff file relative to the latest official groff release as

  ftp://ftp.ffii.org/pub/groff/devel/groff-<version>-current.diff.gz

Please report bugs using the form in the file BUG-REPORT; the idea of
this is to make sure that FSF has all the information it needs 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 us to determine whether it really is a bug or not.

Three mailing lists are available:

  bug-groff@@gnu.org          for reporting bugs
  groff@@gnu.org              for general discussion of groff
  groff-commit@@ffii.org      a read-only list showing logs of
                             commitments to the CVS repository

Note that groff@@gnu.org is an alias for groff@@ffii.org; you must be
subscribed to the `groff' and `groff-commit' lists to send mails.

To subscribe, send a mail to <list>-request@@<domain> (example:
groff-request@@ffii.org) with the word `subscribe' in either the
subject or body of the email (don't include the quotes).

GNU groff was written by James Clark <jjc@@jclark.com>.  It is now
maintained by Ted Harding <ted.harding@@nessie.mcc.ac.uk> and Werner
Lemberg <wl@@gnu.org>.
@


1.1.1.2
log
@Virgin import of FSF groff v1.11
@
text
@d29 1
a29 1
this is to make sure that FSF has all the information it needs to fix the
d33 1
a33 1
enable us to determine whether it really is a bug or not.
d35 2
a36 1
GNU groff was written by James Clark <jjc@@jclark.com>.
@


1.1.1.3
log
@Virgin import of FSF groff v1.15
@
text
@d6 4
a9 5
TeX dvi format, HP LaserJet 4 printers, HTML format (still alpha), 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@@axis.se).
d16 1
a16 1
Groff is free software.  See the file COPYING for copying permission.
d26 1
a26 1
anonymous ftp from ftp.gnu.org in the directory pub/gnu/groff.
d28 6
a33 14
A CVS repository is now available, containing the current development
version of groff.  You can access it with the commands

  export CVSROOT=:pserver:anoncvs@@anoncvs.ffii.org:/var/cvs
  cvs login
  cvs -z9 co groff

(if the prompt for the password appears, just press the enter key).
After a successful login you no longer need the first two commands; an
update of a checked out repository should be done with

  cvs -z9 update -d

Please read the info pages of cvs for further details.
d35 1
a35 33
Alternatively, you can download snapshots (which are updated twice a
day) from

  ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz

or a diff file relative to the latest official groff release as

  ftp://ftp.ffii.org/pub/groff/devel/groff-<version>-current.diff.gz

Please report bugs using the form in the file BUG-REPORT; the idea of
this is to make sure that FSF has all the information it needs 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 us to determine whether it really is a bug or not.

Three mailing lists are available:

  bug-groff@@gnu.org          for reporting bugs
  groff@@gnu.org              for general discussion of groff
  groff-commit@@ffii.org      a read-only list showing logs of
                             commitments to the CVS repository

Note that groff@@gnu.org is an alias for groff@@ffii.org; you must be
subscribed to the `groff' and `groff-commit' lists to send mails.

To subscribe, send a mail to <list>-request@@<domain> (example:
groff-request@@ffii.org) with the word `subscribe' in either the
subject or body of the email (don't include the quotes).

GNU groff was written by James Clark <jjc@@jclark.com>.  It is now
maintained by Ted Harding <ted.harding@@nessie.mcc.ac.uk> and Werner
Lemberg <wl@@gnu.org>.
@


1.1.1.3.2.1
log
@MFC: Upgrade to Groff 1.16.1.
@
text
@d5 6
a10 6
grn, refer, -man, -mdoc, and -ms macros, and drivers for PostScript, TeX
dvi format, HP LaserJet 4 printers, Canon CAPSL printers, HTML format
(still alpha), 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@@axis.se).
d12 2
a13 2
See the file INSTALL for installation instructions.  You will require a
C++ compiler.
d19 2
a20 2
The file PROBLEMS describes various problems that have been encountered
in compiling, installing, and running groff.
d22 3
a24 2
For the moment, the documentation assumes that you are already familiar
with the Unix versions of troff, -man, -ms, and the preprocessors.
d40 1
a40 1
  cvs -z9 update -dP
a52 8
Assuming that groff-<version>.tar.gz and
groff-<version>-current.diff.gz are in the same directory, do the
following to apply the diff file:

  tar xzvf groff-<version>.tar.gz
  cd groff-<version>
  gunzip -c ../groff-<version>-current.diff.gz | patch -p1

d57 2
a58 2
not sure that something is a bug, report it using BUG-REPORT: this will
enable us to determine whether it really is a bug or not.
d71 2
a72 2
groff-request@@ffii.org) with the word `subscribe' in either the subject
or body of the email (don't include the quotes).
@


1.1.1.3.2.2
log
@MFC: Upgrade to Groff 1.17.
@
text
@d23 1
a23 1
with the Unix versions of troff, -ms, and the preprocessors.
@


1.1.1.3.2.3
log
@MFC: Groff 1.18.1.
@
text
@d75 1
a75 1
subscribed to the `groff' list to send mails.
@


1.1.1.4
log
@Virgin import of FSF groff v1.16.1
@
text
@d5 6
a10 6
grn, refer, -man, -mdoc, and -ms macros, and drivers for PostScript, TeX
dvi format, HP LaserJet 4 printers, Canon CAPSL printers, HTML format
(still alpha), 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@@axis.se).
d12 2
a13 2
See the file INSTALL for installation instructions.  You will require a
C++ compiler.
d19 2
a20 2
The file PROBLEMS describes various problems that have been encountered
in compiling, installing, and running groff.
d22 3
a24 2
For the moment, the documentation assumes that you are already familiar
with the Unix versions of troff, -man, -ms, and the preprocessors.
d40 1
a40 1
  cvs -z9 update -dP
a52 8
Assuming that groff-<version>.tar.gz and
groff-<version>-current.diff.gz are in the same directory, do the
following to apply the diff file:

  tar xzvf groff-<version>.tar.gz
  cd groff-<version>
  gunzip -c ../groff-<version>-current.diff.gz | patch -p1

d57 2
a58 2
not sure that something is a bug, report it using BUG-REPORT: this will
enable us to determine whether it really is a bug or not.
d71 2
a72 2
groff-request@@ffii.org) with the word `subscribe' in either the subject
or body of the email (don't include the quotes).
@


1.1.1.5
log
@Virgin import of FSF groff v1.17
@
text
@d23 1
a23 1
with the Unix versions of troff, -ms, and the preprocessors.
@


1.1.1.6
log
@Virgin import of FSF groff v1.18.1
@
text
@d75 1
a75 1
subscribed to the `groff' list to send mails.
@


1.1.1.6.14.1
log
@MFC: Groff 1.19.2.
@
text
@d1 2
a2 2
This is the GNU `groff' document formatting system.  The version
number is given in the file VERSION.
d4 7
a10 8
Included in this release are implementations of `troff', `pic', `eqn',
`tbl', `grn', `refer', `-man', `-mdoc', `-mom', and `-ms' macros, and
drivers for `PostScript', `TeX dvi' format, `HP LaserJet 4' printers,
`Canon CAPSL' printers, `HTML' format (beta status), and
typewriter-like devices.  Also included is a modified version of the
Berkeley `-me' macros, the enhanced version `gxditview' of the X11
`xditview' previewer, and an implementation of the `-mm' macros
contributed by Joergen Haegg (jh@@axis.se).
d12 2
a13 2
See the file `INSTALL' for installation instructions.  You will
require a C++ compiler.
d15 1
a15 1
The file `NEWS' describes recent user-visible changes to `groff'.
d17 1
a17 2
`groff' is free software.  See the file `COPYING' for copying
permission.
d19 2
a20 2
The file `PROBLEMS' describes various problems that have been
encountered in compiling, installing, and running `groff'.
d22 2
a23 2
The most recent released version of `groff' is always available by
anonymous ftp from `ftp.gnu.org' in the directory `gnu/groff'.
d25 2
a26 4
The current development version of `groff' is available from a `CVS'
repository.  You can access it by first selecting a parent directory
in which to create a working copy (call it, say, `~/cvswork'), and
then executing the commands
d28 2
a29 3
  cd ~/cvswork
  CVS_RSH=ssh; export CVS_RSH
  cvs -d:ext:anoncvs@@savannah.gnu.org/cvsroot/groff -z5 co groff
d31 3
a33 1
(Note that you need an `ssh' client for security reasons.)
d35 3
a37 3
This will create a subdirectory, `~/cvswork/groff', with a "checked
out" copy of the `CVS' repository.  An update of this working copy may
be achieved, at any later time by invoking the commands
d39 1
a39 2
  cd ~/cvswork/groff
  CVS_RSH=ssh cvs -z5 update -dP
d41 1
a41 1
Please read the `CVS' info pages for further details.
d43 2
a44 2
Finally, it is possible to access the `CVS' with a web browser by
pointing it to
d46 1
a46 1
  http://savannah.gnu.org/cvs/?group=groff
d48 1
a48 2
Alternatively, you can download snapshots (which are updated twice a day).
The complete `groff' source as a single file is available at
d50 1
a50 1
  http://groff.ffii.org/groff/devel/groff-current.tar.gz
d52 2
a53 7
A diff file relative to `groff-<version>', the latest official `groff'
release is available at

  http://groff.ffii.org/groff/devel/groff-<version>-current.diff.gz

Assuming that `groff-<version>.tar.gz' and
`groff-<version>-current.diff.gz' are in the same directory, do the
d60 1
a60 34
Depending on your requirements, you may need at least some of the
following tools to build `groff' directly from its source:

  ghostscript
  the psutils package
  the netpbm package
  texinfo 4.8
  bison >= 1.875b or byacc

Note that `texinfo' and `bison' or `byacc' are required only for
building from `CVS' sources (either a checked out working copy, or a
daily snapshot).  They are not required for building from a stable
release tarball.  Also note that the version numbers stated are the
minimum supported.  No version of `texinfo' < 4.8 will work, and the
original release of `bison' 1.875 is known not to work; you *may* find
that `bison' releases < 1.875 will work, but in case of difficulty,
please update to a later version *before* posting a bug report.

For *all* sources, you need ghostscript for creation of either `PDF' or
`HTML' output; the `netpbm' and `psutils' packages are required only for
`HTML' output.  If you don't intend to produce output in either of these
formats, then these packages are unnecessary.

In Linux Debian, the installation of `texinfo' is dangerous.  For it
creates a file `install-info' that will block the system installation.
So the created `/usr/local/bin/install-info' must be renamed.

The `groff' configure script searches for the X11 headers and
libraries `Xaw' and `Xmu'.  So the corresponding developer packages of
your system must be installed, otherwise `groff' does not install
`gxditview' and the `-TX*' devices.  In Debian, the developer packages
are `libxaw7-dev' and `libxmu-dev'.

Please report bugs using the form in the file `BUG-REPORT'; the idea of
d62 1
a62 1
the bug.  At the very least, read the `BUG-REPORT' form and make sure
d64 1
a64 1
not sure that something is a bug, report it using `BUG-REPORT': this will
d71 2
a72 2
  groff-commit@@gnu.org       a read-only list showing commitments
                             to the CVS repository
d74 2
a75 2
You can post mails directly to the `bug-groff' list, without subscribing;
to post mails to the `groff' list you must subscribe to it.
d78 2
a79 10
groff-request@@gnu.org for the `groff' list) with the word `subscribe'
in either the subject or body of the email (don't include the quotes).
Alternatively, you may subscribe by visiting the web pages at

  http://lists.gnu.org/mailman/listinfo/bug-groff
  http://lists.gnu.org/mailman/listinfo/groff
  http://lists.gnu.org/mailman/listinfo/groff-commit

Each of these web pages also provides a link to a browseable archive of
postings to the corresponding mailing list.
d81 1
a81 1
GNU `groff' was written by James Clark <jjc@@jclark.com>.  It is now
@


1.1.1.7
log
@Virgin import of FSF groff v1.19.2
@
text
@d1 2
a2 2
This is the GNU `groff' document formatting system.  The version
number is given in the file VERSION.
d4 7
a10 8
Included in this release are implementations of `troff', `pic', `eqn',
`tbl', `grn', `refer', `-man', `-mdoc', `-mom', and `-ms' macros, and
drivers for `PostScript', `TeX dvi' format, `HP LaserJet 4' printers,
`Canon CAPSL' printers, `HTML' format (beta status), and
typewriter-like devices.  Also included is a modified version of the
Berkeley `-me' macros, the enhanced version `gxditview' of the X11
`xditview' previewer, and an implementation of the `-mm' macros
contributed by Joergen Haegg (jh@@axis.se).
d12 2
a13 2
See the file `INSTALL' for installation instructions.  You will
require a C++ compiler.
d15 1
a15 1
The file `NEWS' describes recent user-visible changes to `groff'.
d17 1
a17 2
`groff' is free software.  See the file `COPYING' for copying
permission.
d19 2
a20 2
The file `PROBLEMS' describes various problems that have been
encountered in compiling, installing, and running `groff'.
d22 2
a23 2
The most recent released version of `groff' is always available by
anonymous ftp from `ftp.gnu.org' in the directory `gnu/groff'.
d25 2
a26 4
The current development version of `groff' is available from a `CVS'
repository.  You can access it by first selecting a parent directory
in which to create a working copy (call it, say, `~/cvswork'), and
then executing the commands
d28 2
a29 3
  cd ~/cvswork
  CVS_RSH=ssh; export CVS_RSH
  cvs -d:ext:anoncvs@@savannah.gnu.org/cvsroot/groff -z5 co groff
d31 3
a33 1
(Note that you need an `ssh' client for security reasons.)
d35 3
a37 3
This will create a subdirectory, `~/cvswork/groff', with a "checked
out" copy of the `CVS' repository.  An update of this working copy may
be achieved, at any later time by invoking the commands
d39 1
a39 2
  cd ~/cvswork/groff
  CVS_RSH=ssh cvs -z5 update -dP
d41 1
a41 1
Please read the `CVS' info pages for further details.
d43 2
a44 2
Finally, it is possible to access the `CVS' with a web browser by
pointing it to
d46 1
a46 1
  http://savannah.gnu.org/cvs/?group=groff
d48 1
a48 2
Alternatively, you can download snapshots (which are updated twice a day).
The complete `groff' source as a single file is available at
d50 1
a50 1
  http://groff.ffii.org/groff/devel/groff-current.tar.gz
d52 2
a53 7
A diff file relative to `groff-<version>', the latest official `groff'
release is available at

  http://groff.ffii.org/groff/devel/groff-<version>-current.diff.gz

Assuming that `groff-<version>.tar.gz' and
`groff-<version>-current.diff.gz' are in the same directory, do the
d60 1
a60 34
Depending on your requirements, you may need at least some of the
following tools to build `groff' directly from its source:

  ghostscript
  the psutils package
  the netpbm package
  texinfo 4.8
  bison >= 1.875b or byacc

Note that `texinfo' and `bison' or `byacc' are required only for
building from `CVS' sources (either a checked out working copy, or a
daily snapshot).  They are not required for building from a stable
release tarball.  Also note that the version numbers stated are the
minimum supported.  No version of `texinfo' < 4.8 will work, and the
original release of `bison' 1.875 is known not to work; you *may* find
that `bison' releases < 1.875 will work, but in case of difficulty,
please update to a later version *before* posting a bug report.

For *all* sources, you need ghostscript for creation of either `PDF' or
`HTML' output; the `netpbm' and `psutils' packages are required only for
`HTML' output.  If you don't intend to produce output in either of these
formats, then these packages are unnecessary.

In Linux Debian, the installation of `texinfo' is dangerous.  For it
creates a file `install-info' that will block the system installation.
So the created `/usr/local/bin/install-info' must be renamed.

The `groff' configure script searches for the X11 headers and
libraries `Xaw' and `Xmu'.  So the corresponding developer packages of
your system must be installed, otherwise `groff' does not install
`gxditview' and the `-TX*' devices.  In Debian, the developer packages
are `libxaw7-dev' and `libxmu-dev'.

Please report bugs using the form in the file `BUG-REPORT'; the idea of
d62 1
a62 1
the bug.  At the very least, read the `BUG-REPORT' form and make sure
d64 1
a64 1
not sure that something is a bug, report it using `BUG-REPORT': this will
d71 2
a72 2
  groff-commit@@gnu.org       a read-only list showing commitments
                             to the CVS repository
d74 2
a75 2
You can post mails directly to the `bug-groff' list, without subscribing;
to post mails to the `groff' list you must subscribe to it.
d78 2
a79 10
groff-request@@gnu.org for the `groff' list) with the word `subscribe'
in either the subject or body of the email (don't include the quotes).
Alternatively, you may subscribe by visiting the web pages at

  http://lists.gnu.org/mailman/listinfo/bug-groff
  http://lists.gnu.org/mailman/listinfo/groff
  http://lists.gnu.org/mailman/listinfo/groff-commit

Each of these web pages also provides a link to a browseable archive of
postings to the corresponding mailing list.
d81 1
a81 1
GNU `groff' was written by James Clark <jjc@@jclark.com>.  It is now
@


1.1.1.7.30.1
log
@file README was added on branch RELENG_8_4 on 2013-03-28 13:01:12 +0000
@
text
@d1 134
@


1.1.1.7.30.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 134
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', `grn', `refer', `-man', `-mdoc', `-mom', and `-ms' macros, and
drivers for `PostScript', `TeX dvi' format, `HP LaserJet 4' printers,
`Canon CAPSL' printers, `HTML' format (beta status), and
typewriter-like devices.  Also included is a modified version of the
Berkeley `-me' macros, the enhanced version `gxditview' of the X11
`xditview' previewer, and an implementation of the `-mm' macros
contributed by Joergen Haegg (jh@@axis.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'.

The most recent released version of `groff' is always available by
anonymous ftp from `ftp.gnu.org' in the directory `gnu/groff'.

The current development version of `groff' is available from a `CVS'
repository.  You can access it by first selecting a parent directory
in which to create a working copy (call it, say, `~/cvswork'), and
then executing the commands

  cd ~/cvswork
  CVS_RSH=ssh; export CVS_RSH
  cvs -d:ext:anoncvs@@savannah.gnu.org/cvsroot/groff -z5 co groff

(Note that you need an `ssh' client for security reasons.)

This will create a subdirectory, `~/cvswork/groff', with a "checked
out" copy of the `CVS' repository.  An update of this working copy may
be achieved, at any later time by invoking the commands

  cd ~/cvswork/groff
  CVS_RSH=ssh cvs -z5 update -dP

Please read the `CVS' info pages for further details.

Finally, it is possible to access the `CVS' with a web browser by
pointing it to

  http://savannah.gnu.org/cvs/?group=groff

Alternatively, you can download snapshots (which are updated twice a day).
The complete `groff' source as a single file is available at

  http://groff.ffii.org/groff/devel/groff-current.tar.gz

A diff file relative to `groff-<version>', the latest official `groff'
release is available at

  http://groff.ffii.org/groff/devel/groff-<version>-current.diff.gz

Assuming that `groff-<version>.tar.gz' and
`groff-<version>-current.diff.gz' are in the same directory, do the
following to apply the diff file:

  tar xzvf groff-<version>.tar.gz
  cd groff-<version>
  gunzip -c ../groff-<version>-current.diff.gz | patch -p1

Depending on your requirements, you may need at least some of the
following tools to build `groff' directly from its source:

  ghostscript
  the psutils package
  the netpbm package
  texinfo 4.8
  bison >= 1.875b or byacc

Note that `texinfo' and `bison' or `byacc' are required only for
building from `CVS' sources (either a checked out working copy, or a
daily snapshot).  They are not required for building from a stable
release tarball.  Also note that the version numbers stated are the
minimum supported.  No version of `texinfo' < 4.8 will work, and the
original release of `bison' 1.875 is known not to work; you *may* find
that `bison' releases < 1.875 will work, but in case of difficulty,
please update to a later version *before* posting a bug report.

For *all* sources, you need ghostscript for creation of either `PDF' or
`HTML' output; the `netpbm' and `psutils' packages are required only for
`HTML' output.  If you don't intend to produce output in either of these
formats, then these packages are unnecessary.

In Linux Debian, the installation of `texinfo' is dangerous.  For it
creates a file `install-info' that will block the system installation.
So the created `/usr/local/bin/install-info' must be renamed.

The `groff' configure script searches for the X11 headers and
libraries `Xaw' and `Xmu'.  So the corresponding developer packages of
your system must be installed, otherwise `groff' does not install
`gxditview' and the `-TX*' devices.  In Debian, the developer packages
are `libxaw7-dev' and `libxmu-dev'.

Please report bugs using the form in the file `BUG-REPORT'; the idea of
this is to make sure that FSF has all the information it needs 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 us to determine whether it really is a bug or not.

Three mailing lists are available:

  bug-groff@@gnu.org          for reporting bugs
  groff@@gnu.org              for general discussion of groff
  groff-commit@@gnu.org       a read-only list showing commitments
                             to the CVS repository

You can post mails directly to the `bug-groff' list, without subscribing;
to post mails to the `groff' list you must subscribe to it.

To subscribe, send a mail to <list>-request@@<domain> (example:
groff-request@@gnu.org for the `groff' list) with the word `subscribe'
in either the subject or body of the email (don't include the quotes).
Alternatively, you may subscribe by visiting the web pages at

  http://lists.gnu.org/mailman/listinfo/bug-groff
  http://lists.gnu.org/mailman/listinfo/groff
  http://lists.gnu.org/mailman/listinfo/groff-commit

Each of these web pages also provides a link to a browseable archive of
postings to the corresponding mailing list.

GNU `groff' was written by James Clark <jjc@@jclark.com>.  It is now
maintained by Ted Harding <ted.harding@@nessie.mcc.ac.uk> and Werner
Lemberg <wl@@gnu.org>.
@


