Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XnViewMP fails to load or save QOI images with unicode filenames #8

Open
f2d opened this issue Jun 10, 2022 · 2 comments
Open

XnViewMP fails to load or save QOI images with unicode filenames #8

f2d opened this issue Jun 10, 2022 · 2 comments
Assignees

Comments

@f2d
Copy link

f2d commented Jun 10, 2022

Using both Save As and Batch Convert, no file is saved.
Batch convert log:

E:\第01話.bmp : loading
E:\第01話.bmp 1920x1080x24 : loaded
E:\第01話.qoi : not a picture

Input files: 1
Extracted pages: 1
New files: 1

Total Duration: 0 second(s)

No problem converting same files to JPG in XnViewMP.
No problem with Save As in XnViewMP if target filename is changed to non-unicode (e.g. latin alphanumeric only) in save dialog.
No problem with Paint.net, but saved file with unicode filename cannot be loaded in XnViewMP, showing this message box:

---------------------------
Error
---------------------------
File can't be loaded!
---------------------------
OK   
---------------------------
@pfusik pfusik self-assigned this Jun 10, 2022
@pfusik
Copy link
Owner

pfusik commented Jun 10, 2022

That's a limitation of XnViewMP on Windows. The Unicode characters are lost in XnViewMP. They are passed to the plugin as question marks. The built-in formats work because they don't go through the plugin interface.
Paint.NET opens the files itself, so its plugin doesn't deal with filenames at all.

Best I can do for XnViewMP is to ask its author to provide a new plugin interface that supports Unicode filenames. Let us know how important it is for you and whether you know other users needing that.

@f2d
Copy link
Author

f2d commented Jun 10, 2022

I personally can deal with it, using batch renaming and back, or keep encoding-neutral filename forms.
I don't know anyone else running into this issue.

On the other hand, unlike old XnView Classic, XnViewMP claims unicode filename support, so users probably expect that.
If its author thinks unicode support is important, your proposal should be good.

Also there are old 8.3 filenames that are used when I drag and drop such files into old XnView Classic and some other fallback cases.
But automatic creation and storing of such names may be disabled in some systems.
And they are probably not a good solution for creating new files when full original name may be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants