"FromTheRafters" wrote:

> I've read somewhere that one needs to edit the registry so as to allow
> creation of filenames with such characters.

Only if you're using the keyboard. I wrote a test program using the
CreateFileW function. The ending 'W' means a unicode string is
required for the filename so I could be sure I was using the correct
character.

> If so, I'm wondering if the
> same disallowance applies to such files extracted from archive files. I
> have only ever seen these where the name actually comes from within an
> archive file.

No, it doesn't. Any program can create a file with a unicode name
irrespective of registry settings. After all, the native Windows API
uses unicode exclusively. My test program gave the expected visual
result on XP but not on Win2k (in neither case was the registry value
set), so the older Explorer GUI did not recognise the RLO character.
However, my W2k is so heavily tweaked that it's possible something
else is preventing it from working!