ml> and cannot be fixed unless jamnntpd resends the post with a new   
    ml> character set control line :?   
      
    PQ> Maybe change the "defaultread []" setting in your ~xlat   
    PQ> file?  Try CP850.  I'm thinking about changing it too, to that.   
      
   i don't think that will work... why?   
      
   # The charset specified with "defaultread" is the charset JamNNTPd will use   
   # when no charset was specified in the CHRS and CODEPAGE lines. If you enter   
      
   there are CHRS control lines in those posts so the defaultread won't effect   
   them unless i force it and that would be even worse...   
      
   i've added the following section above my existing iso block in my xlat.cfg...   
   now it looks like the one in the unicode directory in the sources...   
      
   ## this section added to try utf-8 translations   
   read CP437      utf-8         437_utf.chs   
   read CP850      utf-8         850_utf.chs   
   read CP865      utf-8         865_utf.chs   
   read CP866      utf-8         866_utf.chs   
   read LATIN-1    utf-8         iso_utf.chs   
   ## end of addition...   
      
      
   and something i have to keep telling myself to try to avoid confusion is that   
   i'm currently doing this with jamnntpd but my timed reader also has similar   
   capabilities and i believe it even uses the same chs files :)   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)