Péter Szabó

@zvezdochiot, do you have some JPEG files to share for which *jpegoptim* (`jpegoptim -s --all-progressive`) generates very small output? I suspect that *jpegtran* of mozjpeg will generate smaller output, but...

@Adreitz, thank you for suggesting *jpegultrascan* and *pingo*. According to my quick measurements, *jpegultrascan* is about 1450 times slower than *jpegtran* of mozjpeg for a ~100 KiB JPEG input file,...

I was wondering which version of *jpegtran* to use. I've tried mozjpeg version 3.1 (2015-05-19) and version 4.1.1 (2022-09-15). The latter generated JPEG output files a few percent larger than...

I've created a source port of *jpegtran* of mozjpeg on https://github.com/pts/pts-mozjpegtran. The executable programs used by *pdfsizeopt* will be built from these sources, cross-compiled on Linux.

Please note that pdfsizeopt is not a repair tool or data rescue tool for broken PDFs. If the input PDF is broken, then pdfsizeopt may fail (or it may produce...

@rbrito: Could please file issues for the similar files of yours, where running *pdftk* before *pdfsizeopt* fixes it? Maybe those indicate real (so far undiscovered) bugs in pdfsizeopt.

These are valid questions about funding, and I don't have a full answer for it yet. As soon as I have more info, I'll post it to this issue. Unfortunately...

Thank you for reporting this, and thank you for providing all the details! I don't have time to implement this anytime soon, but I'll keep the issue open in case...

@Keks-Dose: Thank you for reporting the issue and suggesting veraPDF to verify PDF/A compliance. It would be easy to add the command-line flag `pdfsizeopt --write-pdfa=yes`, which would fix the compliance...

@Keks-Dose: Could you please upload your input PDF to this issue?