Problems in afmtodit.1, groff_char.7, gropdf.1, pdfroff.1

[esr]

This is automatically generated email about markup problems in a man
page for which you appear to be responsible.  If you are not the right
person or list, please tell me so I can correct my database.

See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated.  Feel free to email me with any
questions.  Note: These patches do not change the modification date of
any manual page.  You may wish to do that by hand.

I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.

--
                             Eric S. Raymond

Problems with pdfroff.1:

My records indicate that you have accepted this patch, so this is just
a reminder.

Unknown or invalid macro.  That is, one that does not fit in the
macro set that the man page seems to be using.  This is a serious
error; it often means part of your text is being lost or rendered
incorrectly.

--- pdfroff.1-unpatched 2016-02-28 18:54:52.506018728 -0500
+++ pdfroff.1   2016-02-28 18:55:23.809925096 -0500
@@ -618,7 +618,7 @@
 searches the process
 .BR PATH ,
 looking for any of the preferred programs, \[oq]gawk\[cq],
-\[oq]mawk\[cq], \[oq]nawk\[cq], and \[ok]awk\[cq], in this order; if
+\[oq]mawk\[cq], \[oq]nawk\[cq], and \[oq]awk\[cq], in this order; if
 none of these are found,
 .B pdfroff
 issues a warning message, and continue processing;
@@ -778,7 +778,7 @@
 An intermediate
 .I PostScript
 file,
-in which \*[lq]Table of Contents\*[rq] entries are collected,
+in which \[lq]Table of Contents\[rq] entries are collected,
 to facilitate relocation before the body text,
 on ultimate output to the
 .I GhostScript

Problems with afmtodit.1:

My records indicate that you have accepted this patch, so this is just
a reminder.

Misspelled macro name.

--- afmtodit.1-unpatched        2016-02-19 06:55:36.565695067 -0500
+++ afmtodit.1  2016-02-19 06:55:52.437647964 -0500
@@ -239,7 +239,7 @@
 rather than the default
 .BR DESC .
 .
-If not found in the current directory, the \[oq]devps\[qc]
+If not found in the current directory, the \[oq]devps\[cq]
 subdirectory of the default font directory is searched (this is true
 for both the default device description file and a file given with
 option

Problems with gropdf.1:

My records indicate that you have accepted this patch, so this is just
a reminder.

Misspelled macro name.

--- gropdf.1-unpatched  2016-02-29 04:23:30.563698607 -0500
+++ gropdf.1    2016-02-29 04:23:48.999656326 -0500
@@ -994,7 +994,7 @@
 Foo-Bar-Bold.pfa is \[oq]XY-Foo-Bar-Bold\[cq] (the PS font name is
 stored in the
 .B internalname
-field in the \[oq]FBB\[cq] file) and belongs to foundry \[oq]F\[]cq]
+field in the \[oq]FBB\[cq] file) and belongs to foundry \[oq]F\[cq]
 thus the following line should be added to \[oq]download\[cq]:
 .
 .RS

Problems with groff_char.7:

My records indicate that you have accepted this patch, so this is just
a reminder.

Ambiguous or invalid backslash.  This doesn't cause groff a problem.
but it confuses doclifter and may confuse older troff implementations.

Misspelled macro name.

--- groff_char.7-unpatched      2016-02-29 04:41:04.637145153 -0500
+++ groff_char.7        2016-02-29 04:42:04.720991734 -0500
@@ -768,10 +768,10 @@
 .nf
 .RS
 .ft C
-\&.\e" Make a pile centered vertically 0.5em\""
-\&.\e" above the baseline.\""
-\&.\e" The first argument is placed at the top.\""
-\&.\e" The pile is returned in string `pile'\""
+\&.\e" Make a pile centered vertically 0.5em
+\&.\e" above the baseline.
+\&.\e" The first argument is placed at the top.
+\&.\e" The pile is returned in string `pile'
 \&.eo
 \&.de pile-make
 \&.  nr pile-wd 0
@@ -782,16 +782,16 @@
 \&.  while \en[pile-#] \e{\e
 \&.    nr pile-wd (\en[pile-wd] >? \ew'\e$[\en[pile-#]]')
 \&.    nr pile-ht +(\en[rst] - \en[rsb])
-\&.    as pile-args \ev'\en[rsb]u'\e"\""
-\&.    as pile-args \eZ'\e$[\en[pile-#]]'\e"\""
-\&.    as pile-args \ev'-\en[rst]u'\e"\""
+\&.    as pile-args \ev'\en[rsb]u'\e"
+\&.    as pile-args \eZ'\e$[\en[pile-#]]'\e"
+\&.    as pile-args \ev'-\en[rst]u'\e"
 \&.    nr pile-# -1
 \&.  \e}
 \&.
-\&.  ds pile \ev'(-0.5m + (\en[pile-ht]u / 2u))'\e"\""
-\&.  as pile \e*[pile-args]\e"\""
-\&.  as pile \ev'((\en[pile-ht]u / 2u) + 0.5m)'\e"\""
-\&.  as pile \eh'\en[pile-wd]u'\e"\""
+\&.  ds pile \ev'(-0.5m + (\en[pile-ht]u / 2u))'\e"
+\&.  as pile \e*[pile-args]\e"
+\&.  as pile \ev'((\en[pile-ht]u / 2u) + 0.5m)'\e"
+\&.  as pile \eh'\en[pile-wd]u'\e"
 \&..
 \&.ec
 .ft
@@ -808,7 +808,7 @@
 glyphs.
 .
 For this reason, the four glyphs \[oq]lf\[cq], \[oq]rf\[cq],
-\[o]lc\[cq], and \[oq]rc\[cq] are not unified with similarly looking
+\[oq]lc\[cq], and \[oq]rc\[cq] are not unified with similarly looking
 bracket pieces.
 .
 In