From looking at the nodes/values, I have come to the conclusion that Windows first looks if all characters in a string can be represented in

Hilko, forwarding this to the mailing list. Please post patches over there. Rich. ----- Forwarded message ----- Date: Wed, 21 Jul 2010 17:09:53 +0200 From: Hilko Bengen Subject: patch: non-ASCII characters in node names Hi Richard, I was a little bit surprised when a colleague claimed that key and value names in the registry could contain non-ASCII characters. I created keys and values with the following names: * "asdf" * "äöü" (common in German, can be represented in Windows-1252, Latin1, Latin9) * the Euro sign (can be represented in Windows-1252, Latin9) * the international currency symbol (can be represented in Windows-1252, Latin1) the Latin1 encoding. If that fails, UTF-16 is used. A bit in the "flags" field is used to indicate the character encoding. I have implemented and briefly tested read support for those names in the patch below. If that patch is acceptable, I'll do write support tomorrow. -Hilko ----- End forwarded message ----- -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top