Optionally force UTF-8 encoding for IPTC records #477
Merged
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
…stieler/commons-imaging into feature/force-UTF-8_encoding_for_IPTC
|
It looks like you did not follow the PR template, specfically:
|
|
@garydgregory You're right, unfortunately I forgot to remove trailing whitespace in one line, now mvn completes successfully! |
|
@thstieler |
asfgit
pushed a commit
that referenced
this pull request
Jan 21, 2025
|
@garydgregory Thank you very much, that's great :-)! |
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.
This pull request adds the option to enforce UTF-8 encoding for writing IPTC records to jpeg files.
This can improve the reliability for correct parsing of IPTC records written by commons-imaging, because some libraries/applications use UTF-8 as default charset when reading IPTC records.