REPLY: 1:3634/12.73 5d6c576c   
   MSGID: 1:153/7001 5d6c60d8   
   CHRS: UTF-8 4   
   Hey mark!   
      
    ml> come on, man... geez... we're trying...   
      
   Me too, which is why I've been ignoring the CHRS kludge.  I am criticizing the   
   document and not anyone trying to make it work, although I doubt they can wrt   
   "CHRS: UTF-8 4", which in the past I've advocated removing it from said FTSC   
   document and possibly creating a new one independent from FTS-5003 so that it   
   only covers a UTF-8 capable FTN applications.  Offhand I think it might be far   
   more progressive a strategy.   
      
    ml> an editor written in javascript like many other parts of the BBS   
      
   I noticed the ".js" part and thought that might be the case.  Anyhow your   
   utf-8 characters came across beautifully and I quoted them back making sure   
   they weren't corrupted by the editor I am using.  Seems to me that you're on   
   the right track despite the quoting issues at your end of things which sounds   
   EXACTLY like the issues both msged and golded have with multibyte characters.   
      
   Life is good,   
   Maurice   
      
   ... Don't cry for me I have vi.   
   --- GNU bash, version 5.0.11(1)-release (x86_64-pc-linux-gnu)   
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)   
   SEEN-BY: 1/123 15/2 18/200 57/0 153/757 154/10 203/0 220/70 221/0   
   SEEN-BY: 226/17 227/114 229/354 426 452 1014 240/5832 249/206 317   
   SEEN-BY: 249/400 267/800 280/464 5003 310/31 317/3 322/757 342/200   
   SEEN-BY: 396/45 423/120 633/280 712/848 770/0 1 100 330 340 772/0   
   SEEN-BY: 772/1 210 500   
   PATH: 153/7001 757 770/1 280/464 229/426