#8 auto detect blank pages


Here is a revised patch to automatically select blank (or dark) pages. It uses Image::Magick::Statistics() to determine the mean and standard deviation for each page. This version of the patch will analyze those pages which have changed since the last analysis was performed. A page is considered to have changed if any of the following transformations have been performed: rotate, threshold, negate, unsharp, crop.

The code has some hooks for future work regarding automatically selecting pages whose OCR text needs to be updated. These functions are currently not accessible to the user.

This patch is meant to be applied to the HEAD (tip) of the repository.


  • Jeffrey Ratcliffe

    Now the libsane-perl frontend is more or less stable, and I am waiting for a new version of a dependency of forks to be uploaded, I've looked a bit harder at your patch.

    I've uploaded a slightly modified version of your patch as it applies to HEAD

    Is a dark page just the black version of a blank page? Is there any point in distinguishing between the two in the GUI? What about if Select Blank Pages selects both blank and dark pages?

  • Roy Shahbazian

    Roy Shahbazian - 2009-04-03

    Looks good. Thanks for adding the settings to the menus.

    I personally used the blank page selection to delete pages that were blank on paper (typically the back of a one-sided print). I used the dark page selection to find pages that needed to be re-scanned. This generally happened with text printed on colored paper.

    On the other hand, I see the value of simplifying the menu. Is it possible to get GTK2 to do a nested menu for some of the Select options (similar to the Firefox "View -> Zoom" menu items)?

  • Jeffrey Ratcliffe

    I have committed the patch to HEAD with your suggestion of the nested menus, plus some SpinButtons in preferences to change the thresholds

  • Jeffrey Ratcliffe

    • status: open --> closed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks