I tried iso8859-2 but it's not working correctly... generally, it's nosense to use other code page that OEM 852 because MS Console uses it (and wine implementation too probably). So it would be great upgrade 4 Win coders to use Win console code page .
I gave you enough info; now do some work or shut-up!
Tim S.
don't be this rude... jens mentioned that this is a wxWidgets issue and can't be changed that easy...
@oditoter
There are many good reasons to NOT use the win default code page
And there are twice as much reasons to use utf8 (the windows console is a relict from win16 time, and windows should be forced to implement a new console with utf8...) you can read here some statements:
http://utf8everywhere.org/But that's nonsense. Why have I to use UTF-8, avoid cin & cout, change too many things ...
The nonsense here lays on Microsoft site... If you want code platform independent (as you mentioned earlier) then the easiest way is my approach, and then you have really Unicode support, and not this pseudo implementation from Microsoft... not use cin and cout are the lowest problem you will heave...
BUT if you find some way to set a new codepacge or any other way to successfully use unicode in the windows console, i would really be happy if you can post your solution here!!!!
greetings