I have bug
Posted: Mon May 13, 2024 1:49 am
XnView Classic: 2.51.1 - 64 bit
OS: Windows 10 64bit
candy clicker
How to Reproduce:
Create a folder containing UTF8 characters and place an image in it. (example: "C:\TEST\背\myimage.png")
Double-click on it in the Windows Explorer to open the image.
An error popup will appear. (see attachment)
Expected Behavior:
The image should open in XnView.
Workaround:
While XnView does not directly support UTF-8 characters in file paths, you can still access such paths within the application by using short paths.
The argument provided in "HKEY_CLASSES_ROOT\XnView.ext\shell\open\command" may contain UTF-8 characters.
An application has been developed to convert these arguments to short paths and forward them to XnView, which is available at the GitHub Repository.
Question:
Would it be feasible to support UTF-8 only for argument parsing in XnView and utilize GetShortPathNameW() to obtain the short path, similar to the provided workaround, or would this require significant effort? Thank you.
OS: Windows 10 64bit
candy clicker
How to Reproduce:
Create a folder containing UTF8 characters and place an image in it. (example: "C:\TEST\背\myimage.png")
Double-click on it in the Windows Explorer to open the image.
An error popup will appear. (see attachment)
Expected Behavior:
The image should open in XnView.
Workaround:
While XnView does not directly support UTF-8 characters in file paths, you can still access such paths within the application by using short paths.
The argument provided in "HKEY_CLASSES_ROOT\XnView.ext\shell\open\command" may contain UTF-8 characters.
An application has been developed to convert these arguments to short paths and forward them to XnView, which is available at the GitHub Repository.
Question:
Would it be feasible to support UTF-8 only for argument parsing in XnView and utilize GetShortPathNameW() to obtain the short path, similar to the provided workaround, or would this require significant effort? Thank you.