Package: texlive-base
Version: 2024.20250114-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 "groff -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>:142: 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.12-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 texlive-base depends on:
ii debconf [debconf-2.0] 1.5.89
ii libpaper-utils 2.2.5-0.3+b1
ii sensible-utils 0.0.24
ii tex-common 6.18
ii texlive-binaries 2024.20240313.70630+ds-5+b1
ii ucf 3.0049
ii xdg-utils 1.2.1-2
Versions of packages texlive-base recommends:
ii lmodern 2.005-1
Versions of packages texlive-base suggests:
ii ghostscript [postscript-viewer] 10.04.0~dfsg-2+b1
ii gv [postscript-viewer] 1:3.7.4-2+b2
ii mupdf [pdf-viewer] 1.25.1+ds1-5+b1
pn perl-tk <none>
ii xpdf [pdf-viewer] 3.04+git20250103-1+b1
pn xzdec <none>
Versions of packages tex-common depends on:
ii ucf 3.0049
Versions of packages tex-common suggests:
pn debhelper <none>
Versions of packages texlive-base is related to:
ii tex-common 6.18
ii texlive-binaries 2024.20240313.70630+ds-5+b1
-- debconf information excluded
Input file is updmap.cfg.5
Output from "mandoc -T lint updmap.cfg.5": (shortened list)
1 filename/section mismatch: *.5 vs TH ... 2
1 input text line longer than 80 bytes: Configures if \fBdvi...
7 whitespace at end of input line
Remove trailing space with: sed -e 's/ *$//'
-.-.
Output from "test-groff -mandoc -t -ww -z updmap.cfg.5": (shortened list)
1 trailing space in the line
Remove trailing space with: sed -e 's/ *$//'
-.-.
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
7
-.-.
Change two HYPHEN-MINUSES (code 0x2D) to an em-dash (\(em),
if one is intended.
" \(em " creates a too big gap in the text (in "troff").
An en-dash is usually surrounded by a space,
while an em-dash is used without spaces.
"man" (1 byte characters in input) transforms an en-dash (\(en) to one
HYPHEN-MINUS,
and an em-dash to two HYPHEN-MINUSES without considering the space
around it.
If "--" are two single "-"
(begin of an option or end of options)
then use "\-\-".
updmap.cfg.5:33:an ideal world, updmap would be unnecessary -- each of these
programs
updmap.cfg.5:42:Running "updmap --help" will output the main documentation for
using
updmap.cfg.5:138:(de-)activated using \fBupdmap\fR with the options
\fI--enable\fR and
updmap.cfg.5:139:\fI--disable\fR, respectively.
-.-.
Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-
42:Running "updmap --help" will output the main documentation for using
138:(de-)activated using \fBupdmap\fR with the options \fI--enable\fR and
139:\fI--disable\fR, respectively.
-.-.
Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff \[u2010] or \[hy]) in the output.
42:Running "updmap --help" will output the main documentation for using
52:\fBdvips\fR \fI-Poutline\fR (resp. \fBdvips\fR \fI-Ppk\fR).
75:The user can override the default by specifying \fBdvips\fR
\fI-Pdownload35\fR
76:(resp. \fBdvips\fR \fI-Pbuiltin35\fR) to download the LW35 fonts
138:(de-)activated using \fBupdmap\fR with the options \fI--enable\fR and
139:\fI--disable\fR, respectively.
-.-.
Add a "\&" after "e.g." and "i.e.", or use English words
(man-pages(7)).
Abbreviation points should be protected against being interpreted as
an end of sentence, if they are not, and that independent of the
current place on the line.
61:URW: URW fonts with "vendor" filenames (e.g. n019064l.pfb)
63:URWkb: URW fonts with "berry" filenames (e.g. uhvbo8ac.pfb)
65:ADOBE: Adobe fonts with "vendor" filenames (e.g. hvnbo___.pfb)
67:ADOBEkb: Adobe fonts with "berry" filenames (e.g. phvbo8an.pfb)
-.-.
Wrong distance 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 b6gin on a new line.
25:teTeX system and is read by \fBupdmap\fP(1). It describes if and how
26:fonts should be included (or not included) into PS-/PDF-files. This
48:if both are available? Independent of this setting, outlines can be forced
49:by putting "p psfonts_t1.map" into a config file that dvips reads. Bitmaps
50:can be forced by putting "p psfonts_pk.map" into a config file. We provide
52:\fBdvips\fR \fI-Poutline\fR (resp. \fBdvips\fR \fI-Ppk\fR).
59:how are the filenames chosen? Valid settings:
61:URW: URW fonts with "vendor" filenames (e.g. n019064l.pfb)
63:URWkb: URW fonts with "berry" filenames (e.g. uhvbo8ac.pfb)
65:ADOBE: Adobe fonts with "vendor" filenames (e.g. hvnbo___.pfb)
67:ADOBEkb: Adobe fonts with "berry" filenames (e.g. phvbo8an.pfb)
76:(resp. \fBdvips\fR \fI-Pbuiltin35\fR) to download the LW35 fonts
77:(resp. use the built-in fonts).
83:Should \fBpdftex\fR download the 14 base PDF fonts? Since some configurations
85:the fonts. The pdf files get bigger, but that is the cost.
88:download the fonts). Adobe recommends embedding all fonts.
92:Should special map files for pxdvi be created? pxdvi is an adaption of xdvi
96:Valid settings are \fItrue\fR (generate configuration) or \fIfalse\fR. See
121:Similar to \fBMap\fR. It should be used when there is Type1 and a bitmap
122:implementation of the font (the latter mostly coming from MetaFont). These
130:Similar to \fBMap\fR. This should be used for kanji fonts.
137:\fB#!\fR at the beginning of the line. Such entries can be
145:\fBupdmap.cfg\fR and rewriting some of them. It may be used by other
146:distributions without contacting the author. Any mistakes or omissions in
-.-.
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.
Line 47, length 82
Configures if \fBdvips\fR (by default) should prefer bitmap fonts or outline
fonts
-.-.
The name of a man page is typeset in bold and the section in roman
(see man-pages(7)).
151:updmap(1), dvips(1)
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
Not considered in a patch, too many lines.
updmap.cfg.5:26:fonts should be included (or not included) into PS-/PDF-files.
This
updmap.cfg.5:27:works for Outline (Postscript Type1) and Bitmap Fonts
(Postscript
updmap.cfg.5:47:Configures if \fBdvips\fR (by default) should prefer bitmap
fonts or outline fonts
updmap.cfg.5:52:\fBdvips\fR \fI-Poutline\fR (resp. \fBdvips\fR \fI-Ppk\fR).
updmap.cfg.5:61:URW: URW fonts with "vendor" filenames (e.g. n019064l.pfb)
updmap.cfg.5:63:URWkb: URW fonts with "berry" filenames (e.g. uhvbo8ac.pfb)
updmap.cfg.5:65:ADOBE: Adobe fonts with "vendor" filenames (e.g. hvnbo___.pfb)
updmap.cfg.5:67:ADOBEkb: Adobe fonts with "berry" filenames (e.g. phvbo8an.pfb)
updmap.cfg.5:71:Configures if \fBdvips\fR (by default) should download the 35
base
updmap.cfg.5:72:PostScript fonts into the document (set \fItrue\fR) or should
these
updmap.cfg.5:73:fonts be used from the ps interpreter / printer (set
\fIfalse\fR).
updmap.cfg.5:87:Valid settings are \fItrue\fR (download the fonts) or
\fIfalse\fR (don't
updmap.cfg.5:96:Valid settings are \fItrue\fR (generate configuration) or
\fIfalse\fR. See
updmap.cfg.5:122:implementation of the font (the latter mostly coming from
MetaFont). These
-.-.
No need for "\&" to be in front of a period (.),
if there is a character in front of it
32:\fBgsftopk\fP(1), and \fBdvipdfmx\fP(1)\&. In
35:available and how they should be treated\&. As things stand, however,
37:needs its own font configuration file\&. \fBupdmap\fP creates font
40:configuration files in sync\&.
-.-.
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.
19:.TH "UPDMAP.CFG" "20" "November 2012" "TeX Live" "TeX Live"
20:.SH "NAME"
23:.SH "DESCRIPTION"
141:.SH "AUTHOR"
-.-.
Section headings (.SH and .SS) do not need quoting.
20:.SH "NAME"
23:.SH "DESCRIPTION"
141:.SH "AUTHOR"
150:.SH "SEE ALSO"
153:.SH "THANKS TO"
-.-.
Remove excessive "\&" when it has no functional purpose.
32:\fBgsftopk\fP(1), and \fBdvipdfmx\fP(1)\&. In
35:available and how they should be treated\&. As things stand, however,
37:needs its own font configuration file\&. \fBupdmap\fP creates font
40:configuration files in sync\&.
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z
":
troff:<stdin>:142: warning: trailing space in the line
--- updmap.cfg.5 2025-02-17 09:34:35.656735074 +0000
+++ updmap.cfg.5.new 2025-02-17 10:06:25.696260222 +0000
@@ -1,70 +1,85 @@
.\" Hey, Emacs! This is an -*- nroff -*- source file.
.\"
.\" Copyright (C) 2004, 2012 Hilmar Preusse <hill...@web.de>
-.\" Copyright (C) 2012 Norbert Preining <prein...@logic.at>
-.\"
+.\" Copyright (C) 2012 Norbert Preining <prein...@logic.at>
+.\"
.\" This is free software; you can redistribute it and/or modify it under
.\" the terms of the GNU General Public License as published by the Free
.\" Software Foundation; either version 2, or (at your option) any later
.\" version.
-.\"
+.\"
.\" This is distributed in the hope that it will be useful, but WITHOUT
.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
.\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
.\" for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
+.\"
+.\" You should have received a copy of the GNU General Public License
.\" along with this program. if not, see <http://www.gnu.org/licenses/>.
-.\"
-.TH "UPDMAP.CFG" "20" "November 2012" "TeX Live" "TeX Live"
-.SH "NAME"
+.\"
+.TH UPDMAP.CFG 20 "November 2012" "TeX Live" "TeX Live"
+.SH NAME
\fBupdmap.cfg\fR \- configuration of font mapping/inclusion for dvips and
friends.
-.SH "DESCRIPTION"
+.SH DESCRIPTION
The file \fBupdmap.cfg\fR is the central font configuration file of a
-teTeX system and is read by \fBupdmap\fP(1). It describes if and how
-fonts should be included (or not included) into PS-/PDF-files. This
-works for Outline (Postscript Type1) and Bitmap Fonts (Postscript
-Type3) mostly coming from MetaFont.
+teTeX system and is read by \fBupdmap\fP(1).
+It describes
+if and how fonts should be included
+(or not included)
+into PS-/PDF-files.
+This works for Outline (Postscript Type1)
+and Bitmap Fonts (Postscript Type3) mostly coming from MetaFont.
.PP
\fBupdmap\fP is a utility that creates font configuration files for
\fBdvips\fP(1), \fBpdftex\fP(1), \fBxdvi\fP(1), \fBps2pk\fP(1),
-\fBgsftopk\fP(1), and \fBdvipdfmx\fP(1)\&. In
-an ideal world, updmap would be unnecessary -- each of these programs
+\fBgsftopk\fP(1), and \fBdvipdfmx\fP(1).
+In an ideal world,
+updmap would be unnecessary \(en each of these programs
would read the same configuration file to learn what fonts are
-available and how they should be treated\&. As things stand, however,
+available and how they should be treated.
+As things stand,
+however,
each of these tools has subtly different requirements and thereby
-needs its own font configuration file\&. \fBupdmap\fP creates font
-configuration files for all of these programs from several sources,
-namely all \fBupdmap.cfg\fR, allowing you to easily keep all the different
-configuration files in sync\&.
+needs its own font configuration file.
+\fBupdmap\fP creates font configuration files for all of these programs
+from several sources,
+namely all \fBupdmap.cfg\fR,
+allowing you to easily keep all the different
+configuration files in sync.
.P
-Running "updmap --help" will output the main documentation for using
+Running "updmap \-\-help" will output the main documentation for using
\fBupdmap\fR.
.P
\fBdvipsPreferOutline\fR
.br
-Configures if \fBdvips\fR (by default) should prefer bitmap fonts or outline
fonts
-if both are available? Independent of this setting, outlines can be forced
-by putting "p psfonts_t1.map" into a config file that dvips reads. Bitmaps
-can be forced by putting "p psfonts_pk.map" into a config file. We provide
-such config files which can be enabled via
-\fBdvips\fR \fI-Poutline\fR (resp. \fBdvips\fR \fI-Ppk\fR).
+Configures
+if \fBdvips\fR
+(by default)
+should prefer bitmap fonts or outline fonts
+if both are available?
+Independent of this setting,
+outlines can be forced by putting "p psfonts_t1.map" into a config file
+that dvips reads.
+Bitmaps can be forced by putting "p psfonts_pk.map" into a config file.
+We provide such config files which can be enabled via
+\fBdvips\fR \fI\-Poutline\fR
+(resp.\& \fBdvips\fR \fI\-Ppk\fR).
.br
Valid settings for dvipsPreferOutline are \fItrue\fR / \fIfalse\fR.
.P
\fBLW35\fR
.br
Which fonts of the "Basic 35 Laserwriter Fonts" do you want to use and
-how are the filenames chosen? Valid settings:
+how are the filenames chosen?
+Valid settings:
.br
-URW: URW fonts with "vendor" filenames (e.g. n019064l.pfb)
+URW: URW fonts with "vendor" filenames (e.g.\& n019064l.pfb)
.br
-URWkb: URW fonts with "berry" filenames (e.g. uhvbo8ac.pfb)
+URWkb: URW fonts with "berry" filenames (e.g.\& uhvbo8ac.pfb)
.br
-ADOBE: Adobe fonts with "vendor" filenames (e.g. hvnbo___.pfb)
+ADOBE: Adobe fonts with "vendor" filenames (e.g.\& hvnbo___.pfb)
.br
-ADOBEkb: Adobe fonts with "berry" filenames (e.g. phvbo8an.pfb)
+ADOBEkb: Adobe fonts with "berry" filenames (e.g.\& phvbo8an.pfb)
.P
\fBdvipsDownloadBase35\fR
.br
@@ -72,28 +87,37 @@ Configures if \fBdvips\fR (by default) s
PostScript fonts into the document (set \fItrue\fR) or should these
fonts be used from the ps interpreter / printer (set \fIfalse\fR).
.br
-The user can override the default by specifying \fBdvips\fR \fI-Pdownload35\fR
-(resp. \fBdvips\fR \fI-Pbuiltin35\fR) to download the LW35 fonts
-(resp. use the built-in fonts).
+The user can override the default by specifying \fBdvips\fR \fI\-Pdownload35\fR
+(resp.\& \fBdvips\fR \fI\-Pbuiltin35\fR)
+to download the LW35 fonts
+(resp.\& use the built-in fonts).
.br
Valid settings are \fItrue\fR / \fIfalse\fR.
.P
\fBpdftexDownloadBase14\fR
.br
-Should \fBpdftex\fR download the 14 base PDF fonts? Since some configurations
-(ps / pdf tools / printers) use bad default fonts, it is safer to download
-the fonts. The pdf files get bigger, but that is the cost.
-.br
-Valid settings are \fItrue\fR (download the fonts) or \fIfalse\fR (don't
-download the fonts). Adobe recommends embedding all fonts.
+Should \fBpdftex\fR download the 14 base PDF fonts?
+Since some configurations
+(ps / pdf tools / printers)
+use bad default fonts,
+it is safer to download the fonts.
+The pdf files get bigger,
+but that is the cost.
+.br
+Valid settings are \fItrue\fR
+(download the fonts)
+or \fIfalse\fR
+(don't download the fonts).
+Adobe recommends embedding all fonts.
.P
\fBpxdviUse\fR
.br
-Should special map files for pxdvi be created? pxdvi is an adaption of xdvi
-with support for reading and displaying files generated by the ptex family
-of engines.
+Should special map files for pxdvi be created?
+pxdvi is an adaption of xdvi with support for reading
+and displaying files generated by the ptex family of engines.
.br
-Valid settings are \fItrue\fR (generate configuration) or \fIfalse\fR. See
+Valid settings are \fItrue\fR (generate configuration) or \fIfalse\fR.
+See
http://www.tug.org/texlive/updmap-kanji.html for detailed discussion.
.P
\fBkanjiEmbed\fR
@@ -101,55 +125,66 @@ http://www.tug.org/texlive/updmap-kanji.
\fBkanjiVariant\fR
.br
The options \fBkanjiEmbed\fR and \fBkanjiVariant\fR specify special
-replacements in the map lines. In a map, the string "@kanjiEmbed@"
-will be replaced by the value of that option; similarly for
-\fBkanjiVariant\fR. In this way, users of Japanese TeX can select
-different fonts to be included in the final output.
+replacements in the map lines.
+In a map,
+the string "@kanjiEmbed@" will be replaced by the value of that option;
+similarly for \fBkanjiVariant\fR.
+In this way,
+users of Japanese TeX can select different fonts to be included in the
+final output.
.P
\fBMap\fR
.br
-Points to a map file, which describes a mapping from a font (called in the TeX
-document) to the pfb file containing the Postscript code.
+Points to a map file,
+which describes a mapping from a font
+(called in the TeX document)
+to the pfb file containing the Postscript code.
.br
Usage: \fBMap\fR filename.map
.P
-The syntax of map files is the same as \fBdvips\fP(1) uses, see the
-section "psfonts.map" in the manual of \fBdvips\fP(1).
+The syntax of map files is the same as \fBdvips\fP(1) uses,
+see the section "psfonts.map" in the manual of \fBdvips\fP(1).
.P
\fBMixedMap\fR
.br
-Similar to \fBMap\fR. It should be used when there is Type1 and a bitmap
-implementation of the font (the latter mostly coming from MetaFont). These
-entries will not be used in the default map of \fBdvips\fR if
-\fBdvipsPreferOutline\fR is set to \fIfalse\fR.
+Similar to \fBMap\fR.
+It should be used
+when there is Type1 and a bitmap implementation of the font
+(the latter mostly coming from MetaFont).
+These entries will not be used in the default map of \fBdvips\fR
+if \fBdvipsPreferOutline\fR is set to \fIfalse\fR.
.br
Usage: \fBMixedMap\fR filename.map
.P
\fBKanjiMap\fR
.br
-Similar to \fBMap\fR. This should be used for kanji fonts.
+Similar to \fBMap\fR.
+This should be used for kanji fonts.
.br
Usage: \fBKanjiMap\fR filename.map
.P
The sign \fB#\fR precedes a comment.
.P
Map files not to be used should be commented out using the string
-\fB#!\fR at the beginning of the line. Such entries can be
-(de-)activated using \fBupdmap\fR with the options \fI--enable\fR and
-\fI--disable\fR, respectively.
+\fB#!\fR at the beginning of the line.
+Such entries can be
+(de-)activated using \fBupdmap\fR with the options \fI\-\-enable\fR and
+\fI\-\-disable\fR, respectively.
-.SH "AUTHOR"
-This manual page was written by Hilmar Preusse <hill...@web.de> and
-extended by Norbert Preining <prein...@logic.at>, for
-the Debian GNU/Linux system by simply copying the comments from
-\fBupdmap.cfg\fR and rewriting some of them. It may be used by other
-distributions without contacting the author. Any mistakes or omissions in
-the manual page are our fault; inquiries about or corrections to this manual
-page should be directed to tex-l...@tug.org.
+.SH AUTHOR
+This manual page was written by Hilmar Preusse <hill...@web.de> and
+extended by Norbert Preining <prein...@logic.at>,
+for the Debian GNU/Linux system by simply copying the comments from
+\fBupdmap.cfg\fR and rewriting some of them.
+It may be used by other
+distributions without contacting the author.
+Any mistakes or omissions in the manual page are our fault;
+inquiries about or corrections to this manual page
+should be directed to tex-l...@tug.org.
-.SH "SEE ALSO"
-updmap(1), dvips(1)
+.SH SEE ALSO
+.BR updmap "(1), " dvips (1)
-.SH "THANKS TO"
+.SH THANKS TO
Frank Kuester,
Thomas Esser.
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)
-.-
