I am pretty aware that there are big problems with internalization and unicode in the language, and std::string and std::wstring. Nevertheless, of the possible alternatives, wstrings work better with...
Type: Posts; User: Elysia
I am pretty aware that there are big problems with internalization and unicode in the language, and std::string and std::wstring. Nevertheless, of the possible alternatives, wstrings work better with...
Since std::string works with char, it means you cannot iterate a utf-8 string since it will always move one byte at a time. Furthermore, any string operations on string will be unlikely to work since...
Because it causes problems! Alla non-english characters cannot be represented by ANSI. It would rely on non-standard extended character set which tends to be different for each language of Windows....
Come now, it's a plea, not a demand. But correct me if I'm wrong, I don't think std::string works very well with utf-8.
At least it allows you to work internationally natively without extra libraries. Or at least hopefully. It works so-so on Windows.
And the fact that std::string would probably not be very good for...
Please make that std::wstring at the very least. It's time to dump ANSI.
Hopefully the next standard should clear some of this mess up.
Don't use C-style strings unless you have a good reason, please. No need to feed that into the fire unless we are sure it's needed.
IOW, don't mention C-style stuff unless we are certain the OP...
That seems unlikely. Best use proper strings:
std::map<std::wstring, blah>