-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
windows encoding support #4240
Comments
TODO list: doesn't seem to bad, actually:
|
note, part two of this probably requires using the windows API for long filenames, where that API is easily accessed by only using normalized, absolute filenames and prefixing them with |
the Microsoft team who write the .NET libraries also write a blog. 7 years ago, they explained that until the windows API is fixed to stop rejecting long paths that are supported the underlying NT API (but not by windows explorer), .NET won't be able to add support for long paths because it is just too broken (http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx) the official solution? yuck. I sort of knew this, but was also hoping we could leap-frog julia past 1990-era limitations (like it does for Unicode strings), so that this would never need to be true |
Jameson, I'm endlessly grateful that you're willing to tackle these things. Thank you. |
hrm, msys-git did it msysgit/git#122 (with a disclaimer that cmd / explorer / most windows programs won't be able to access the file, and a few API's like chdir don't support them). so maybe it is possible. |
except for limited usage cases, julia code on windows uses an incorrect encoding (including the clipboard code). solution: always use utf16 format. windows provides a function to make this straightforward. see
libuv/src/win/util.c
uv_utf16_to_utf8
anduv_utf8_to_utf16
for usage.(replaces #1919)
The text was updated successfully, but these errors were encountered: