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.

-.-

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

  If I get a negative (or no) response from upstream, I send henceforth
bugs to Debian.

-.-

   * 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 ' \\"' <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 -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":

troff:<stdin>:35: warning: trailing space in the line
troff:<stdin>:36: warning: trailing space in the line
troff:<stdin>:37: warning: trailing space in the line
troff:<stdin>:49: warning: trailing space in the line
troff:<stdin>:50: warning: trailing space in the line
troff:<stdin>:51: warning: trailing space in the line
troff:<stdin>:63: warning: trailing space in the line
troff:<stdin>:64: warning: trailing space in the line
troff:<stdin>:65: 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.

Hi,

  Thanks for your bugreport.

The pnginfo.1 is come from man/pnginfo.sgml.in,

it used docbook2man to get pnginfo.1.

Would you supply a patch for man/pnginfo.sgml.in?


Thanks!

在 2026/3/3 18:25, Bjarni Ingi Gislason via Pkg-phototools-devel 写道:

[...]

Hi,

  I do not know the SGML language.

  For the input file, it can be made better by

1) removing trailing spaces

2) beginning each sentence on a new line

3) start each markup on a new line

  as long as the translator accepts that.

  The main culprit is the translator.

  So the natural way is to send the maintainers of it the input file and
the content of my e-mail, showing the defects of the translations.

  Another possibility is to try other implementations of the translator.