Interesting. Was it actually UTF-8? Or was it UCS2? The thread in question is discussing UTF-8, as opposed to local codepages, but it's possible they're getting

Interesting. Was it actually UTF-8? Or was it UCS2? The thread in question is discussing UTF-8, as opposed to local codepages, but it's possible they're getting confused by the fact that it requires conversion to UTF-8 to pass the strings around. I'm guessing Windows is taking those UTF-8 strings and transparently converting them to UCS2 though, since Windows internals have stuck to UCS2 for so long.