Hello Niels,   
      
   On 12 Nov 12 at 13:06, you wrote to Maxim Sokolsky:   
      
    MS>> UTF-8 conversion works only from one side - to UTF8, not from.   
    MS>> This is currect state of golded in a latest cvs sources. So you   
    MS>> could read messages, but not write.   
      
    NJ> Thanks for the pointer!  In the mean time, I have managed to work   
    NJ> around my problem by setting the gnome-terminal encoding, the LC_CTYPE   
    NJ> environment variable, and all the GoldED XLAT* configuration   
    NJ> parameters to ISO8859-1 / LATIN-1.  This allows me to correctly read   
    NJ> and write messages containing the "special" characters I use myself   
    NJ> (typically latin vowels with accents on them).  With this setup, I   
    NJ> can't read the russian characters you use, but I would probably not   
    NJ> understand them anyway, so perhaps this is as good as it gets. ;-)   
      
   Just an update here. It looks like I can see 3/4 of the characters Maxim used   
   in his tearline and origin line. Right now I'm using _all_ UTF-8 console, with   
   a terminus-font (best for unicode, apparantly). In Golded's config, I have   
   UTF-8 for everything as well.   
      
   This is the only time it has somewhat worked, and I went off Stas's post about   
   using screen to run Golded. That's enough tinkering for tonight. lol   
      
   Regards,   
   Nick   
      
   --- SBBSecho 2.20-Linux   
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)