You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use cwebp to convert some files into webp.
when trying to convert files from a directory that has spaces in its name or to a destination directory that has spaces in its name, cwebp does not convert the files, for some reason.
furthermore, when trying to convert a file that has a space in its name and is inside a folder that also has a space in its name, a file is created next to the destination folder, which takes the first word in that folder's name as its name. the file does not have an extension but seems to be webp, as it can be opened in a photo viewer.
am I the only one who's having this problem?
The text was updated successfully, but these errors were encountered:
ranshaa05
changed the title
cwebp: input_image or output_image can not have any spaces in them.
cwebp: input_image and output_image can not have any spaces in them.
Oct 22, 2021
Since below what this is doing is passing the params to dwebp.exe (in my case, in windows), then input and output params need to be quoted
I just added quotes to my source and destination, and it's working fine, but it seems to also write whatever is inside the "logging" parameter to the end of the final filename, so I just wrote logging="".
I'm trying to use cwebp to convert some files into webp.
when trying to convert files from a directory that has spaces in its name or to a destination directory that has spaces in its name, cwebp does not convert the files, for some reason.
furthermore, when trying to convert a file that has a space in its name and is inside a folder that also has a space in its name, a file is created next to the destination folder, which takes the first word in that folder's name as its name. the file does not have an extension but seems to be webp, as it can be opened in a photo viewer.
am I the only one who's having this problem?
The text was updated successfully, but these errors were encountered: