View Single Post
Old 02-13-2015, 05:19 PM   #983
willus
Fuzzball, the purple cat
willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.
 
willus's Avatar
 
Posts: 1,303
Karma: 11087488
Join Date: Jun 2011
Location: California
Device: iPad
Quote:
Originally Posted by dhdurgee View Post
Does the -cbox option work in addition to the -m option? I am already using PDFtk to assemble a single PDF from the individual articles, so I would not have too much problem with determinine which pages have the extra header information that needs to be removed. Looking at the output I assume I should be somewhat conservative on this as you appear to be detecting white space margins for automatic cropping.

Dave
Yes, -cbox works in addition to -m. They actually work a little differently. The -m option acts only on the entire source page (not the cropped area) and causes the source page to be treated as if all those margin areas become white (that's what actually happens to the internal bitmap). So it doesn't affect the size of the processed source page. The -cbox option causes just that cropped area to be processed, and the source page becomes a smaller size. It's a subtle difference but can affect how things are processed. To disable auto-cropping of white space, you can use -t-.
willus is offline   Reply With Quote