On 6/21/2012 10:37 AM, mark lewis -> All wrote:   
   >   
   > i've two messages from the same system created and posted by the same   
   > software... neither carries a CHRS control line... my jamnntpd assumes   
   > these to be CP437 and xlats them to iso-8859-1... however, these two are   
   > translated differently...   
      
   >    Content-Type: text/plain; charset=iso-8859-1; format=flowed   
   >    Content-Transfer-Encoding: 8bit   
      
   > and   
      
   >    Content-Type: text/plain; charset=us-ascii; format=flowed   
   >    Content-Transfer-Encoding: 7bit   
   >   
   >   
   > the first message body DID have some characters above 127 that were xlated   
   > and the second message body was all 7bit ascii... i think there's a bug   
   > because according to my settings, both should have been translated to iso-   
   > 8859-1 when my newsreader requested them...   
   >   
   > or am i missing something?   
      
   No missing anything.  In the code, unless a 8bit character is found, then no   
   translation is executed (saves CPU time for 7bit messages).   
      
   For instance, even though the CHRS for this message will say, UTF-8 2, it   
   doesn't need to be translated as all the characters are indeed standard   
   us-ascii.   
      
   However, see next message.   
      
   ---   
    * Origin: -=[ Space Station Alpha ]=- (1:266/420.0)