Package: libnss3-tools
Version: 2:3.109-1
Severity: minor
Tags: patch
* What led up to the situation?
Checking for defects with a new version
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man
page"
[Use "grep -e ' $' -e '\\~$' <file>" to find obvious trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
troff:<stdin>:340: warning: trailing space in the line
troff:<stdin>:342: warning: trailing space in the line
troff:<stdin>:343: warning: trailing space in the line
troff:<stdin>:344: warning: trailing space in the line
troff:<stdin>:345: warning: trailing space in the line
troff:<stdin>:346: warning: trailing space in the line
troff:<stdin>:347: warning: trailing space in the line
troff:<stdin>:348: warning: trailing space in the line
troff:<stdin>:349: warning: trailing space in the line
troff:<stdin>:350: warning: trailing space in the line
troff:<stdin>:351: warning: trailing space in the line
troff:<stdin>:352: warning: trailing space in the line
troff:<stdin>:353: warning: trailing space in the line
troff:<stdin>:354: warning: trailing space in the line
troff:<stdin>:355: warning: trailing space in the line
troff:<stdin>:356: warning: trailing space in the line
troff:<stdin>:359: warning: trailing space in the line
troff:<stdin>:383: warning: trailing space in the line
troff:<stdin>:474: warning: trailing space in the line
troff:<stdin>:476: warning: trailing space in the line
troff:<stdin>:477: warning: trailing space in the line
troff:<stdin>:478: warning: trailing space in the line
troff:<stdin>:479: warning: trailing space in the line
troff:<stdin>:480: warning: trailing space in the line
troff:<stdin>:545: warning: trailing space in the line
troff:<stdin>:546: warning: trailing space in the line
troff:<stdin>:547: warning: trailing space in the line
troff:<stdin>:548: warning: trailing space in the line
troff:<stdin>:549: warning: trailing space in the line
troff:<stdin>:550: warning: trailing space in the line
troff:<stdin>:551: warning: trailing space in the line
troff:<stdin>:552: warning: trailing space in the line
troff:<stdin>:553: warning: trailing space in the line
troff:<stdin>:554: warning: trailing space in the line
troff:<stdin>:555: warning: trailing space in the line
troff:<stdin>:556: warning: trailing space in the line
troff:<stdin>:557: warning: trailing space in the line
troff:<stdin>:558: warning: trailing space in the line
troff:<stdin>:559: warning: trailing space in the line
troff:<stdin>:560: warning: trailing space in the line
troff:<stdin>:561: warning: trailing space in the line
troff:<stdin>:562: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.19-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages libnss3-tools depends on:
ii libc6 2.41-6
ii libnspr4 2:4.36-1
ii libnss3 2:3.109-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
libnss3-tools recommends no packages.
libnss3-tools suggests no packages.
-- no debconf information
Input file is signtool.1
Output from "mandoc -T lint signtool.1": (shortened list)
1 input text line longer than 80 bytes: * An independent cer...
1 input text line longer than 80 bytes: * CA server software...
1 input text line longer than 80 bytes: * Confirm the identi...
1 input text line longer than 80 bytes: 3\&. Specify the nam...
1 input text line longer than 80 bytes: An individual file c...
1 input text line longer than 80 bytes: Authors: Elio Maldon...
1 input text line longer than 80 bytes: Before you can use N...
1 input text line longer than 80 bytes: Blocks recursion int...
1 input text line longer than 80 bytes: Certificates contain...
1 input text line longer than 80 bytes: Creates a JAR file w...
1 input text line longer than 80 bytes: Displays the content...
1 input text line longer than 80 bytes: Entries in a Netscap...
1 input text line longer than 80 bytes: Excludes the specifi...
1 input text line longer than 80 bytes: For example, if you ...
1 input text line longer than 80 bytes: For information abou...
1 input text line longer than 80 bytes: Generates a new priv...
1 input text line longer than 80 bytes: If you have a signin...
1 input text line longer than 80 bytes: Licensed under the M...
1 input text line longer than 80 bytes: Lists signing certif...
1 input text line longer than 80 bytes: Lists the PKCS #11 m...
1 input text line longer than 80 bytes: Lists the certificat...
1 input text line longer than 80 bytes: Name of a file to wh...
1 input text line longer than 80 bytes: Optimizes the archiv...
1 input text line longer than 80 bytes: Retains the temporar...
1 input text line longer than 80 bytes: Sets the quantity of...
1 input text line longer than 80 bytes: Signs a directory of...
1 input text line longer than 80 bytes: Specifies a password...
1 input text line longer than 80 bytes: Specifies a special ...
1 input text line longer than 80 bytes: Specifies a text fil...
1 input text line longer than 80 bytes: Specifies the base f...
1 input text line longer than 80 bytes: Specifies the compre...
2 input text line longer than 80 bytes: Specifies the name o...
1 input text line longer than 80 bytes: Specifies the nickna...
1 input text line longer than 80 bytes: Specifies the size o...
1 input text line longer than 80 bytes: Specifies which avai...
1 input text line longer than 80 bytes: Specifies your certi...
1 input text line longer than 80 bytes: Tells signtool not t...
1 input text line longer than 80 bytes: Tells signtool to si...
1 input text line longer than 80 bytes: The NSS tools were w...
1 input text line longer than 80 bytes: The NSS wiki has inf...
1 input text line longer than 80 bytes: The certificate info...
1 input text line longer than 80 bytes: The prompts show up ...
1 input text line longer than 80 bytes: The significance of ...
1 input text line longer than 80 bytes: The signtool command...
1 input text line longer than 80 bytes: The signtool option ...
1 input text line longer than 80 bytes: This Unix example sh...
1 input text line longer than 80 bytes: This documentation i...
1 input text line longer than 80 bytes: To see fully qualifi...
1 input text line longer than 80 bytes: To use Netscape Sign...
1 input text line longer than 80 bytes: Two signing certific...
1 input text line longer than 80 bytes: When you receive an ...
1 input text line longer than 80 bytes: You can use the \-M ...
1 input text line longer than 80 bytes: You must also have a...
1 input text line longer than 80 bytes: You use the \-L opti...
1 input text line longer than 80 bytes: You use the \-l opti...
1 input text line longer than 80 bytes: causes the files to ...
9 skipping paragraph macro: PP after SH
-.-.
Output from "test-nroff -mandoc -t -ww -z signtool.1": (shortened list)
42 line(s) with a trailing space
Remove trailing space with: sed -e 's/ *$//'
-.-.
Show if docman-to-man created this.
Who is actually creating this man page? Debian or upstream?
Is the generating software out of date?
4:.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.-.
Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
Number of lines affected is
42
-.-.
Find a repeated word
! 62 --> the
-.-.
Strings longer than 3/4 of a standard line length (80).
Use "\:" to split the string at the end of an output line, for example a
long URL (web address)
663 \m[blue]\fBhttp://www\&.mozilla\&.org/projects/security/pki/nss/\fR\m[]\&;.
The NSS site relates directly to NSS code changes and releases\&.
-.-.
Wrong distance (not two spaces) between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
Mark a final abbreviation point as such by suffixing it with "\&".
Some sentences (etc.) do not begin on a new line.
Split (sometimes) lines after a punctuation mark; before a conjunction.
Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.
Use
#!/usr/bin/sh
sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\. */\1.\n/g' $1
to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"
[List of affected lines removed.]
-.-.
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Add "\:" to split the string for the output, "\<newline>" in the source.
[List of affected lines removed.]
Longest line is number 96 with 1678 characters
Generates a new private\-public key pair and corresponding object\-signing
certificate with the given nickname\&. The newly generated keys and certificate
are installed into the key and certificate databases in the directory specified
by the \-d option\&. With the NT version of Netscape Signing Tool, you must use
the \-d option with the \-G option\&. With the Unix version of Netscape Signing
Tool, omitting the \-d option causes the tool to install the keys and
certificate in the Communicator key and certificate databases\&. If you are
installing the keys and certificate in the Communicator databases, you must
exit Communicator before using this option; otherwise, you risk corrupting the
databases\&. In all cases, the certificate is also output to a file named
x509\&.cacert, which has the MIME\-type application/x\-x509\-ca\-cert\&. Unlike
certificates normally used to sign finished code to be distributed over a
network, a test certificate created with \-G is not signed by a recognized
certificate authority\&. Instead, it is self\-signed\&. In addition, a single
test signing certificate functions as both an object\-signing certificate and a
CA\&. When you are using it to sign objects, it behaves like an object\-signing
certificate\&. When it is imported into browser software such as Communicator,
it behaves like an object\-signing CA and cannot be used to sign objects\&. The
\-G option is available in Netscape Signing Tool 1\&.0 and later versions
only\&. By default, it produces only RSA certificates with 1024\-byte keys in
the internal token\&. However, you can use the \-s option specify the required
key size and the \-t option to specify the token\&.
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
[List of affected lines removed.]
-.-
Use a character "\(->" instead of plain "->" or "\->".
433:\-\-> test\&.f
-.-.
No need for '\&' to be in front of a period (.),
if there is a character in front of it.
Remove with "sed -e 's/\\&\././g'".
[List of affected lines removed.]
-.-.
Lines longer than about(?) 1023 forces a mail program to use quoted-printable
encoding which is bad. Translater program is unusable.
Line 96, length 1678
Generates a new private\-public key pair and corresponding object\-signing
certificate with the given nickname\&. The newly generated keys and certificate
are installed into the key and certificate databases in the directory specified
by the \-d option\&. With the NT version of Netscape Signing Tool, you must use
the \-d option with the \-G option\&. With the Unix version of Netscape Signing
Tool, omitting the \-d option causes the tool to install the keys and
certificate in the Communicator key and certificate databases\&. If you are
installing the keys and certificate in the Communicator databases, you must
exit Communicator before using this option; otherwise, you risk corrupting the
databases\&. In all cases, the certificate is also output to a file named
x509\&.cacert, which has the MIME\-type application/x\-x509\-ca\-cert\&. Unlike
certificates normally used to sign finished code to be distributed over a
network, a test certificate created with \-G is not signed by a recognized
certificate authority\&. Instead, it is self\-signed\&. In addition, a single
test signing certificate functions as both an object\-signing certificate and a
CA\&. When you are using it to sign objects, it behaves like an object\-signing
certificate\&. When it is imported into browser software such as Communicator,
it behaves like an object\-signing CA and cannot be used to sign objects\&. The
\-G option is available in Netscape Signing Tool 1\&.0 and later versions
only\&. By default, it produces only RSA certificates with 1024\-byte keys in
the internal token\&. However, you can use the \-s option specify the required
key size and the \-t option to specify the token\&.
Longest line is: 1678 characters.
-.-.
Only one space character is after a possible end of sentence
(after a punctuation, that can end a sentence).
[List of affected lines removed.]
-.-.
Put a subordinate sentence (after a comma) on a new line.
[List of affected lines removed.]
-.-.
Remove quotes when there is a printable
but no space character between them
and the quotes are not for emphasis (markup),
for example as an argument to a macro.
signtool.1:10:.TH "SIGNTOOL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
signtool.1:30:.SH "NAME"
signtool.1:32:.SH "SYNOPSIS"
signtool.1:35:.SH "STATUS"
signtool.1:39:.SH "DESCRIPTION"
signtool.1:65:.SH "OPTIONS"
signtool.1:668:.SH "AUTHORS"
signtool.1:673:.SH "LICENSE"
signtool.1:676:.SH "NOTES"
-.-.
Use ".na" (no adjustment) instead of ".ad l" (and ".ad" to begin the
same adjustment again as before).
26:.ad l
-.-.
Section headings (.SH and .SS) do not need quoting their arguments.
30:.SH "NAME"
32:.SH "SYNOPSIS"
35:.SH "STATUS"
39:.SH "DESCRIPTION"
65:.SH "OPTIONS"
203:.SH "THE COMMAND FILE FORMAT"
328:.SH "EXTENDED EXAMPLES"
633:.SH "SEE ALSO"
660:.SH "ADDITIONAL RESOURCES"
668:.SH "AUTHORS"
673:.SH "LICENSE"
676:.SH "NOTES"
-.-.
Remove excessive "\&" when it has no functional purpose.
38:\m[blue]\fBMozilla NSS bug 836477\fR\m[]\&\s-2\u[1]\d\s+2
-.-.
Use "\-" instead of "-" in web addresses.
16:.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
-.-.
Put a (long) web address on a new line to reduce the posibility of
splitting the address between two output lines.
Or inhibit hyphenation with "\%" in front of the name.
647:https://wiki\&.mozilla\&.org/NSS_Shared_DB_Howto
658:https://wiki\&.mozilla\&.org/NSS_Shared_DB
663:\m[blue]\fBhttp://www\&.mozilla\&.org/projects/security/pki/nss/\fR\m[]\&;.
The NSS site relates directly to NSS code changes and releases\&.
665:Mailing lists: https://lists\&.mozilla\&.org/listinfo/dev\-tech\-crypto
675:Licensed under the Mozilla Public License, v\&. 2\&.0\&. If a copy of the
MPL was not distributed with this file, You can obtain one at
http://mozilla\&.org/MPL/2\&.0/\&;.
680:\%https://bugzilla.mozilla.org/show_bug.cgi?id=836477
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z
":
troff:<stdin>:340: warning: trailing space in the line
troff:<stdin>:342: warning: trailing space in the line
troff:<stdin>:343: warning: trailing space in the line
troff:<stdin>:344: warning: trailing space in the line
troff:<stdin>:345: warning: trailing space in the line
troff:<stdin>:346: warning: trailing space in the line
troff:<stdin>:347: warning: trailing space in the line
troff:<stdin>:348: warning: trailing space in the line
troff:<stdin>:349: warning: trailing space in the line
troff:<stdin>:350: warning: trailing space in the line
troff:<stdin>:351: warning: trailing space in the line
troff:<stdin>:352: warning: trailing space in the line
troff:<stdin>:353: warning: trailing space in the line
troff:<stdin>:354: warning: trailing space in the line
troff:<stdin>:355: warning: trailing space in the line
troff:<stdin>:356: warning: trailing space in the line
troff:<stdin>:359: warning: trailing space in the line
troff:<stdin>:383: warning: trailing space in the line
troff:<stdin>:474: warning: trailing space in the line
troff:<stdin>:476: warning: trailing space in the line
troff:<stdin>:477: warning: trailing space in the line
troff:<stdin>:478: warning: trailing space in the line
troff:<stdin>:479: warning: trailing space in the line
troff:<stdin>:480: warning: trailing space in the line
troff:<stdin>:545: warning: trailing space in the line
troff:<stdin>:546: warning: trailing space in the line
troff:<stdin>:547: warning: trailing space in the line
troff:<stdin>:548: warning: trailing space in the line
troff:<stdin>:549: warning: trailing space in the line
troff:<stdin>:550: warning: trailing space in the line
troff:<stdin>:551: warning: trailing space in the line
troff:<stdin>:552: warning: trailing space in the line
troff:<stdin>:553: warning: trailing space in the line
troff:<stdin>:554: warning: trailing space in the line
troff:<stdin>:555: warning: trailing space in the line
troff:<stdin>:556: warning: trailing space in the line
troff:<stdin>:557: warning: trailing space in the line
troff:<stdin>:558: warning: trailing space in the line
troff:<stdin>:559: warning: trailing space in the line
troff:<stdin>:560: warning: trailing space in the line
troff:<stdin>:561: warning: trailing space in the line
troff:<stdin>:562: warning: trailing space in the line
-.-.
Generally:
Split (sometimes) lines after a punctuation mark; before a conjunction.
--- signtool.1 2025-03-28 16:55:56.908495598 +0000
+++ signtool.1.new 2025-03-28 17:21:24.071568276 +0000
@@ -337,26 +337,26 @@ You use the \-L option to list the nickn
.RS 4
.\}
.nf
-signtool \-L
+signtool \-L
-using certificate directory: /u/jsmith/\&.netscape
-S Certificates
-\- \-\-\-\-\-\-\-\-\-\-\-\-
- BBN Certificate Services CA Root 1
- IBM World Registry CA
- VeriSign Class 1 CA \- Individual Subscriber \- VeriSign, Inc\&.
- GTE CyberTrust Root CA
- Uptime Group Plc\&. Class 4 CA
-* Verisign Object Signing Cert
- Integrion CA
- GTE CyberTrust Secure Server CA
- AT&T Directory Services
-* test object signing cert
- Uptime Group Plc\&. Class 1 CA
- VeriSign Class 1 Primary CA
+using certificate directory: /u/jsmith/\&.netscape
+S Certificates
+\- \-\-\-\-\-\-\-\-\-\-\-\-
+ BBN Certificate Services CA Root 1
+ IBM World Registry CA
+ VeriSign Class 1 CA \- Individual Subscriber \- VeriSign, Inc\&.
+ GTE CyberTrust Root CA
+ Uptime Group Plc\&. Class 4 CA
+* Verisign Object Signing Cert
+ Integrion CA
+ GTE CyberTrust Secure Server CA
+ AT&T Directory Services
+* test object signing cert
+ Uptime Group Plc\&. Class 1 CA
+ VeriSign Class 1 Primary CA
\- \-\-\-\-\-\-\-\-\-\-\-\-
-Certificates that can be used to sign objects have *\*(Aqs to their left\&.
+Certificates that can be used to sign objects have *\*(Aqs to their left\&.
.fi
.if n \{\
.RE
@@ -380,7 +380,7 @@ Verisign Object Signing Cert
Issued by: VeriSign, Inc\&. \- Verisign, Inc\&.
Expires: Tue May 19, 1998
test object signing cert
- Issued by: test object signing cert (Signtool 1\&.0 Testing
+ Issued by: test object signing cert (Signtool 1\&.0 Testing
Certificate (960187691))
Expires: Sun May 17, 1998
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
@@ -471,13 +471,13 @@ To use Netscape Signing Tool with a ZIP
.RS 4
.\}
.nf
-cd signdir
+cd signdir
- zip \-r \&.\&./myjar\&.jar *
- adding: META\-INF/ (stored 0%)
- adding: META\-INF/manifest\&.mf (deflated 15%)
- adding: META\-INF/signtool\&.sf (deflated 28%)
- adding: META\-INF/signtool\&.rsa (stored 0%)
+ zip \-r \&.\&./myjar\&.jar *
+ adding: META\-INF/ (stored 0%)
+ adding: META\-INF/manifest\&.mf (deflated 15%)
+ adding: META\-INF/signtool\&.sf (deflated 28%)
+ adding: META\-INF/signtool\&.rsa (stored 0%)
adding: text\&.txt (stored 0%)
.fi
.if n \{\
@@ -542,24 +542,24 @@ You can use the \-M option to list the P
signtool \-d "c:\enetscape\eusers\ejsmith" \-M
using certificate directory: c:\enetscape\eusers\eusername
-Listing of PKCS11 modules
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
- 1\&. Netscape Internal PKCS #11 Module
- (this module is internally loaded)
- slots: 2 slots attached
- status: loaded
- slot: Communicator Internal Cryptographic Services Version 4\&.0
- token: Communicator Generic Crypto Svcs
- slot: Communicator User Private Key and Certificate Services
- token: Communicator Certificate DB
- 2\&. CryptOS
- (this is an external module)
- DLL name: core32
- slots: 1 slots attached
- status: loaded
- slot: Litronic 210
- token:
-
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+Listing of PKCS11 modules
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ 1\&. Netscape Internal PKCS #11 Module
+ (this module is internally loaded)
+ slots: 2 slots attached
+ status: loaded
+ slot: Communicator Internal Cryptographic Services Version 4\&.0
+ token: Communicator Generic Crypto Svcs
+ slot: Communicator User Private Key and Certificate Services
+ token: Communicator Certificate DB
+ 2\&. CryptOS
+ (this is an external module)
+ DLL name: core32
+ slots: 1 slots attached
+ status: loaded
+ slot: Litronic 210
+ token:
+
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
.fi
.if n \{\
.RE
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
The same goes for man pages that are used as an input.
For a style guide use
mandoc -T lint
-.-
Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
It should also check its input files for too long (> 80) lines.
This is just a simple quality control measure.
The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
"git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")
Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced.
The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.
See man-pages(7), item "semantic newline".
-.-
The difference between the formatted output of the original and patched file
can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -d -u <out1> <out2>
and for groff, using
\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output from 'diff -d -u ...' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option \"-warnings=w\"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT=\"-ww -b -z\"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-
