Hello Paul,   
      
   On 15 Dec 12 at 15:29, you wrote to me:   
      
    PQ> Hi! Nicholas,   
      
    PQ> In a message to Stas Degteff you wrote:   
      
    NB>> @PID: GED+LNX 1.1.5-b20120826   
    NB>> @TID: SBBSecho 2.20-Linux r1.216 Nov 22 2012 GCC 4.5.4   
      
    NB>> @CHRS: LATIN-1 2   
      
    NB>> Compile went great, I'll let you know if I see anything wierd. So   
    NB>> far everything seems to be working the way it should. :)   
      
    PQ> So far, so good.  (Too good!  I'm envious. :)   
      
   Well, it seems the issue I explained before is still happening, though it only   
   seems to happen in echoes not related to fidonet (othernets), and only about   
   5-7 out of about 300 echoes total. So I wouldn't have a clue as to where to   
   try and pinpoint the issue, but I can nose around for a bit when I have some   
   free time.   
      
   Did I mention I can view most, if not all, encodings now? I use Konsole from   
   my desktop (which is a complete UTF-8 system with support for other encodings)   
   to ssh over to my server machine (where Golded is setup to use LATIN-1, while   
   loading charsets.cfg (the complete collection, not just a few lines). From   
   here I can click "View > Set Encodings > {insert random encoding}" and view   
   the messages as they were originally typed. I can view the Russian text in   
   Maxim's tearline and origin line by switching to CP866. I can see all European   
   characters with ISO-8859-1. I can see ANSI symbols with CP850, though I would   
   like to get CP437 working, but that seems to be the one encoding I'm missing   
   in Konsole at the moment.   
      
   I'm not using screen or luit either. I'm quite impressed!   
      
   Regards,   
   Nick   
   --- SBBSecho 2.20-Linux   
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)