Possible regression: v0.7 doesn't support spanish accent marks (tilde) in paths

[Xandor19]

I've just installed Zeal v0.7 on Windows 11 and set a custom path for docsets (as I've always done) to some path in my D drive, then I downloaded my usual docsets. The path contained a spanish accent mark (tilde) in word "Bibliografía" and even when it let me set that path with no errors, it couln'd find the docsets and was having quite strange behaivor.

Note

I know it's common to have issues with non-english languages properties, but I'm opening this issue cause with v0.6.1 there was no problem with tildes on docsets path, so just in case something went broken.

Here a description:

At first I just installed Scala and the progress bar showed that it finished downloading and installing. However, in Zeal's sidebar Scala doesn't appeared, not any method/name when using the search. I went to the docsets path (the one with the accent mark) and Scala.docset folder existed and looked like a regular Zeal docset storage, so at least in that part is working with the path. When I opened the docsets menu in Zeal again, there wasn't any docset marked as installed and Scala was placed as available to install as it wasn't downloaded earlier.

I did the same test with other docsets (Ruby and Rails 7, Docker and VueJs). Though I already told the cause, here is some other behaivor to note: each of them supposedly finished downloading and installing and disapeared from the "Available" tab in docsets menu, but they never showed in the "Installed" tab nor on the main sidebar, just like Scala. When in the Available tab I used the searchbar to input one of the supposedly installed docsets, it showed it again with the option to install it and the same happens over and over. Also, the docsets folders for each of the listed languages/tools was correctly created.

The original path also had blankspaces in some folder names, so at first I thought that was the issue, but paths with such names work fine.

[trollixx]

Something else must be going on on in your case. I tried storing docsets in C:\Temp\Bibliografía and C:\Temp\Bibliografía\docsets and in both cases it worked as expected.

[trollixx]

Zeal doesn't really do direct file I/O, which would indicate a bug in Qt. I just updated CI to build with Qt 6.6.3. Can you try a CI build to see if the bug is still there?

[Xandor19]

Is v0.7.1-dev.20+cbd3208 the build to try? I just downloaded it from CI builds and has the same issue, but I'm not sure if it is the Qt 6.6.3 or Qt 5? I see both on the pipeline.

For me, this is the path that works:
D:\Documentos\Bibliografia y Documentacion\Lenguajes\Documentaciones

And the one that doesn't:
D:\Documentos\Bibliografía y Documentación\Lenguajes\Documentaciones

As you can see, the only difference are the accent marks

[trollixx]

I've been trying to reproduce this issue with all possible kinds of diacritics, and Zeal always works as expected. I am honestly not sure what else to try. The only possible difference I can think of is that your Windows system language is probably set to Spanish, while I use English version.

I'm not sure if it is the Qt 6.6.3 or Qt 5

CI builds only come with Qt 6. I recently updated the pipeline to bundle Qt 6.7.1. Maybe that fixes it?

[trollixx]

I made one more change in 5081898 that can be related. Let me know if it still doesn't work.

[Xandor19]

I just tested the CI build with the portable Zeal, but the issue persists. I tried to reproduce your env by setting Windows language to English, but it still has the same issue (Windows did kind of a messy language chance and I have spanglish allover the OS, so I-m not completely sure that it was a valid test)