On 5/16/19 12:03 AM, Paul Jewell via gimp-developer-list wrote:
Hi All, I am wondering about a curious event I am seeing related to exporting PNG images from Gimp either through the usual interface, or via a script like so: pdb.file_png_save2(gimp.image_list()[0], gimp.image_list()[0].layers[0], '/tmp/test1.png', '/tmp/test1.png', 0, 0, 0, 0, 0, 0, 0, 0, 0) pdb.file_png_save2(gimp.image_list()[0], gimp.image_list()[0].layers[0], '/tmp/test2.png', '/tmp/test2.png', 0, 0, 0, 0, 0, 0, 0, 0, 0) It seems that exporting these two pngs, some different data is written because they have a different sha1sum. (I would guess timestamp, but I disabled this with the plugin option as shown) This weirdness does not seem to happen with other file formats like webp, raw, etc. Is there any way to disable the writing of this extra data?
Can't reproduce. Saving the same PNG twice gives two files with identical hashes even when saving: * background color * gamma * layer offset * resolution * comment the comment _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
