Hello Niels,   
      
   On 03 Dec 12 at 07:49, you wrote to Robert Bashe:   
      
    NJ> I have experienced this as well.  As far as I can gather, the relevant   
    NJ> settings from the Linux side are:   
      
    NJ>   - The encoding of your current terminal, e.g. gnome-terminal.  I   
    NJ> have this set to Western (ISO-8859-1) - The LC_CTYPE environment   
    NJ> variable.  I have this set to en_US.iso88591, but this locale may need   
    NJ> to be enabled first (e.g., cf.   
    NJ> https://wiki.archlinux.org/index.php/Locale)   
      
    NJ> In GoldED, the relevant configuration options are mentioned in the   
    NJ> "character translation" section of advanced.cfg (which depends on   
    NJ> charsets.cfg, and the charsets dir containing translation files) that   
    NJ> is distributed with at least the sources of golded.   
      
   I have done this over here. Though do you need to define specific XLATCHARSET   
   lines for your operation? Or can you just include the charsets.cfg file?   
      
    NJ> I have good experiences with setting XLATIMPORT, XLATEXPORT, and   
    NJ> XLATLOCALSET to LATIN-1.  Don't know if that includes esszets: I never   
    NJ> encounter one in messages I usually read ;-)  But at least the Dutch   
    NJ> and French "special" characters now work correctly.   
      
   That's also what I've done here. Though it still doesn't seem like I can   
   actually type special letters with alt-codes. If I do, I get a couple extended   
   ascii blocks. "ë"   
      
    NJ> I originally wanted to use UTF-8 for all of these charsets, but that   
    NJ> dit not work out, though people have proposed a workaround for that in   
    NJ> this area a while ago.   
      
   That was the route I was trying, but failed at as well. :)   
      
   Regards,   
   Nick   
      
   --- SBBSecho 2.20-Linux   
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)