| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
|
@victoryforce : Can you propose a release note entry for this? TIA. |
Sorry, something went wrong.
I'll think about the wording. So far I can't explain what exactly has been fixed in less than a few paragraphs. I need to briefly describe two problems, two types of not very correctly made files that we need to read both correctly:
|
Sorry, something went wrong.
|
Well, I suggest just writing in the release notes: Fixed an issue with reading TIFF files that (incorrectly) contain metadata specific to the raw files they were made from. There's probably no need to go into technical details of what happened, why it happened and how it was fixed... |
Sorry, something went wrong.
|
Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
If some program creates a TIFF file from a raw file which is based on a TIFF container, while preserving all Exif data, such a file cannot be distinguished from a raw file by its signature.
We want to support reading such TIFFs, and even those that, by mistake, contain metadata specific to raw files. The raw loader may in this case conclude that it is reading a raw file and produce wrong image. We can fix this by calling TIFF loader first. It checks the file extension and limits itself to processing only .tif/.tiff. So it's safe for nearly all raw files except those few disguised as TIFF files (actually they are a hybrid TIFF+Raw) with .tif extension. Obviously, for these tricky files, this function should not be called.
Resolves #19131.