It is a locale-dependent glyph. What is probably meant is whatever would show up in a GUI application in a US locale. Note that this does not agree with what will show up in a console application on the same machine. Or in a machine that isn't in a US-based locale.

I am not on Windows so I cannot tell you what glyph that is. But the fastest way to find it out is to write that character somewhere and view it in a GUI application. You can do this with Perl by writing a script to write chr(160) into a file and then view it in notepad. (But NOT any DOS editor because that is in the console and so is a different locale.) You can do this by using Win32::Clipboard to paste chr(160) into the clipboard and then paste into virtually any Windows application.

Yes, this design sucks. Which is why Microsoft applications like to insert these locale-dependent characters everywhere. Because while it sucks even within their world, it causes incompatibility headaches that make everything else suck even worse...

Cheers,
Ben