Corrected documentation of TIFF saving arguments #4015
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
|
Thanks. |
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 #4013, which reports that the
dpiargument in TIFF saving doesn't support '(numerator, denominator)' values as the documentation claims.The documentation was added in #369
Looking at code, this functionality was removed in #1419, where 'A tuple of more than one rational tuples' 'flatten to floats' was removed, along with
ifd[X_RESOLUTION] = _cvt_res(dpi[0])being changed toifd[X_RESOLUTION] = dpi[0].While updating this, I also note that we round the dpi - that was added in #3709
Also removed in #1419 was the use of "inch", "cm" and "centimeter" for
resolution_unit, so I'm fixing that as well.