SUMMARY When I try to open a file (.cbz) containing .webp, a message pops up that the file cannot be opened. STEPS TO REPRODUCE 1. create any .webp file 2. zip the file with 7z 3. change the file extension from .zip to .cbz 4. try to open the file OBSERVED RESULT message: "file cannot be opened" EXPECTED RESULT the file opens without problems as if it were if it contained .jpg or .png SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Okular cant open .webp files either (if you try drag and drop). However the site (https://okular.kde.org/) says it should be supported. Okular can open an .tiff file (drag and drop), but if you zip this file and rename it to .cbz and try to open it, an error will appear.
Please in the future do not report two different problems in the same issue, makes tracking them unnecessarily hard. Also, can you please attach that cbz that you say we fail to open?
Created attachment 158178 [details] test .cbz file with one .webp image
(In reply to Albert Astals Cid from comment #1) > Please in the future do not report two different problems in the same issue, > makes tracking them unnecessarily hard. > > Also, can you please attach that cbz that you say we fail to open? I apologize for two problems in one issue. The main problem is that .cbz files containing .webp image/s cannot be opened. (everything else is not so important) I've added an example of a file that won't open.
Created attachment 158179 [details] error popup when trying to open file
(In reply to flampingog from comment #2) > Created attachment 158178 [details] > test .cbz file with one .webp image My okular opens it on linux. Do you have in your okular install the windows equivalent of /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqwebp.so ? it could be called plugins\imageformats\qwebp.dll
Yes that was the problem and is getting fixed soon-ish
(In reply to Albert Astals Cid from comment #6) > Yes that was the problem and is getting fixed soon-ish Glad to hear it. Apparently "okular-23.04.0-1367-windows-cl-msvc2019-x86_64" already contains a fix and everything works as it should. Thanks! Problem solved.