On Saturday 22 December 2007 4:13:09 pm Jeffrey Ratcliffe wrote: > On 22/12/2007, John Goerzen <[EMAIL PROTECTED]> wrote: > > the padwidth and pageheight give the physical size of the expected > > paper. -x and -y are constrained within the pagewidth and pageheight > > values. This scanner is sheetfed, so there is no concept of a physical > > scan bed that has a limited size. The valid range of -x and -y depend > > on --pagewidth and --pageheight. gscan2pdf seems to only be using -x > > and -y. > > > > If --pagewidth and --pageheight are listed and a paper size large than > > the default is selected, the relevant --pagewidth or --pageheight should > > be increased to match -x or -y. --pagewidth or --pageheight should > > never be decreased. Alternatively, you could always set --pagewidth or > > --pageheight to the maximum. As far as I can tell, that works. > > I have only seen the --pagewidth and --pageheight options for Fujitsu > scanners, and they are only meaningful for ADF operation. > > gscan2pdf lists only the paper sizes than can be scanner by the tlxy > options. The pagewidth and height options are completely ignored. > > What gscan2pdf should do is to check the page sizes against the > pagewidth/height options, if present and set them to the selected > paper size, ignoring the tlxy options (which would only be useful if > you wanted to scan an area of a page, based on a preview scan).
There may occasionally actually a need for it, but the Fujitsu scanner I have at least seems to be more intelligent than the scanimage options seem to suggest. That sounds like a reasonable first start. I'd be happy to test it out and see if I can make the thing jam :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
