When there are special characters, like spaces, inside the original image url, the end result on the FE is double encoded. That is because the url is once encoded by the CMS, and once by the responsive image resolver in the FE (most probably by the cloudinary SDK).
One option would be to just decode the URI before calling buildResponsiveImage()
When there are special characters, like spaces, inside the original image url, the end result on the FE is double encoded. That is because the url is once encoded by the CMS, and once by the responsive image resolver in the FE (most probably by the cloudinary SDK).
One option would be to just decode the URI before calling
buildResponsiveImage()