Bug #8822

Incorrect encoding for ENV in Windows

Added by Dāvis Mosāns 8 months ago. Updated 8 months ago.

[ruby-core:56822]
Status:Assigned
Priority:Normal
Assignee:cruby-windows
Category:-
Target version:-
ruby -v:ruby 2.0.0p247 (2013-06-27) [x64-mingw32] Backport:1.9.3: UNKNOWN, 2.0.0: UNKNOWN

Description

=begin
When reading ENV and if it contains non-ASCII - string won't have correct encoding.
In Ruby 2.0 we can force it to UTF8 (it doesn't matter what's windows encoding nor consoles) and it will be correct, but in Ruby 1.9 there's no way to correctly read it.

Writing non-ASCII string to ENV is not possible at all neither of versions.

Also Ruby1.9 fails to read ENV with name witch contains non-ASCII

Here's (()) (basically set environment variable outside of ruby and in ruby print it out)

Output on (()) and on (())

Seems it wasn't properly fixed in #5570
=end

History

#1 Updated by Dāvis Mosāns 8 months ago

In Ruby 2.0 when assigning to ENV, seems it double encodes it.
But in Ruby 1.9 it's interesting that after assigning - it shows console's encoding, but that shouldn't be needed at all...

#2 Updated by Zachary Scott 8 months ago

  • Status changed from Open to Assigned
  • Assignee set to cruby-windows

#3 Updated by Usaku NAKAMURA 8 months ago

Since Ruby 1.8 assumes the encoding of ENV is locale (or -K specified encoding),
Ruby 1.9 also treats it as locale for compatibility.
It was intentional decision, not bug.
We were able to break compatibility at Ruby 2.0, but the work was not done.

BTW, to be sure, the present behavior of Ruby 2.0 is wrong.
It should be corrected.

Also available in: Atom PDF