-
Notifications
You must be signed in to change notification settings - Fork 114
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
OpenInExplorer doesn't work with paths with non english characters. #548
Comments
If you run EDIT: If it does give an error, can you figure out a way (probably some combination of quoting), to protect the string (or protect windows from the string)? |
Hey @wpferguson I thought I did mention that in my original issue, sorry! That's what I meant when I said the "commands it logs are OK" Yes, first thing I did was try them in a terminal and from the "Run" utility and it works perfectly! The logs show that the commands are perfectly fine, but fail to be executed by
That's the first thing I tried wrapping the file path in quotes:
It made no difference :( |
Can you try Thanks |
Ok, appologies for so many comments. This works:
It creates a BAT file like this (suggested by this stack overflow answer):
It even works with multiple selected files. Would that be acceptable in a PR? The 65001 encoding is apparently just UTF-8? Not sure why, but this works. |
Does the solution still work with normal strings? Yes, a PR would be welcome 😄, though a better place to apply it would probably be in lib/dutils/system.lua so it fixes calls from all scripts and not just OpenInExplorer. |
Ok, made the changes in system.lua. I've tried multiple actions that use that command (update lua scripts, run external editors, open in explorer) and so far they all work as expected. For normal paths and paths with accentuated characters. I'll open a PR and maybe you guys can test it on your end. Thank you! |
Hello!
Currently using DT 5.0 in Windows 11 with Lua API 9.4.0.
I read another issue that reported something similar and the reply was that #437 would fix the issue but apparently not for this script.
It works ok with paths with only english characters. I've modified the script to log the paths and commands it's tryint to open and they are Ok, not sure where it fails (it says LUA result from windows command was 1).
Here's the log with some example paths I tried. Notice the ones with accentuated characters fail (with the word "montaña")
The text was updated successfully, but these errors were encountered: