TZUTC: -0600   
   PID: JamNNTPd/Win32 1.2.3   
   REPLYADDR ozznixon@gmail.com   
   REPLY: 2:280/464.113 5c7df899   
   MSGID: 1:275/362.0 5c838504   
   On 2019-03-05 04:18:33 +0000, Maurice Kinal -> Paul Quinn said:   
      
   >   
   > Speaking of FTN standards, why is your CHRS kludge using a bogus   
   > setting?  Shouldn't it be "UTF-8 4"?  Also I see no evidence that your   
   > editor can even handle utf8, nevermind type 4 utf8 characters ...   
   > whatever they are.  Do you know?   
      
   Hey Maurice,   
      
   "Level 4 is for multi byte character encodings. The only presently   
    known implementation is UTF-8." .... fts-5003.001   
      
   If NNTPd supported it, I would paste in ExchangeBBS' UTF matrix, which does a   
   full CP437->UTF-8 output for terminals it detects support UTF8. I spent months   
   building it as Wikipedia's CP437 html uses invalid UTF-8 codes to represent   
   the high-bit DOS character set.   
      
   ^ACHRS:     
      
   --- FMail-W32 2.0.1.4   
    * Origin: Modern Pascal, LLC. (1:275/362.0)   
   SEEN-BY: 1/19 15/0 2 16/0 18/200 19/36 34/999 90/1 104/57 116/18 120/544   
   SEEN-BY: 123/130 131 140 1970 153/7715 154/10 203/0 218/700 220/60   
   SEEN-BY: 221/0 1 6 360 222/2 226/17 229/107 426 452 1014 230/0 150   
   SEEN-BY: 230/152 240/1120 5832 249/206 317 400 250/1 261/38 100 1466   
   SEEN-BY: 266/512 267/155 275/0 89 91 93 95 96 98 100 201 362 280/464   
   SEEN-BY: 280/5003 5006 282/1031 1056 291/1 111 310/31 317/3 320/119   
   SEEN-BY: 320/219 322/757 340/400 342/13 200 393/68 396/45 423/120   
   SEEN-BY: 633/280 640/1384 712/848 770/1 801/161 189 2320/105 3634/12   
   SEEN-BY: 5020/715 1042   
   PATH: 275/362 100 261/38 320/219 221/1 280/464 229/426