MSGID: 1:154/10 65f5c0fc   
   REPLY: 2:280/464.113 65f5bcea   
   PID: SmapiNNTPd/Linux 2.2.1   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2024-02-05   
   On Sat, 16 Mar 2024 15:38:18 GMT, Maurice Kinal -> Nicholas Boel wrote:   
      
    MK> I note that you convert them back to utf-8 before replying.  I do the   
    MK> same here except that after replying I convert them back to the   
    MK> supported 8-bit character set, cp866 in this case.  To be honest utf-8   
    MK> for all would be best especially when given bogus information in   
    MK> so-called ftn standards.  Simply shocking methinks.   
      
   I believe this client forces utf-8 when posting, which is fine. The conversion   
   works automatically. I do have other clients for testing purposes that can   
   send it back in CP866, but why?   
      
    MK> For sure.  Someone has to be on the side of what is right and proper.    
   :-)   
      
   Be prepared to be in the fight for the long haul. :)   
      
   Regards,   
   Nick   
      
   ... "Take my advice, I don't use it anyway."   
   --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb   
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016   
   SEEN-BY: 128/260 135/225 153/757 7001 7715 154/10 30 40 50 700 203/0   
   SEEN-BY: 214/22 218/0 1 601 700 820 840 850 860 870 880 930 940 220/90   
   SEEN-BY: 221/0 6 226/18 30 70 227/114 229/110 112 113 206 307 317   
   SEEN-BY: 229/400 426 428 470 664 700 240/1120 5832 266/512 280/464   
   SEEN-BY: 280/5003 282/1038 291/111 292/8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 460/58 467/888 633/280 712/848   
   SEEN-BY: 770/1 2320/105 3634/12 5020/400 5075/35   
   PATH: 154/10 280/464 103/705 218/700 229/426