Hello, Benny Pedersen.   
   On 10.03.16 20:44 you wrote:   
      
    BP> if utf-8 is enabled it works with unicode senders, no problem    
    BP> there, its just that it changes default aswell for when senders    
    BP> dont add chrs kludge aswell :/ so if one use latin-1 in hotdoged,    
    BP> it will display utf-8 postings as cp437 since it cant decode    
    BP> unicode in iconv there real bug is imho clients leave out chrs    
    BP> kludge not how hotdoged works   
      
   Ftn support realization does not support per-message and per-group encoding   
   right now. That's because of the underlying algorithms used for unpacking pkt   
   files. Actually that's jnode part of code.    
      
   So the only encoding that Hotdoged takes care of at the moment is a codepage   
   in server settings.    
      
   I'm looking forward to fix this but it will take too much refactoring.    
      
   --   
   Best regards!   
   Posted using Hotdoged on Android   
   --- Hotdoged/2.12/Android   
    * Origin: Android device, Milky Way (2:5020/2141.3)