pdfbox-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tilman Hausherr <THaush...@t-online.de>
Subject Re: Large memory footprint and long processing time for one page PDF
Date Sun, 12 Nov 2017 11:43:21 GMT
Yes, I see it now, PrintPDF uses PDFPageable, which creates a 
PDFPrintable, which uses Scaling.ACTUAL_SIZE, and doesn't have a 
parameter for that. Maybe that should be expanded with an extra 
parameter and also allowed as a parameter in the command line utility too.


Am 09.11.2017 um 11:31 schrieb Thorsten Schöning:
>>> BTW 2, it seems to me that the command line app is printing using
>>> Scaling.ACTUAL_SIZE while in your bug SHRINK_TO_SIZE is preferred.
> [...]
>> Sorry I don't understand.
> There's the following sentence in one of the comments in your provided
> bug report:
>> ACTUAL_SIZE usually clips unless you have a printer that has a
>> printable area equal to the full page size of the PDF (i.e. to print
>> A4 you'll need an A4+ printer). So yes, SHRINK_TO_SIZE is usually
>> what you want.
> So I would have expected that printing at the command line would to
> default to SHRINK_TO_SIZE as well. But looking at the code I have the
> feeling that this is not the case.
> Just wanted to mention it, might not be a problem and my print results
> are perfectly fine, not missing any content or such.
> Mit freundlichen Grüßen,
> Thorsten Schöning

To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org

View raw message