From: miles@gnu.org   
      
   "Alf P. Steinbach"  writes:   
   > For example, Visual C++ has (unfortunately undocumented) Windows   
   > ANSI as its narrow character execution character set, and UTF-16 as   
   > its wide character execution character set.   
      
   Worse, this seems to be location-dependent...   
      
   I work in a Japanese company; we use both VS and gcc, and want   
   Japanese in strings etc... we eventually settled on using Shift-JIS   
   because it's the only thing Japanese versions of VS support sanely   
   while maintaining portability to non-MS compilers (and gcc can just be   
   told what character set to use with an option).   
      
   VS's handling of UTF-8, in particular, is a complete clusterf*ck -- it   
   _will not_ accept it without a BOM -- and a BOM makes a source-file   
   unusable with other compilers...   
      
   [I use the term "VS" a bit loosely here -- VS and VC++ both have their   
   own idea of what's going on, and various settings affect one but not   
   the other; IIRC, we could get UTF-8 to work with VC++, but not with VS   
   itself... or maybe it was vice-versa...]   
      
   -Miles   
      
   --   
   Joy, n. An emotion variously excited, but in its highest degree arising from   
   the contemplation of grief in another.   
      
      
         [ 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)