Handle removing orientation from alternate types of EXIF data #5584
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #5580
When an image is copied in
exif_transpose(), theinfodictionary is copied. However, this is not the only way to specify orientation - it might also be specified throughtag_v2or the user may have set it onImage.Exif()directly, which are not copied to a new image. So an error was raised ifexif_transpose()tried to remove the orientation if the orientation wasn't there.This PR allows for the orientation to be already absent after copying, and also removes the orientation from the "Raw profile type exif" the "XML:com.adobe.xmp" info keys if they are used instead.