From: 0xCDCDCDCD@gmx.at   
      
   On 14.11.2011 08:19, Miles Bader wrote:   
   > "Alf P. Steinbach"  writes:   
   >> So it's almost as if the C++ standardization sent a signal to the   
   >> OS-folks, both Windows and *nix: hey, wake up, start using UTF-8! And   
   >> within 5 years this happened in the Linux world, while for Windows not   
   >> even the bugs that prevents use of UTF-8, were fixed (the most amazing   
   >> such: try "chcp 65001" and then "more" in a console (SNAFU)).   
   >   
   > I can't help but think this is intentional to some degree:  MS has   
   > invested a huge amount of time and effort in their clunky half-assed   
   > non-portable UTF-16 infrastructure, and probably doesn't really _want_   
   > people to start using a more portable and functional UTF-8-based   
   > solution instead -- even though doing so would probably be better for   
   > users/developers.   
   >   
      
   I'm left scratching my head inhowfar implied wchar_t*===UTF-16 is any   
   worse that char*===UTF-8 ?   
      
   cheers,   
   Martin   
      
   --   
   I'm here to learn, you know.   
   Just waiting for someone,   
   to jump from the shadows,   
   telling me why I'm wrong.   
      
      
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)