[Groff-commit] groff/man groff_tmac.man

[Eric S. Raymond]

CVSROOT:        /sources/groff
Module name:    groff
Changes by:     Eric S. Raymond <esr>   07/02/04 18:08:37

Modified files:
        man            : groff_tmac.man 

Log message:
        Fix some Germanisms and one macro-escape typo.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/groff/man/groff_tmac.man?cvsroot=groff&r1=1.25&r2=1.26

Patches:
Index: groff_tmac.man
===================================================================
RCS file: /sources/groff/groff/man/groff_tmac.man,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- groff_tmac.man      4 Feb 2007 17:53:06 -0000       1.25
+++ groff_tmac.man      4 Feb 2007 18:08:37 -0000       1.26
@@ -280,7 +280,7 @@
 .
 To be used with
 .BR \%grodvi (@MAN1EXT@)
-\[en] this man page also gives more details how to use it.     
+\[en] this man page also gives more details of how to use it.  
 .
 .
 .TP
@@ -458,7 +458,7 @@
 .
 .TP
 .B www
-Additions of elements known from the html format, as being used in the
+Additions of elements known from the html format, as used in the
 internet (World Wide Web) pages; this includes URL links and mail
 addresses; see
 .BR groff_www (@MAN7EXT@).
@@ -468,17 +468,17 @@
 .SH NAMING
 .\" --------------------------------------------------------------------
 .
-In classical roff systems, there was a funny naming scheme for macro
-packages, due to a simplistic design in option parsing.
-.
-Macro packages were always included by option
+Classical roff systems were designed before the conventions of the
+modern C 
+.BR getopt (3)
+call evolved, and used a naming scheme for macro packages that looks
+odd to modern eyes. Macro packages were always included with the option
 .BR -m ;
 when this option was directly followed by its argument without an
 intervening space, this looked like a long option preceded by a single
 minus \[em] a sensation in the computer stone age.
-.
-To make this optically working for macro package names, all classical
-macro packages choose a name that started with the letter `m',
+To make this invocation form work, classical troff
+macro packages used names that started with the letter `m',
 which was omitted in the naming of the macro file.
 .
 .
@@ -499,7 +499,7 @@
 .P
 For similar reasons, macro packages that did not start with an `m'
 had a leading `m'
-added in the documentation and in talking; for example, the package
+added in the documentation and in speech; for example, the package
 corresponding to
 .I tmac.doc
 was called
@@ -795,7 +795,7 @@
 the name under which the macro was called is in
 .BR $0 ,
 and the number of arguments is in register
-.BR \n[.$] ;
+.BR \en[.$] ;
 see
 .BR groff (@MAN7EXT@).
 .
@@ -994,7 +994,7 @@
 .SS "Diversions"
 .\" --------------------------------------------------------------------
 .
-Diversions can be used to realize quite advanced programming
+Diversions can be used to implement quite advanced programming
 constructs.
 .
 They are comparable to pointers to large data structures in the
@@ -1010,11 +1010,10 @@
 .
 .
 .P
-Most of the problems arising with diversions can be avoided if you are
-conscious about the fact that diversions always deal with complete
-lines.
+Most of the problems arising with diversions can be avoided if you remain
+aware of the fact that diversions always store complete lines.
 .
-If diversions are used when the line buffer has not been flashed,
+If diversions are used when the line buffer has not been flushed,
 strange results are produced; not knowing this, many people get
 desperate about diversions.
 .
@@ -1022,7 +1021,7 @@
 right places.
 .
 To be on the secure side, enclose everything that has to do with
-diversions into a pair of line breaks; for example, by amply using
+diversions into a pair of line breaks; for example, by explicitly using
 .B .br
 requests.
 .