You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My 2¢:
The executable is already quite large. I'd prefer oxipng to remain very focussed as a command line tool, so suggest conversion is done with other utility programs.
I'd say support for optimizing other image formats is clearly out of scope.
Support for reading other image formats and converting them to optimized PNGs could be more appropriate (see #480 for related discussion), but given the PNG format lossless nature and the ability to tune its filter selecting and Deflate encoding parameters for speed over compression size, it is practical to use alternativeencoders for faster-than-usual PNG encoding, reducing the need for OxiPNG to support more input formats from a user perspective. Furthermore, Rust library and application developers can already use the internal raw image API to decode images from any format they prefer. Therefore, I agree with @ace-dent's perspective that it seems more sensible to keep OxiPNG focused on handling PNGs.
Is support of other formats, such as tiff, jpeg, webp desired/planed or out of scope?
The text was updated successfully, but these errors were encountered: