Subject: 2.51.2: File cannot be opened with strange characters in the path
XnView: Classic 2.51.2 - 32 bit
OS: Windows 64bit
Now that google albums archive are going to be deleted (https://support.google.com/picasa/answer/7008270?hl=en) many users will download their backups. They are using a strange character (black dot) in the path:
Example: 2019-12-17-Hangout_ slow dawn ● [username]
Effect: You cannot open the picture because a warning is displayed and the picture is not opened.
To reproduce:
1. Try to open a picture placed in a folder which path contains "●"
2. Any other app will open the file, but xnview won't
Actual behaviour (bug): A warning is displayed, the picture is never opened. See attached "warning"
Expected behaviour: The file should be opened, regardless of the path
2.51.2: File cannot be opened with strange characters in the path [Solved]
Moderators: XnTriq, helmut, xnview
-
- Posts: 3
- Joined: Thu Jul 20, 2023 12:57 pm
2.51.2: File cannot be opened with strange characters in the path [Solved]
You do not have the required permissions to view the files attached to this post.
-
- XnThusiast
- Posts: 4180
- Joined: Sun Apr 29, 2012 9:45 am
- Location: Cheltenham, U.K.
Re: 2.51.2: File cannot be opened with strange characters in the path
I don't see a "●" in the in the screenshot?
-
- Posts: 3
- Joined: Thu Jul 20, 2023 12:57 pm
Re: 2.51.2: File cannot be opened with strange characters in the path
You are right, the "●" is rendered as "?" in the screenshot, but the character is there.
I assume that the encoding that is used to save the string path is not 100% right.
I assume that the encoding that is used to save the string path is not 100% right.
-
- XnThusiast
- Posts: 4180
- Joined: Sun Apr 29, 2012 9:45 am
- Location: Cheltenham, U.K.
Re: 2.51.2: File cannot be opened with strange characters in the path
XnView Classic doesn't have full Unicode support, you might try XnView MP which does...
-
- Posts: 3
- Joined: Thu Jul 20, 2023 12:57 pm
Re: 2.51.2: File cannot be opened with strange characters in the path
OK Thanks for the workaround! I've installed the MP version and it works as expected. Thanks!