Comments by japcrword (Top 3 by date)

Well, currently I don't know. I prefer to think that it is not a bug. I simply decided to use cout + utf8 instead of wcout on linux.

Thank you very much for the advice and for the article (it is certainly useful for me as I'm not an expert in Unicode). I followed your advice. The output was:

terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
Aborted

From which I concluded that the needed locale wasn't installed. For the list of available locales I ran 'locale -a' (just to make sure the be_BY.utf8 locale wasn't present - and it wasn't). I have installed the locale with 'locale-gen be_BY.utf8'. Now the program doesn't throw an exception but still wcout doesn't work. The results of calling setlocale and wcout.imbue are (as far as I can judge based on output) identical. I did check source file encoding. It's utf8. I've verified my code under MS Windows 7 + MS Visual C 2008 (though I used different locale string). Both cout and wcout worked properly. But under Linux / G++ the wcout behaviour differs. I'm using Ubuntu 10.04 Lucid Lynx 64 bit and g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3.