I disagree. UTF-8 is not a locale, it's a character translation mapping. Although abusing the locale system for "easy" Unicode support is doable, I have to commend Microsoft for not taking the easy route. Proper Unicode support requires more from the application than just treating it like ASCII text. Buffer overflows etc blah blah.
Then again, like I just replied to another thread, it would be the easiest and fastest way to add Unicode support to mIRC, by just converting between UTF-8 and UCS-2 (which is used by Windows), and treating it like any other text, just using the Unicode text input and rendering functions instead. :-)
But the point is, the Unicode support in Windows is good enough. UTF-8 <-> UCS-2 conversion is not exactly difficult to add. I think I could do it in my sleep with both hands tied behind my back.
