pdftocairo.1: Some remarks and a patch with editorial changes for this man page

Bjarni Ingi Gislason bjarniig at simnet.is
Wed Aug 12 23:13:57 BST 2026


Package: poppler-utils
Version: 26.07.0-2
Severity: minor
Tags: patch

  Additional remarks.

  Mails from me to "submit at bugs.debian.org" are no longer acknowledged.  A
Debian maintainer told me, that he would contact the mail administrator
about me not wanting to send bugs upstream.

-.-

Dear Maintainer,

>From "/usr/share/doc/debian/bug-reporting.txt.gz":

  Don't file bugs upstream

   If you file a bug in Debian, don't send a copy to the upstream software
   maintainers yourself, as it is possible that the bug exists only in
   Debian. If necessary, the maintainer of the package will forward the
   bug upstream.

-.-

  For forwarding bug reports to upstream see:

https://www.debian.org/Bugs/Developer#forward

-.-

  "Handling bug reports" in
http://people.debian.org/~enrico/dcg/ch03s02.html

-.-

  I do not send reports upstream if I have to get an account there.
The Debian maintainers have one already.

-.-

   * 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=0 -ww -z < "man page"

  [Use 

grep -n -e ' $' -e '\\~$' -e ' \\f.$' -e ' \\"' -e ' "$' <file>

  to find (most) 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?

Output from "test-groff  -mandoc  -K utf8 -rF0 -rHY=0 -ww -z ":

an.tmac:<stdin>:1: style: .TH missing third argument; consider document modification date in ISO 8601 format (YYYY-MM-DD)
an.tmac:<stdin>:1: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0")
an.tmac:<stdin>:7: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:39: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:43: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:46: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:49: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:51: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:74: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:77: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:80: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:83: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:86: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:89: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:92: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:95: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:98: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:103: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:119: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:223: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:236: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:239: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:243: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:248: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:253: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:263: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:269: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:311: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:314: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:318: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:324: warning: trailing whitespace [-w trail]
an.tmac:<stdin>:327: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:331: style: .BI expects at least 2 arguments, got 1

Output from "test-nroff  -mandoc  -K utf8 -rF0 -rHY=0 -ww -z ":

an.tmac:<stdin>:1: style: .TH missing third argument; consider document modification date in ISO 8601 format (YYYY-MM-DD)
an.tmac:<stdin>:1: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0")
an.tmac:<stdin>:7: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:39: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:43: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:46: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:49: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:51: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:74: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:77: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:80: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:83: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:86: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:89: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:92: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:95: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:98: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:103: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:119: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:223: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:236: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:239: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:243: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:248: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:253: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:263: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:269: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:311: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:314: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:318: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:324: warning: trailing whitespace [-w trail]
an.tmac:<stdin>:327: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:331: style: .BI expects at least 2 arguments, got 1


   * 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: forky/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 7.1.7+deb14-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 poppler-utils depends on:
ii  libc6          2.42-17
ii  libcairo2      1.18.4-3+b1
ii  libfreetype6   2.14.3+dfsg-2
ii  liblcms2-2     2.19.1-1
ii  libpoppler162  26.07.0-2
ii  libstdc++6     16.1.0-3

poppler-utils recommends no packages.

poppler-utils suggests no packages.

-- no debconf information
-------------- next part --------------
Input file is pdftocairo.1

Output from "mandoc -T lint  pdftocairo.1": (shortened list)

     35 STYLE: input text line longer than 80 bytes
      1 STYLE: whitespace at end of input line
      1 WARNING: missing date, using "": TH
      1 WARNING: skipping paragraph macro: PP empty


Find trailing whitespace with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' -e ' "$' <man page>

-.-.

Output from
test-groff mandoc -Kutf8 -ww -z pdftocairo.1: (shortened list)

     16 .BI expects at least 2 arguments, got 1
      6 .IR expects at least 2 arguments, got 1
      1 .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0")
      1 .TH missing third argument; consider document modification date in ISO 8601 format (YYYY-MM-DD)
      2 1 leading space(s) on input line
      8 end of sentence detected before end of text line [-w style]
      1 trailing whitespace [-w trail]

Find (most) trailing whitespace with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' -e ' "$' <man page>

-.-.

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".

See more information in the attachment "trailing whitespace".

Number of lines affected is

1

-.-.

Change '-' (\-) to '\(en' (en-dash) for a (numeric) range.

GNU gnulib has recently (2023-06-18) updated its
"build_aux/update-copyright" to recognize "\(en" in man pages.

  '-' is rendered as a hyphen (u2010) in UTF-8 encoding.

pdftocairo.1:337:The pdftocairo software and documentation are copyright 1996-2004 Glyph
pdftocairo.1:338:& Cog, LLC and copyright 2005-2011 The Poppler Developers.

-.-.

Change - to \- if it shall be printed as a minus sign.

pdftocairo.1:138:scale-to-y is set to -1, the vertical size will determined by the
pdftocairo.1:143:is set to -1, the horizontal size will determined by the aspect ratio

-.-.

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.

101: The output file '-' can not be used with this option.
138:scale-to-y is set to -1, the vertical size will determined by the
143:is set to -1, the horizontal size will determined by the aspect ratio
266:in the print properties dialog will be used except when -origpagesizes is specified.

-.-.

Wrong distance (not two spaces, not a new line character (\n)) 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 (fill completely
an A4 sized page line on a terminal)
into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

[List of affected lines removed.]

Longest line is number 54 with 175 characters
Not all options are valid with all output formats. One (and only one) of the output format options (\-png, \-jpeg, \-tiff, \-pdf, \-print, \-ps, \-eps, or \-svg) must be used.

-.-.

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.]

-.-.

Only one space character is after a possible end of sentence
(after a punctuation, that can end a sentence).
Start a new sentence on a new line.

[List of affected lines removed.]

-.-.

Output from "test-groff  -mandoc  -K utf8 -rF0 -rHY=0 -ww -z ":

an.tmac:<stdin>:1: style: .TH missing third argument; consider document modification date in ISO 8601 format (YYYY-MM-DD)
an.tmac:<stdin>:1: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0")
an.tmac:<stdin>:7: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:39: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:43: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:46: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:49: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:51: style: .IR expects at least 2 arguments, got 1
an.tmac:<stdin>:74: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:77: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:80: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:83: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:86: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:89: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:92: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:95: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:98: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:103: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:119: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:223: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:236: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:239: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:243: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:248: warning: end of sentence detected before end of text line [-w style]
troff:<stdin>:253: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:263: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:269: warning: end of sentence detected before end of text line [-w style]
an.tmac:<stdin>:311: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:314: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:318: style: .BI expects at least 2 arguments, got 1
troff:<stdin>:324: warning: trailing whitespace [-w trail]
an.tmac:<stdin>:327: style: .BI expects at least 2 arguments, got 1
an.tmac:<stdin>:331: style: .BI expects at least 2 arguments, got 1


-.-

Generally:

Split (sometimes) lines after a punctuation mark; before a conjunction.

Adjustment to both margins and hyphenation are unnecessary (and just waste
resources) in nroff mode for man pages; add

.if n \{\
.  nh
.  nr HY 0
.  ad l
.  ds AD l
.\}

-.-

Tables:

  Use the preprocessor 'tbl' to make tables.

  Put data, that are wider than the header in the (centered) last column,
in a "T{...\nT}" block(, when the table gets wider than the output line).

  Table headings, that are wider than any data in the corresponding
column, do not need to be centered, so left adjustment (l, L) is
sufficient.  There is thereby no change in the standard output.
-------------- next part --------------
--- pdftocairo.1	2026-08-12 20:59:41.989467211 +0000
+++ pdftocairo.1.new	2026-08-12 22:09:17.354942518 +0000
@@ -4,7 +4,7 @@ pdftocairo \- Portable Document Format (
 .SH SYNOPSIS
 .B pdftocairo
 [options]
-.IR PDF-file
+.I PDF-file
 .RI [ output-file ]
 .SH DESCRIPTION
 .B pdftocairo
@@ -36,19 +36,19 @@ The image formats (PNG, JPEG, and TIFF)
 When \-singlefile is used with the image formats, the file type is appended to
 .IR output-file .
 When the output format is a vector format (PDF, PS, EPS, and SVG),
-.IR output-file
+.I output-file
 is the full filename.
 
 If the
-.IR PDF-file
+.I PDF-file
 is \*(lq\-\*(rq , the PDF is read from stdin.
 If the
-.IR output-file
+.I output-file
 is \*(lq\-\*(rq , the output file will be written to stdout. Using stdout is not valid with image formats unless \-singlefile is used.
 If
-.IR output-file
+.I output-file
 is not used, the output filename will be derived from the
-.IR PDF-file
+.I PDF-file
 filename.
 .PP
 Not all options are valid with all output formats. One (and only one) of the output format options (\-png, \-jpeg, \-tiff, \-pdf, \-print, \-ps, \-eps, or \-svg) must be used.
@@ -71,36 +71,36 @@ at the top left (SVG) or bottom left (PD
 .PP
 .SH OPTIONS
 .TP
-.BI \-png
+.B \-png
 Generates a PNG file(s)
 .TP
-.BI \-jpeg
+.B \-jpeg
 Generates a JPEG file(s). See also \-jpegopt.
 .TP
-.BI \-tiff
+.B \-tiff
 Generates a TIFF file(s)
 .TP
-.BI \-pdf
+.B \-pdf
 Generates a PDF file
 .TP
-.BI \-ps
+.B \-ps
 Generate a PS file
 .TP
-.BI \-eps
+.B \-eps
 Generate an EPS file. An EPS file contains a single image, so if you
 use this option with a multi-page PDF file, you must use \-f and \-l
 to specify a single page.  The page size options (\-origpagesizes,
 \-paper, \-paperw, \-paperh) can not be used with this option.
 .TP
-.BI \-svg
+.B \-svg
 Generate a SVG (Scalable Vector Graphics) file
 .TP
-.BI \-print
+.B \-print
 (Windows only) Prints to a system printer. See also \-printer and \-printeropt.
  If an output file is not specified, the output will be sent to the printer.
- The output file '-' can not be used with this option.
+ The output file '\-' can not be used with this option.
 .TP
-.BI \-printdlg
+.B \-printdlg
 (Windows only) Prints to a system printer. Displays the print dialog to allow
 the print options to be modified before printing.
 .TP
@@ -116,7 +116,7 @@ Generates only the odd numbered pages.
 .B \-e
 Generates only the even numbered pages.
 .TP
-.BI \-singlefile
+.B \-singlefile
 Writes only the first page and does not add digits.
 .TP
 .BI \-r " number"
@@ -135,12 +135,12 @@ side will be determined by the aspect ra
 .TP
 .BI \-scale-to-x " number"
 Scales each page horizontally to fit in scale-to-x pixels. If
-scale-to-y is set to -1, the vertical size will determined by the
+scale-to-y is set to \-1, the vertical size will determined by the
 aspect ratio of the page (PNG/JPEG/TIFF only).
 .TP
 .BI \-scale-to-y " number"
 Scales each page vertically to fit in scale-to-y pixels. If scale-to-x
-is set to -1, the horizontal size will determined by the aspect ratio
+is set to \-1, the horizontal size will determined by the aspect ratio
 of the page (PNG/JPEG/TIFF only).
 .TP
 .BI \-x " number"
@@ -260,10 +260,10 @@ PostScript file (PS only).  This tells t
 .B WINDOWS PRINTER OPTIONS
 for the available options.
 .TP
-.BI \-setupdlg
+.B \-setupdlg
 (Windows only). When used with \-print, the printer properties dialog is displayed
 allowing the print settings to be modified before printing. The paper size selected
-in the print properties dialog will be used except when -origpagesizes is specified.
+in the print properties dialog will be used except when \-origpagesizes is specified.
 .TP
 .BI \-opw " password"
 Specify the owner password for the PDF file.  Providing this will
@@ -308,34 +308,34 @@ Other error.
 When JPEG output is specified, the \-jpegopt option can be used to control the JPEG compression parameters.
 It takes a string of the form "<opt>=<val>[,<opt>=<val>]". Currently the available options are:
 .TP
-.BI quality
+.B quality
 Selects the JPEG quality value. The value must be an integer between 0 and 100.
 .TP
-.BI progressive
+.B progressive
 Select progressive JPEG output. The possible values are "y", "n",
 indicating progressive (yes) or non-progressive (no), respectively.
 .TP
-.BI optimize
+.B optimize
 Sets whether to compute optimal Huffman coding tables for the JPEG output, which
 will create smaller files but make an extra pass over the data. The value must
 be "y" or "n", with "y" performing optimization, otherwise the default Huffman
 tables are used.
 .SH WINDOWS PRINTER OPTIONS
-In Windows, you can use the \-print option to print directly to a system printer. Additionally, you can use the \-printopt 
+In Windows, you can use the \-print option to print directly to a system printer. Additionally, you can use the \-printopt
 option to configure the printer. It takes a string of the form "<opt>=<val>[,<opt>=<val>]". Currently the available options are:
 .TP
-.BI source
+.B source
 Selects the source paper tray to be used (bin). The possible values are "upper", "onlyone", "lower", "middle", "manual", "envelope",
 "envmanual", "auto", "tractor", "smallfmt", "largefmt", "largecapacity", "formsource", or a numeric value to choose a driver specific source.
 .TP
-.BI duplex
+.B duplex
 Sets the duplex mode of the printer. The possible values are "off", "short" or "long",
 indicating no duplexing, short-edge binding, or long-edge binding, respectively.
 General option \-duplex is a synonym of "duplex=long". If both options are specified,
 \-printopt has priority.
 .SH AUTHOR
-The pdftocairo software and documentation are copyright 1996-2004 Glyph
-& Cog, LLC and copyright 2005-2011 The Poppler Developers.
+The pdftocairo software and documentation are copyright 1996\(en2004 Glyph
+& Cog, LLC and copyright 2005\(en2011 The Poppler Developers.
 .SH "SEE ALSO"
 .BR pdfdetach (1),
 .BR pdffonts (1),
-------------- next part --------------
  Check the output from "lintian" in the Debian distribution.

  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>

  To find most trailing spaces use

grep -n -e ' $' -e ' \\f.$' -e ' \\"' -e ' "$' <man page>

  The same goes for man pages that are used as an input.

-.-

  For a style guide use

  mandoc -T lint

-.-

  For general input conventions consult the man page "nroff(7)" (item
"Input conventions") or the Texinfo manual about the same item.

-.-

  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 when that has been fixed.

  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)

-.-
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: clean files of trailing whitespace
Date: no date
Size: 498
URL: <http://alioth-lists.debian.net/pipermail/pkg-freedesktop-maintainers/attachments/20260812/4b0d0c53/attachment-0001.eml>


More information about the Pkg-freedesktop-maintainers mailing list