* According to the Metadataworkinggroup's Guidelines for handling ima… #55
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
…ge metadata type ASCII should be represented as UTF-8 (pages 32 and 33), this forces UTF-8 decoding of this TIFF field.
|
Any update on this pull request? |
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.
Small fix to be compliant with the Metadata working group guidelines. For them, which includes Adobe, TIFF data of type ASCII should be written as UTF-8 (code is ok) and possibly read as UTF-8 (my patch) (see pages 32 and 33 of the guideline 2.0 document). Therefore i just changed the encoding format for reading, hoping i did not miss anything. Possibly can you add it to your master?