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
We ideally use oxipng on all the images and sometimes even pngquant. It would be ideal to bake these tools into our container creation and have the release notes automatically run oxipng -D on the resulting images.
pngquant is great too, but it is lossy and would need to be run manually (or be a manual step that's checked). oxipng is not lossy (visually) and is safe to automate.
The text was updated successfully, but these errors were encountered:
@jelly mentioned that the official container (which we use) is Debian 10, which means we probably have to jump through hoops instead of just installing the command. So we might even need to curl it down from GitHub's releases.
(Otherwise, we'd have to install cargo and a rust compilation stack and then build/install oxipng.)
We may also want to include pngquant in the container, but not run it by default, as it is lossy and can change things.
We ideally use
oxipng
on all the images and sometimes evenpngquant
. It would be ideal to bake these tools into our container creation and have the release notes automatically runoxipng -D
on the resulting images.pngquant
is great too, but it is lossy and would need to be run manually (or be a manual step that's checked).oxipng
is not lossy (visually) and is safe to automate.The text was updated successfully, but these errors were encountered: