Progressive JPEG defaults to baseline after image processing
@thelightstain wrote: Dear all, I suppose this is coming from gift so I opened an issue there. Did anybody else notice this behavior? Read full topic
View ArticleProgressive JPEG defaults to baseline after image processing
@zabatonni wrote: Same here. I always make sure that i use progressive jpegs on my site and this is a big disappointment. Read full topic
View ArticleProgressive JPEG defaults to baseline after image processing
@thelightstain wrote: Quoting from the issue’s closing message: The gift package does not provide any image decoding/encoding functionality. I believe hugo uses the standard image/jpeg package to...
View ArticleClik here to view.
Progressive JPEG defaults to baseline after image processing
@bep wrote: thelightstain: Now I am confused. Is hugo using the standard package? Or gift? Both. But since both Hugo and Gift is limited by that constraint**, there currently is no (known to me)...
View ArticleProgressive JPEG defaults to baseline after image processing
@thelightstain wrote: Thanks for clearing things up. What I found in go is guetzli and I don’t believe it handles progressive encoding. Mozjpeg would be a nice candidate, but still in C (++). I don’t...
View ArticleClik here to view.
Progressive JPEG defaults to baseline after image processing
@bep wrote: thelightstain: I assume site generation speed No, speed is not a concern, it is plenty fast enough. It’s about maintainance/integration/security. We currently only have LibSASS as an C++...
View ArticleProgressive JPEG defaults to baseline after image processing
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed. Read full topic
View Article
