summaryrefslogtreecommitdiffstats
path: root/upstream/opensuse-leap-15-6/man1/pamfixtrunc.1
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/opensuse-leap-15-6/man1/pamfixtrunc.1')
-rw-r--r--upstream/opensuse-leap-15-6/man1/pamfixtrunc.138
1 files changed, 38 insertions, 0 deletions
diff --git a/upstream/opensuse-leap-15-6/man1/pamfixtrunc.1 b/upstream/opensuse-leap-15-6/man1/pamfixtrunc.1
new file mode 100644
index 00000000..d6a64300
--- /dev/null
+++ b/upstream/opensuse-leap-15-6/man1/pamfixtrunc.1
@@ -0,0 +1,38 @@
+\
+.\" This man page was generated by the Netpbm tool 'makeman' from HTML source.
+.\" Do not hand-hack it! If you have bug fixes or improvements, please find
+.\" the corresponding HTML page on the Netpbm website, generate a patch
+.\" against that, and send it to the Netpbm maintainer.
+.TH "Pamfixtrunc User Manual" 0 "" "netpbm documentation"
+.PP
+\fBpamfixtrunc\fP was replaced in Netpbm 10.66 (March 2014) by
+.BR "pamfix" (1)\c
+\&.
+.PP
+\fBpamfix\fP with a \fB-truncate\fP option is the same thing as
+\fBpamfixtrunc\fP. But \fBpamfix\fP has other options to repair other
+kinds of corruption.
+.PP
+Another change that came with Netpbm 10.66 is that an invalid sample value
+(a value greater than the maxval the image declares in its header) is
+considered by the common Netpbm image reading facility (in libnetpbm) to be
+unreadable, which means the file is essentially truncated. In older Netpbm,
+the invalid sample value propagates to the output in a program such as
+\fBpamfixtrunc\fP. Thus, in older Netpbm a file with 100 rows and an invalid
+sample value in the 3rd row would pass through \fBpamfixtrunc\fP unchanged.
+But in Netpbm 10.66, \fBpamfix -truncate\fP with the same input would produce
+an output image with only 2 rows. While it is not possible in 10.66 to
+cause \fBpamfix\fP to generate an invalid Netpbm image, you can
+use \fB-clip\fP and \fB-changemaxval\fP options to avoid truncating the
+file in a case like this.
+.PP
+You should not make any new use of \fBpamfixtrunc\fP and if you modify an
+existing use, you should upgrade to \fBpamfixtrunc\fP. But note that if you
+write a program that might have to be used with very old
+Netpbm, \fBpamfixtrunc\fP is the only way to do that.
+.SH DOCUMENT SOURCE
+This manual page was generated by the Netpbm tool 'makeman' from HTML
+source. The master documentation is at
+.IP
+.B http://netpbm.sourceforge.net/doc/pamfixtrunc.html
+.PP \ No newline at end of file