On Sun, 04 Aug 2013, Michiel van der Vlist wrote to mark lewis:   
      
    PQ>> The console version is probably still reading Windows'   
    PQ>> setting/configuration.   
      
    MvdV>> The console is set to CP866 as the active code page when golded    
    MvdV>> is started.   
      
    ml> i'd be willing to bet that it is not reading what the current    
    ml> console's code page is set to... like paul said above, it is    
    ml> probably reading the OS's codepage setting and using that...   
      
    MvdV> I am not sure what you mean by the "OS's codepage" in the case of   
    MvdV> WinXP. Windows XP's internally uses unicode.   
      
   i was thinking about the GUI always using a certain codepage whereas the   
   terminal console might be using something else...   
      
    MvdV> The notion of codepages only makes sense in a DOS look alike    
    MvdV> text window or in a text processing application that reads or    
    MvdV> writes files in a specific encoding.   
      
   pretty much true these days...   
      
    MvdV> AFAIK, there is no such thing as the "OS's code page setting" in    
    MvdV> WinXP.   
      
   i haven't dug into the guts in a long time but isn't iso-8859-1 pretty common?   
   yes, unicode is used internally but iso-8859-1 seems to be used for a lot of   
   apps, too...   
      
    ml> i've seen similar during this long transition period of    
    ml> FPC/Lazarus to UTF-8 and the management/usage of codepages... the    
    ml> problem seems to be reading a file in one codepage and then    
    ml> converting it to the local codepage for display...   
      
    MvdV> There is no "local code page for display" in XP. The display is   
    MvdV> unicode.   
      
   that makes sense on the one hand...   
      
    MvdV> Even in a DOS look-alike text window. You can set the   
    MvdV> code page to 866 an it will properly display the cyrillics when   
    MvdV> displaying a text file with the type command when that file is   
    MvdV> encoded in CP866. But type right Alt 5 in the same text window   
    MvdV> and you will see a Euro sign. There is no Euro sign in CP866. The   
    MvdV> display is  not limited to the one byte character set selected   
    MvdV> with the CHCP command. All the characters in the internal unicode   
    MvdV> character set are available for display. I can display a mix of   
    MvdV> cyrillics and umlauted and accented latin characters in the XP   
    MvdV> text window. This impossible in a classic DOS sceen.   
      
   again, true ;) DOS stuff doesn't have the ability to display glyphs from more   
   than one codepage as they appear in those other codepages... as more and more   
   things move to UTF8 or UTF16, DOS may be able to do these things but only when   
   it, too, joins the rest of the UTF family...   
      
   FWIW: i understand that delphi's new versions all use UTF16 internally... at   
   least IIRC recent discussions on the free pascal lists...   
      
    MvdV> Anyway, it seems that Golded's  XLATLOCALSET command does not   
    MvdV> work...    
      
   that would definitely cause problems...   
      
    MvdV> Is it a bug in Golded or am I doing something wrong?   
      
   that i dunno... sorry... hopefully someone else will be able to provide the   
   answer to that...   
      
   )\/(ark   
      
   --- FMail/Win32 1.60   
    * Origin:  (1:3634/12.71)