Bj”rn Felten -> Shawn Highfield <2:203/2> wrote in   
   news:179$fido.jamnntpd@JamNNTPd:   
      
   yes, this is a reply to an old message... i was reading back to see what i   
   could find about the utf-8 stuff and how to configure it...   
      
   your file is a lot different than mine...   
      
   did you have to copy the chs files from the unicode/xlat directory to the   
   xlat directory?   
      
   can you do both utf and iso at the same time?   
      
   will it hurt anything to have both sets of chs files in the xlat directory?   
      
   i don't see utf to other character set files... do you know why?   
      
   i note that you are not using the -keepsoftcr option on your "read 866"   
   line... any paricular reason?   
      
   do i have an older or newer default xlat.cfg file than you or is yours   
   highly modified?   
      
   i don't understand the differences between my xlat.cfg and the one you   
   posted below :?   
      
    BF> = = = = = =   
      
    BF> # Syntax: read [,]     
    BF> #   
    BF> # Here you can configure the charset translations to be used when   
    BF> reading # messages. CHRS and CODEPAGE are taken from the respective   
    BF> kludge lines. # If you omit the xlat file, no actual charset translation   
    BF> will take place.   
      
    BF> read CP437      iso-8859-1    437_iso.chs   
    BF> read CP850      iso-8859-1    850_iso.chs   
    BF> read CP865      iso-8859-1    865_iso.chs   
    BF> readalias UKR       CP866   
    BF> readalias FIDO,2    CP866   
    BF> readalias +7        CP866   
    BF> read CP866      koi8-r        866_koi.chs   
    BF> read IBMPC,850  iso-8859-1    850_iso.chs   
    BF> read IBMPC,865  iso-8859-1    865_iso.chs   
    BF> read IBMPC      iso-8859-1    437_iso.chs   
    BF> read LATIN-1    iso-8859-1   
    BF> read UTF-8      utf-8   
    BF> read *          unknown-8bit   
      
    BF> # Charset translations when posting messages   
      
    BF> # The charset specified with "defaultread" is the charset JamNNTPd will   
    BF> use # when no charset was specified. It can be overridden for specific   
    BF> areas in # the jamnntpd.groups config file.   
      
    BF> defaultpost iso-8859-1   
      
    BF> # Syntax: read      
    BF> #   
    BF> # Here you can configure the charset translations to be used when   
    BF> posting # messages. If you don't want to create CHRS kludges, enter ""   
    BF> as CHRS. # You should have "read" translations set up for all charsets   
    BF> you accept or # the receiver name of the posts migth not be translated   
    BF> properly.   
      
    BF> #post iso-8859-1 LATIN-1   
    BF> post iso-8859-1 IBMPC         iso_437.chs   
    BF> post koi8-r     CP866         koi_866.chs   
    BF> post utf-8      UTF-8   
    BF> post us-ascii   ""   
      
   )\/(ark   
      
    * Origin: news://news.wpusa.dynip.com | acct reqd to post (1:3634/12)