From: "usa (Usaku NAKAMURA)" <usa@...>
Date: 2013-12-02T01:22:44+09:00
Subject: [ruby-core:58747] [Backport 200 - Backport #8943] Invalid encoding	for Windows Registry


Issue #8943 has been updated by usa (Usaku NAKAMURA).


Oh, sorry, the previous message was wrong.
Please forget about it.
----------------------------------------
Backport #8943: Invalid encoding for Windows Registry
https://bugs.ruby-lang.org/issues/8943#change-43317

Author: davispuh (D��vis Mos��ns)
Status: Open
Priority: Normal
Assignee: cruby-windows
Category: 
Target version: 


=begin
It's not possible to correctly read non-ASCII registry values. It's also not possible to write them with correct encoding.

to test import ((<test.reg|URL:https://gist.github.com/davispuh/6676385#file-test-reg>))

then ((<test3.rb|URL:https://gist.github.com/davispuh/6676377#file-test3-rb>))

Output on Ruby 2.0 (it's same for 1.9.3 except encoding is US-ASCII not UTF-8, but both are wrong)

 N:\Projects>ruby test3.rb
 UTF-8
 ���??���?���
 "\xE5??\xE4?\xE2"
 test

(it hangs here)

screenshot of registry after running it ((<URL:http://i.imm.io/1gFES.png>))


seems that whoever wrote Ruby code to interact with WinAPI had no idea about encodings/code pages Windows uses as there's loads of issues and they've been for years.
=end



-- 
http://bugs.ruby-lang.org/