Bug #1192: encoding problem with tr() and hash keys 1.9.1

• Status: Closed
• Assignee: naruse (Yui NARUSE)
• Target version: 1.9.1
• ruby -v: ruby 1.9.1p0 (2009-01-30 revision 21907) [i686-linux]

[do1 (Do One)]

=begin
In utf-8 environment I do:

irb(main):121:0> h = {"a" => 1, "\u0101" => 2}
=> {"a"=>1, "ā"=>2}
irb(main):122:0> h.key? "a".tr("z", "\u0101")
=> false <--- wrong!
irb(main):123:0> h.key? "\u0101".tr("z", "\u0101")
=> true

So after I change utf-8 string without extended chars in it with tr(),
where second character set is having extended chars, new string is not
found in hash.

Both strings are same in Marshal encoding:

irb(main):124:0> Marshal.dump "a".tr("\u0101", "\u0101")
=> "\x04\bI"\x06a\x06:\rencoding"\nUTF-8"
irb(main):126:0> Marshal.dump "a"
=> "\x04\bI"\x06a\x06:\rencoding"\nUTF-8"
=end

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed
• % Done changed from 0 to 100

=begin
Applied in changeset r22525.
=end

[mame (Yusuke Endoh)]

• Category set to M17N
• Status changed from Closed to Open
• Assignee set to naruse (Yui NARUSE)

=begin
Hi,

The fix in r22525 seems to be incomplete:

$ ruby19 -ve 'p ["a".hash, "a".tr("a", "\u0101").tr("\u0101", "a").hash]'
ruby 1.9.2dev (2009-02-22 trunk 22527) [i686-linux]
[903321233, 903321232]

--
Yusuke ENDOH [e-mail]
=end

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

=begin
Applied in changeset r22547.
=end