Am 23.05.2016 um 23:59 schrieb Jehan Pagès:
On Mon, May 23, 2016 at 11:42 PM, Thorsten Stettin
Am 23.05.2016 um 23:07 schrieb C R:
Yes, if "save comment" is unchecked it saves fine.
I never touch the comment, so it's strange that there would be something
invalid in it.
Thanks for looking into this.
Maybe we should create a bug report?
You have precedence. You know, I'm just a packager. :-P
In German: Bitte nach Ihnen.
But seriously: From where you got this picture? Please explain the entire
workflow from your camera.
IMHO information like this is very important in order to handle issues like
Well from my point of view, it does not matter where the broken
metadata comes from, as long as it is not generated by GIMP (in which
case, yes it matters a lot! GIMP should not be able to create files
with broken metadata). Of course, if that's another Free Software
which created the metadata, it would be cool to report a bug there,
but that's still not an issue in GIMP.
The only issue I see in GIMP here is that broken metadata should not
be an export-stopper since it's a data bug which is easily catchable
and bypassed (by removing the wrong metadata).
Au contraire mon capitan!
To cut a long story short:
It's very important to know from where comes Gimp's lag regarding non
corfirming data regardless they come from.
gimp-developer-list mailing list
List address: firstname.lastname@example.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list