Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot open webp files #78

Closed
gregzaal opened this issue Aug 29, 2022 · 5 comments · Fixed by #93
Closed

Cannot open webp files #78

gregzaal opened this issue Aug 29, 2022 · 5 comments · Fixed by #93
Labels
duplicate This issue or pull request already exists format support Related to add/remove/change of a specific format support.

Comments

@gregzaal
Copy link

I believe webp is meant to be supported now, but I still get "The file xyz.webp could not be read!" errors when opening any webp file.

Example file:
thumbnail.zip

@sylikc sylikc added the duplicate This issue or pull request already exists label Aug 29, 2022
@sylikc
Copy link
Owner

sylikc commented Aug 29, 2022

@gregzaal please try #4 (comment)

@gregzaal
Copy link
Author

Do you mean adding webp to the config FilesProcessedByWIC=*.wdp;*.hdp;*.jxr;*.webp ?

This doesn't seem to help.

@OCD-Man
Copy link

OCD-Man commented Sep 24, 2022

I know there is no problem opening webp files.

So when I got a blank window when opening the file you attached in your post in JPEGView, the first thing I did was open it in a hex editor to look at the text portion of the hex editor window to see if the header info showed it was a webp file or something else.

The header clearly says it is a png file.

So just rename your file as PNG and it will open in JPEGView.

Normally if you rename a file to a different extension, the program just detects what kind of file it is from the info in the file such as the header, and not from the file extension which is just to tell the operating system which program should open the file (which can be seen by changing this file extension to .jpg). But webp has it's own dll file which makes me think that webp support is more of an addon to the program which I guess is why opening webp files is programmed differently. Still JPEGView should instead read the header of the webp file to determine if it is webp before processing it as webp, even if initially JPEGView attempts to open it as webp based on the file extension.

But that should be put in a to do list, and as for this issue, I guess it can be closed.

@LaurentGrenet
Copy link

LaurentGrenet commented Oct 4, 2022

Hello all, (and in particular hello @sylikc )

what is VERY surprising with Webp management by JPEGView is that if we have a look on file provided by @gregzaal in its initial message just above, and about which one @OCD-Man says it's actually a png file (according what we can see as its actual content) is the fact that JPEGView is able to open it in any case except if its extension is .webp !
If you rename the file as [anything].jpeg, [anything].png, [anything].bmp, or even [anything].[anyextension] except webp, or even no extension at all, JPEGView opens it succesfully ! Only if it's named [anything].webp that JPEGView fails opening it !
Strange, no ?

And on the other hand, all files "natively Webp" (ie. that are proposed to be stored with a .webp extension when right-click + save image as", eg. the one proposed in https://en.wikipedia.org/wiki/WebP) that I have downloaded from the WEB have all been correctly opened by JPEGView... even when named *.webp (and also if renamed *.png, *.bmp, *.jpg, *.[whateveryouwant] )

VERY strange, no ?

@sylikc
Copy link
Owner

sylikc commented Dec 17, 2022

Closed by #93

@sylikc sylikc closed this as completed Dec 17, 2022
@sylikc sylikc added the format support Related to add/remove/change of a specific format support. label Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists format support Related to add/remove/change of a specific format support.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants