Allow invalid encoding in EXIF UserComment field #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've come across multiple applications that fail to encode the EXIF
UserCommentfield correctly (i.e. omitting the 8 byte ID code completely). In that case, ExifTool decodes the data correctly (with a warning), butimagemetadoes not return any data for the field.This seems to especially affect Python applications making use of Pillow which relies on applications implementing their own encoding for this field. One could argue that the applications are at fault here, but given "When in doubt, Exiftool is right".. here we go.
The included sample file was generated with the following script which is exactly how affected applications are setting the
UserCommentfield: