bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #65936] [grohtml] litters working directory with 0-length image fil


From: Dave
Subject: [bug #65936] [grohtml] litters working directory with 0-length image files
Date: Mon, 8 Jul 2024 19:04:58 -0400 (EDT)

Follow-up Comment #6, bug #65936 (group groff):

[comment #3 comment #3:]
> We do have the following recent note in our "PROBLEMS" file
> (unfortunately, I think most distributors don't ship it, and
> to be fair we don't install it).

Bug #61950 seeks to give user-relevant items in this file more visibility.

> * When I run "groff -Thtml", I get complaints from pnmcrop.
> 
>   pnmcrop: The image is entirely background; there is nothing to crop.
> 
> This appears to be two bugs in Netpbm 11.01.00 through 11.3.5 at least;

The "at least" range can potentially be widened: I have Netpbm 10.70.0 and get
the warning, though only when giving -Thtml to the latest groff, not groff
1.22.4.  But because this item was only recently added to PROBLEMS, I presume
some recent groff change provoked the warning.

> the diagnostic is spurious, and pnmcrop is ignoring or overriding the
> "-quiet" option that the pre-grohtml(1) program passes to it.

The diagnostic certainly seems to be spurious for me; as I mentioned, my
generated .png files look fine.

Curiously, "-quiet" seems to be an undocumented option in this version of
pnmcrop.

$ pnmcrop -quiet /dev/null
pnmcrop: Error reading magic number from Netpbm image stream.  Most often,
this means your input file is empty.
$ pnmcrop -loud /dev/null
unrecognized option '-loud'.  Recognized options are: -black -white -sides
-left -right -top -bottom -verbose -margin -borderfile




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65936>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]