You need to log in before you can comment on or make changes to this bug.
Using fax2tiff from libtiff version 4.0.9 (or compiled from current master, 981e43ec) I observe the following behavior: $ fax2tiff -4 -P -X 1728 -B -M -o out.tif in.raw in.raw: Empty input file. And out.tif is a 267-byte file which appears to be corrupt. Using fax2tiff from 4.0.8 or earlier, the command produces no output and a valid 18,977-byte TIFF file. I have bisected the regression to 1cb6c46b9db2c589f76bee6d760f96fa6bc0c835 (the first bad commit). The test file I used contains name and phone number information for a client, so I would prefer not to post it publicly. Let me know if it would be useful. Thanks, Kevin
I think this is related to https://gitlab.com/libtiff/libtiff/merge_requests/55 http://bugzilla.maptools.org/show_bug.cgi?id=2799
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets, such as this one, have been migrated to the libtiff GitLab instance at https://gitlab.com/libtiff/libtiff/issues . The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is the initial Bugzilla issue number.
