On 10/04/2022 20:36, martin f krafft wrote:
Regarding the following, written by "Jeff" on 2022-04-10 at 12:52 Uhr +0000:

    Can't this be achieved with a user defined tool?

Sure thing, for instance:

|convert -size 2480x3508 -depth 300x300 -transparent white in.pdf out.pdf |

I see four problems with this though:

 1.

    This operation would be a lot faster on the PNM files, rather than
    first writing the PDF, and then basically accessing the PDF bitmaps
    page-wise for this operation;

The user-defined tools operate on the source images, not the resulting PDF. I think you might be mixing them up with the post-save hook, which does operate on the PDF.

 3.

    A user-defined tool does not have access to the resolution to be
    used, unlike gscan2pdf. I can calculate the dimensions, but only if
    I have the resolution;

The user-defined tools currently offer 3 variables, %i for input filename, %o for output filename, and %r for resolution.

I understand your point, but the argument can be made about all of the post-processing tools built-in, and the question becomes which one of those are so commonly used that they should be built-in. I never use unsharp mask, negation, brigthness/contrast, or even OCR, but they are built-in.

Absolutely. I was not suggesting it shouldn't be added, only provide a workaround until I found time to do so.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to