* doc/groff.texinfo: Integrated groff_out.man.

Some macro fixes.

* man/groff_out.man: Minor fixes.

1 files changed, 25 insertions, 25 deletions

diff --git a/man/groff_out.man b/man/groff_out.man
index 3ef60578..92f9ecf4 100644
--- a/man/groff_out.man
+++ b/man/groff_out.man
@@ -3,7 +3,7 @@
 .ig
 groff_out.5
 
-Last update: 10 Apr 2002
+Last update: 24 Apr 2002
 
 This file is part of groff, the GNU roff type-setting system.
 
@@ -264,7 +264,7 @@ program before it is fed into a device postprocessor program.
 As the GNU roff processor
 .BR groff (@MAN1EXT@)
 is a wrapper program around troff that automatically calls a
-postprocessor, this output does not show up automatically.
+postprocessor, this output does not show up normally.
 .
 This is why it is called
 .I intermediate
@@ -289,10 +289,10 @@ describes what is output by the GNU troff program, while
 refers to the language that is accepted by the parser that prepares
 this output for the postprocessors.
 .
-This parser is smarter on white space and implements obsolete elements
+This parser is smarter on whitespace and implements obsolete elements
 for compatibility, otherwise both formats are the same.
 .
-The pre-groff roff versions are denoted by
+The pre-groff roff versions are denoted as
 .I classical
 .IR troff .
 .
@@ -308,8 +308,8 @@ language.
 While the
 .I groff
 language is a high-level programming language for text processing, the
-intermediate output language is a kind of low-level assembler by
-specifying all positions on the page for writing and drawing.
+intermediate output language is a kind of low-level assembler language
+by specifying all positions on the page for writing and drawing.
 .
 .P
 The intermediate output produced by
@@ -348,14 +348,14 @@ for device controlling.
 .\" --------------------------------------------------------------------
 .
 .I Classical troff output
-had strange requirements on white space.
+had strange requirements on whitespace.
 .
 The
 .I groff
-output parser, however, is smart about white space by making it
+output parser, however, is smart about whitespace by making it
 maximally optional.
 .
-The white space characters, i.e.\& the
+The whitespace characters, i.e.\& the
 .IR tab ,
 .IR space ,
 and
@@ -387,7 +387,7 @@ separated by syntactical space.
 .P
 A line break is a syntactical element, too.
 .
-Every command argument can be followed by white space, a comment, or a
+Every command argument can be followed by whitespace, a comment, or a
 newline character.
 .
 Thus a
@@ -466,7 +466,7 @@ The names of characters and fonts can be of arbitrary length.
 A character that is to be printed will always be in the current font.
 .
 .P
-A string argument is always terminated by the next white space
+A string argument is always terminated by the next whitespace
 character (space, tab, or newline); an embedded
 .B #
 character is regarded as part of the argument, not as the beginning of
@@ -507,7 +507,7 @@ with the arguments set as outlined in the section
 .BR "Device Control Commands" .
 .
 But the parser for the intermediate output format is able to swallow
-additional white space and comments as well.
+additional whitespace and comments as well.
 .
 .P
 The
@@ -581,7 +581,7 @@ single character, taking a fixed number of arguments.
 .
 Most of them are commands for positioning and text writing.
 .
-These commands are smart about white space.
+These commands are smart about whitespace.
 .
 Optionally,
 .I syntactical space
@@ -673,7 +673,7 @@ for the filling color of graphic objects is
 .BR DF .
 .
 The color components are specified as integer arguments between 0 and
-\n[@maxcolor] with black having all components\~0.
+\n[@maxcolor].
 .
 The number of color components and their meaning vary for the
 different color schemes.
@@ -848,7 +848,7 @@ doesn't use this.
 .
 .
 .command w
-Informs about a paddable white space to increase readability.
+Informs about a paddable whitespace to increase readability.
 .
 The spacing itself must be performed explicitly by a move command.
 .
@@ -860,7 +860,7 @@ The spacing itself must be performed explicitly by a move command.
 Each graphics or drawing command in the intermediate output starts
 with the letter\~\c
 .B D
-followed by another single character that specifies a subcommand; this
+followed by one or two characters that specify a subcommand; this
 is followed by a fixed or variable number of integer arguments that
 are separated by a single space character.
 .
@@ -997,16 +997,16 @@ graphics, and the outline of graphic objects is
 .BR m .
 .
 The color components are specified as integer arguments between 0 and
-\n[@maxcolor] with black having all components\~0.
+\n[@maxcolor].
 .
 The number of color components and their meaning vary for the
 different color schemes.
 .
 These commands are generated by the groff escape sequences
-.B \*[@backslash]DF
+.B \*[@backslash]D'F\ .\|.\|.'
 and
 .B \*[@backslash]M
-(with no other corresponding graphics command).
+(with no other corresponding graphics commands).
 .
 No position changing.
 .
@@ -1276,8 +1276,8 @@ while
 .argument h
 is the minimal horizontal motion, and
 .argument v
-the minimal vertical motion; all arguments are positive integers in
-basic units\~\c
+the minimal vertical motion possible with this device; all arguments
+are positive integers in basic units\~\c
 .unit u
 per inch.
 .
@@ -1311,7 +1311,7 @@ this is actually just ignored.
 .xsub Typesetter
 Set name of device to word
 .argument xxx ,
-a sequence of characters ended by the next white space character.
+a sequence of characters ended by the next whitespace character.
 .
 The possible device names coincide with those from the groff
 .B -T
@@ -1380,7 +1380,7 @@ strange command that combined a horizontal move and the printing of a
 character.
 .
 It didn't have a command code, but is represented by a 3-character
-argument consisting of exactly 2 digits and a character.
+argument consisting of exactly 2\~digits and a character.
 .
 .TP
 .argument ddc
@@ -1402,7 +1402,7 @@ of variable length a separating space is obligatory.
 In
 .I classical
 .IR troff ,
-large cluster of these and other commands were used, mostly without
+large clusters of these and other commands were used, mostly without
 spaces; this made such output almost unreadable.
 .
 .RE
@@ -1612,7 +1612,7 @@ This output can be fed into the postprocessor
 .BR xditview (1x)
 or
 .BR gxditview (@MAN1EXT@)
-for displaying in X window.
+for displaying in\~X.
 .
 .P
 Due to the obsolete jump-and-write command, the text clusters in the