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 was able to open any file on Windows in 0.27.6, such as hello_🌎.jpg and in 0.28.0 all of the methods for UTF-16 paths are gone, removed in commit 7933ff4. This change makes Exiv2 usable on Windows only for Win-1252 characters, which is what fopen operates on. In order to open files with UTF-16 paths and names, one needs to use _wfopen. Can this change be reverted by any chance? If not, is there any replacement functionality planned? It is a pretty significant regression.
Thank you
The text was updated successfully, but these errors were encountered:
Discussed in #2795
I was able to open any file on Windows in 0.27.6, such as hello_🌎.jpg and in 0.28.0 all of the methods for UTF-16 paths are gone, removed in commit 7933ff4. This change makes Exiv2 usable on Windows only for Win-1252 characters, which is what
fopen
operates on. In order to open files with UTF-16 paths and names, one needs to use_wfopen
. Can this change be reverted by any chance? If not, is there any replacement functionality planned? It is a pretty significant regression.Thank you
The text was updated successfully, but these errors were encountered: