MSGID: 1:275/362.0 5CE846AC   
   REPLY: 1:229/452 3A842B10   
   PID: PCBoard/16ml   
   TID: ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09)   
   > MK> Here are 4 utf8 characters that all contain a trailing 0x81 byte:   
   > MK> Ã� Ð� Ñ� Ó�   
   >   
   > MK> These 4 all contain a trailing 0x83 byte:   
   > MK> Ã σ Ѓ у   
   >   
   > MK> These 4 all contain a trailing 0x88 byte:   
   > MK> È ψ Ј ш   
   >   
   > MK> These 4 all contain a trailing 0x8d byte:   
   > MK> Ã Ï Ð Ñ   
   >   
   > MK> Ã� Ä� Ð� Ñ�   
   >   
   > MK> These 4 all contain a trailing 0x90 byte:   
   > MK> Ã� Å� Ð� Ñ�   
   >   
   > MK> These 4 all contain a trailing 0x98 byte:   
   > MK> Ø Ř И ј   
   >   
   > MK> Finally, these 4 all contain a trailing 0x9d byte:   
   > MK> Ã� Å� Ð� Ñ�   
       
   Sorry for the dela on this thread - still int he process of moving to   
   Florida. Anyway, what I see in Unison NNTP Client are the UTF8 A I D N   
   or A I D O characters as it should have been. However, in PCBoard 16, I   
   see the CP437 8bit character plus the character your trailing each line   
   with. My PCBoard terminal (fTelnet) would render the UTF8, however, the   
   header did not contain ^aCHRS: UTF8 so it assumes to stay in the   
   current state (CP437 as detected during the ANSI detection routine).   
       
   So, some environments render the UTF8 w/o the required CHRS signature.   
       
   Ozz   
   --- ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09)   
    * Origin:  (1:1/123)   
   SEEN-BY: 15/2 18/200 226/17 229/123 354 426 452 1014 240/5832 249/206   
   SEEN-BY: 249/317 400 280/464 317/3 322/757 342/200 393/68 633/280   
   PATH: 1/123 229/426