MSGID: 2:280/464.113 5c7df899   
   REPLY: 3:640/1384 5c7dde19   
   TZUTC: -0800   
   RFC-3339: 2019-03-05 04:18:33.859082801+00:00   
   CHRS: UTF-8 4   
   LANG: en_CA.utf8   
   MøøSGID: 2:280/464.113 5c7df899-33349031   
   Hey Paul!   
      
    PQ> Your arguments are wasted on me.   
      
   Probably but then again I saw the need to defend myself so it really doesn't   
   matter ... does it?   
      
    PQ> I don't possess the smarts to decipher the whoosiemahjiggers.   
      
   And yet you seem to know what Maurice thinks about the FTSC and it's rights to   
   creating standards, as well as my opinion and modus operendi as it pertains to   
   all things called standards in this fine and upstanding hobby.  What is the   
   deal with that?   
      
    PQ> Why don't you figure out how to amend the FTS.   
      
   I've tried and may try again in the near future.  It won't take much to   
   rectify the current documentation in question and given they, whoever 'they'   
   were and are, are only one character away from altering a pirated and   
   corrupted standard to make it truly useful.  Heck one might actually believe   
   it is an achievable and honourable goal.   
      
   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?   
      
   Life is good,   
   Maurice   
      
   ... A Møøse once bit my sister ...   
   --- GNU bash, version 5.0.2(1)-release (x86_64-pc-linux-gnu)   
    * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)   
   SEEN-BY: 15/2 18/200 123/1970 154/10 203/0 221/0 226/17 229/107 426   
   SEEN-BY: 229/452 1014 240/5832 249/206 317 400 280/464 5003 310/31   
   SEEN-BY: 317/3 322/757 342/200 393/68 396/45 423/120 633/280 770/1   
   PATH: 280/464 229/426