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

File.join generates corrupted Windows-31J String on Windows #2400

Closed
headius opened this issue Dec 31, 2014 · 5 comments
Closed

File.join generates corrupted Windows-31J String on Windows #2400

headius opened this issue Dec 31, 2014 · 5 comments

Comments

@headius
Copy link
Member

headius commented Dec 31, 2014

From http://jira.codehaus.org/browse/JRUBY-7131

The original bug report did not have a good reproduction, so we'll need a Windows machine and we'll need to figure out how to type Unicode into a terminal to reproduce this.

I'm going to pessimistically guess it's still broken, but for now this bug is a placeholder until we can confirm that.

@headius
Copy link
Member Author

headius commented Dec 31, 2014

cc @nahi, who filed the original report.

@ahorek
Copy link
Contributor

ahorek commented Jan 1, 2015

IRB in Java window displays correct characters, but original windows console is ascii only
???/??? instead of 日本語/日本語

@headius
Copy link
Member Author

headius commented Feb 23, 2015

My environment seems screwy and won't display multibyte chars in Command Prompt, but it does appear to join the filenames correctly. Can someone reproduce the File.join problem and show me:

  • a git repo with a reproduction file
  • a session log showing the failure OR a short video showing the failure

@enebo enebo added this to the Invalid or Duplicate milestone May 16, 2017
@enebo
Copy link
Member

enebo commented May 16, 2017

Multiple years with no repro. Closing. fwiw continued work on appveyor test runs are straightening out some of these issues over time but without a repro I don't know if this is one or not.

@enebo enebo closed this as completed May 16, 2017
@ahorek
Copy link
Contributor

ahorek commented May 16, 2017

@enbo I think it was already fixed in 9000 by #3871 - it shoud be closed, thanks

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

No branches or pull requests

3 participants