Hello Bj”rn!   
      
   19 Apr 11 17:07, you wrote to Shawn Highfield:   
      
    SH>> Is it recommended we all add this? Will it cause any issues with   
    SH>> other clients?   
      
    BF>    I for one wouldn't recommend it. It seems to trash the message   
    BF> header in an unnecessary way.   
      
   Care to share an example?   
      
    BF>    This is what my part looks like, and with the unfortunate   
    BF> shortcomings still in JamNNTPd when it comes to marrying UTF-8 with   
    BF> FTN, it so far seems to be optimal. At least to me, and I today seem   
    BF> to be one of a few who have problems with my umlauted name. :)   
      
   Does your post commands below allow UTF-8 posts?   
      
   I admit stabbing in the dark finding the solution that works, but it would   
   also be helpful for an example trashed header to be shown if my solution isnt   
   working.   
      
    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   
    BF> translation 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   
    BF> will use # when no charset was specified. It can be overridden for   
    BF> specific 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   ""   
      
    BF> --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.2.17)   
    BF> Gecko/20110414   
    BF>  * Origin: news://felten.yi.org (2:203/2)   
    BF> 880 1025   
    BF> @PATH: 203/2 0 123/500 456   
      
   ==   
   Ross   
   Fidonet Feeds Or Fidonet In Your Newsreader: http://www.easternstar.info   
   E-mail: ross(at)cassell(dot)us | Other Places: http://links.cassell.us   
      
   Stand Or Fall!   
      
   ... Taxes are the sexual aphrodesiac for every Democrat.   
   --- GoldED+/LNX 1.1.5-b20060121   
    * Origin: The Eastern Star - Spartanburg, SC USA (1:123/456)