HEIF format support (fixes #207) #215
Open
Conversation
This file contains hidden or 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
* image_utils:
enable HEIF by ad-hoc calling register_heif_opener()
add 'HEIF' to IMG_FORMATS
* Bump version to 0.3.3
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.
HEIF Support
This is attempt to support HEIF format, ubiquitous on Apple devices, using Pillow-Heif
See below why using libheif directly might be better option.
Licensing
This PR uses pi-heif - the light version of Pillow-Heif which only links against LGPL-licensed libheif, evading harsher GPL restrictions of the full version (see LICENSES_bundled.txt)
libheif is built and packaged for the wide range of platforms and leaves only small amount of platforms to follow LGPL-restrictive path.
However, Pillow-Heif, including pi-heif variant, provides wheels only for:
which is more narrow platform support than one of libheif.
Therefore, direct usage of libheif is advised, however it's out of scope of this PR.
If the author chooses to merge this PR, I suggest creating
LICENSES_bundled.txtfollowing Pillow-Heif approach which seems pretty neat.This PR fixes #207