Open GoogleCodeExporter opened 9 years ago
Hi, thank you for the feature enhancement request.
I'll gauge the interest for a while and see if and when I should implement this
feature.
(The feature itself will probably involve a lot of effort, so I'll need to see
that there's a lot of demand for this feature.)
Original comment by coobird...@gmail.com
on 25 Aug 2013 at 6:14
I absolutely would love this feature.
I was using thumbnailator for a while and now need to show also all the exif
details in a image database software (for the thumbnails for improved speed). I
was hoping Thumbnailator can do this.
Original comment by adamsblu...@googlemail.com
on 13 Sep 2013 at 11:32
Note to self
------------
Check the Exif specification for fields which need to be updated upon editing
an image.
In particular, "PixelXDimension (0xA002)" and "PixelYDimension (0xA003)" needs
to be updated to the new dimensions.
Also to consider is what to do about "Orientation" -- according to the
specification, it says to set it to "1" (origin is at left-top), so it appears
that applying the rotation as indicated in the "Orientation" field seems to be
the correct thing to do.
(Which is the same thing that GIMP performed to a portrait-oriented image.)
Original comment by coobird...@gmail.com
on 23 Dec 2013 at 6:43
Thanks for a great library and it appears to be significantly faster than some
of the other Image Processing libraries on Java out there.
I would be careful about keeping EXIF data in all circumstances... for example,
we are looking to strip the GPS information from our photos for security
reasons. I think this should probably be an 'opt in' feature option.
Original comment by wtfi...@gmail.com
on 20 May 2014 at 12:09
Thank you for the feedback.
It would probably be more useful to keep the Exif metadata by default, as
suddenly removing metadata from an image would probably violate the principle
of least surprise.
That said, it probably would be a good idea to have a way to enable/disable
this feature, as there probably would be cases where removing the metadata
would be desirable.
When security is a concern (such as removing GPS data), one shouldn't depend on
a side-effect of the implementation of a library -- there should be deliberate
action to remove undesirable metadata.
This isn't just with Thumbnailator, but any case where security is a concern.
One shouldn't assume that the input data will always present itself in a
particular way -- in other words, practice defensive programming :)
Original comment by coobird...@gmail.com
on 19 Jun 2014 at 3:40
+1
+1
Original issue reported on code.google.com by
lifeis...@gmail.com
on 17 Aug 2013 at 6:49