TID: Mystic BBS 1.12 A47   
   MSGID: 1:120/616 2e91eabd   
   REPLY: 1:154/10 654abe48   
   TZUTC: -0500   
   On 07 Nov 2023, Nicholas Boel said the following...   
       
    NB> 2) Is this where iconv support would be beneficial, when an incoming   
    NB> message has a CP866 kludge, iconv would translate it to UTF-8 on my end   
    NB> so that it is readable and writable, and then translate it back to CP866   
    NB> when the reply is sent? Or would it still stay UTF-8 because I'm forcing   
    NB> it on export?   
      
   this is exactly how it works in the IRC client i use. default is UTF-8   
   internally, and on input from user, but you can set server, channel, nickname   
   level with personalized encoding.   
      
   http://epicsol.org/encoding   
      
   it's nice that the fido message has a hint, but if it's wrong, or you know a   
   whole ftn is in russian for example, it would be useful to set that whole net   
   or a specific person that is misconfigured to default to what you want instead.   
      
   --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)   
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)   
   SEEN-BY: 1/19 123 15/0 16/0 18/200 19/10 37 90/1 103/705 105/81 106/201   
   SEEN-BY: 120/616 123/10 130 131 124/5016 129/305 142/104 153/757 7715   
   SEEN-BY: 154/10 30 40 50 700 203/0 218/700 220/90 221/0 1 6 360 226/18   
   SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 400 426 428 452   
   SEEN-BY: 229/470 664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038   
   SEEN-BY: 291/111 292/854 8125 301/1 305/3 310/31 317/3 320/119 219   
   SEEN-BY: 320/319 2119 322/0 757 326/101 341/66 234 342/200 396/45   
   SEEN-BY: 423/81 120 460/58 633/280 712/848 770/1 2320/105 3634/12   
   SEEN-BY: 5020/400   
   PATH: 120/616 154/10 280/464 221/1 320/219 229/426