Right, Andre :) And I'm always getting slightly into a rant-mode with this :)
A simpler solution would be to agree on UTF-8 - com'on it's almost year 2012, we've landed on the moon, we'll fly to mars soon but we still shall stick to that stoneaged 7bit crap? That's ridiculous!
And yes, a switch to UTF-8 does work. Of course you have to instruct your co-workers. But it's not that much more difficult than instructing them to use 7 bit ASCII only.
Using English for the C++ texts is not always a way to go. You might have a team that targets only domestic use (it may want to translate it to English later on), that would have an additional translation step. You might have developers which are unable to build correct and understandable English texts (look at the forums!). These end up with an hard to understand English text being translated back to their native language - sound weird at best and at worst would lead to babelfish like native texts in the end.
And as a last one catch-all:
Machines have to adapt to man, not the otherwise round.
I'm plainly unwilling to restrict myself (and adding additional, unnecessary work!) only because of 40 year old artifacts that stinking lazy programmers are not willing to change to recent standards.
