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

Windows encodings fixes #4159

Merged
merged 2 commits into from
Aug 6, 2014
Merged

Windows encodings fixes #4159

merged 2 commits into from
Aug 6, 2014

Conversation

vassilevsky
Copy link
Contributor

These small fixes allow Vagrant to run under non-ASCII Windows usernames.
As it turns out, Windows uses different encodings in different parts of itself and none of them are UTF-8 :)
After these patches, vagrant init completes successfully.

Dir.entries have filesystem encoding (ANSI in Windows).
Path fragments have terminal encoding (DOS).
@sneal
Copy link
Contributor

sneal commented Jul 8, 2014

Excellent! I'm working on better non-ASCII support for Windows guests, so I'm glad to see this. Does vagrant up work or only vagrant init?

@vassilevsky
Copy link
Contributor Author

vagrant box add crashes. But that is because of ChildProcess and MRI (!) shortcomings. I've opened an issue on that at ChildProcess repo:
enkessler/childprocess#81

@sneal
Copy link
Contributor

sneal commented Jul 17, 2014

Does this fix #3937 ?

@vassilevsky
Copy link
Contributor Author

Unfortunately, it does not. I am seeing that error too. Done some debugging but no solution yet. Some really weird things in ENV there.

@mitchellh
Copy link
Contributor

This is a good start. Thanks so much. Encodings on Windows are a nightmare.

mitchellh added a commit that referenced this pull request Aug 6, 2014
@mitchellh mitchellh merged commit 9748b5d into hashicorp:master Aug 6, 2014
@vassilevsky vassilevsky deleted the windows-encodings branch August 7, 2014 06:34
@luisrudge
Copy link

hasn't fixed

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants