Sean Kelly Wrote:

> > The wide functions are supposed to be utf16, and those should work.
> 
> Surprisingly, they don't appear to work properly. The locale used for
> the UTF16 to multibyte conversion is the currently set locale, and that
> prints garbage on my Windows install.

For me it just didn't print non-ASCII characters. May be it supports just a 
small subset of unicode?

Reply via email to