Jeffrey Ratcliffe

I've almost finished a complete rewrite. It's probably going to be called scantpaper. Needless to say, the aim to be better in lots of ways, including error handling. I've just got to nail the last couple of bugs and write a few more tests.

gscan2pdf hangs on File Save

I've almost finished a complete rewrite. It's probably going to be called scantpaper. Needless to say, the aim to be better in lots of ways, including error handling. I've just got to nail the last couple of bug and write a few more tests.

Thanks for the report. Please start gscan2pdf from the command line with the --log=log option, reproduce the error, and post the log file.

This bug has now hit Debian sid. I'll have to skip the test in sid to avoid FTBFS. Your bug report is now seeing some attention.

300x300 without a unit should normally default to dots (pixels) per inch. And living in a land that uses SI units, I would be also happy for it to default to pixels per cm. But the new behaviour ends up being 72 ppi, which makes far less sense than anything else.

If you compare the output of identify, whereas in previous versions, the resolution metadata was still present in the image, plus the undefined units, in this new version, the resolution is completely missing. I'm calling this a bug in Imagemagick.

Thanks for the report. Debian testing still has 7.1.2-8, so I can't reproduce this. Please try the following with 7.1.2-9 and attach the jpg to the report: magick -units Undefined -density 300 xc:white test.jpg What does the following then return? identify -verbose test.jpg