MSGID: 2:230/0 5f7c7bc2   
   TZUTC: 0000   
   REPLY: 2:240/77 5f7b39ce   
   CHRS: LATIN-1 2   
   TID: hpt/lnx 1.9.0-cur 17-02-17   
   Hello Kai!   
      
   05 Oct 2020 17:03, Kai Richter wrote to Benny Pedersen:   
      
    KR> Guys, what kind of problem are you talking about??   
      
   none   
      
   if its all 7 bit there is just diffrent parsing of 7 bit   
      
    KR> If you code all humans writing symbols to HTML you will have the same    
    KR> situation like now.   
      
   so you know json ?   
      
    KR> HTML will need multiple bytes to define a symbol.   
      
   same as unicode when its 8 bit charters    
       
    KR> No matter if the HTML charset will be limited to 7 bit or not,   
      
   ?, i have seen UTF-8 and QP combined badly in lots of emails where programmers   
   dont understand double encodeing problems, QP hide 8 bit chatters, so UTF-8   
   dont know it needs to be unicode encoded, thats not how it should be, since   
   the reader does not know if sender send from what charset :/   
      
    KR> the software must know which symbol have to be displayed for that    
    KR> multibyte sequence.   
      
   and unicode solve that much better then html, hmm   
      
      
    Regards Benny   
      
   ... there can only be one way of life, and it works :)   
      
   --- Msged/LNX 6.1.2 (Linux/5.8.13-gentoo-x86_64 (x86_64))   
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)   
   SEEN-BY: 1/123 90/1 120/340 123/131 226/30 227/114 702 229/101 424   
   SEEN-BY: 229/426 452 550 616 664 1016 240/5832 249/206 317 400 292/854   
   SEEN-BY: 317/3 322/757 342/200 633/280   
   PATH: 230/0 203/0 280/464 229/101 426