>>1
Use GMail. If she already sent it to you, forward it to your GMail account.
Also, stick it in her pooper.
>>4
It does, with an ugly hack
>>7
Daily WTF
>>10
Windows 2000 and beyond have somewhat mediocre Unicode 4.0 support in the kernel (UTF-16) and applications. The Unicode support in the console subsystem is, however, awesome, only that nobody knows how to use it, and you can't use it properly using the crappy CRT. I had to ask Microsoft about this. Just call ReadConsoleW and WriteConsoleW yourself, and you'll have a true Unicode console. Basically, it works at Unicode and your locale at the same time: you can even write Unicode, then read non-Unicode from it (though you'll get ? for characters outside your legacy locale). (With this information, I wrote a Python Unicode driver that will enable full Unicode I/O with the Windows console, regardless of font, modifying sys.std*, so that raw_input, print, etc. work with unicode objects. I can share if you like.) What really sucks about Windows' Unicode support is that it still sticks to its shitty legazy locales - in the west Windows-1252 and CP850 and uses confusing and wrong names for them (ANSI and OEM). It would be much, much, much more useful if it came with an UTF-8 locale - the only locale, so that you could work in either UTF-8 or UTF-16 modes.
I'm quite content with UTF-8 support in Linux.