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
I'm trying to have a pipeline that processes PNGs so when they're saved again, if the image data doesn't change, they don't get flagged as a new file by Git (for example).
I was going to use oxipng for this, but it seems it changes the order of chunks for some reason.
I created an image of a single pixel and ran oxipng as oxipng -o 4 -i 0 --strip All pixel.png. The first time I got this result:
Hi,
I'm trying to have a pipeline that processes PNGs so when they're saved again, if the image data doesn't change, they don't get flagged as a new file by Git (for example).
I was going to use
oxipng
for this, but it seems it changes the order of chunks for some reason.I created an image of a single pixel and ran
oxipng
asoxipng -o 4 -i 0 --strip All pixel.png
. The first time I got this result:And the second time (against the already optimized png):
As you can see, the
pHYs
chunk is moving around, and if I run a third time, other blocks will randomly move.Will it be possible for metadata chunks to be always in the same order, either all the time or with some parameter?
Thanks in advance.
The text was updated successfully, but these errors were encountered: