Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug : progressive jpeg #50

Open
abarre opened this issue Jan 6, 2017 · 1 comment
Open

bug : progressive jpeg #50

abarre opened this issue Jan 6, 2017 · 1 comment

Comments

@abarre
Copy link

abarre commented Jan 6, 2017

If image-recompress fails to find a better quality for a given image, the resulting image is not encoded in progressive mode even if the option has been set.

The expected behavior is to get a progressive image as a result with the same quality.

@andrews05
Copy link

andrews05 commented Jun 14, 2019

+1, most jpegs are still able to be optimized by mozjpeg even if they don't actually get recompressed. This would save me having to run images through jpegtran if jpeg-recompress doesn't act on them.
Perhaps this could be dependant on the --no-copy switch: If copying the file, optimize it, else if no-copy is set then still skip it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants