TID: FMail-W32 2.2.0.0   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 4   
   MSGID: 2:280/5555 63ff158a   
   REPLY: 323.fidoutf8@1:103/705 28628892   
   Hello Chris,   
      
   On Tuesday February 28 2023 01:54, you wrote to me:   
      
    MvV>> Other than that: my comment was on Chris' message that was a   
    MvV>> quote-reply to my message. He quoted the UTF-8 encoded text but   
    MvV>> the reply was in CP437 thereby messing up the quote.   
      
    CJ> Your message was not entirely UTF-8. It contained a legacy ö   
    CJ> That caused Notepad Kladblok to interpret all of it as legacy.   
      
   Ah yes.. If there is just ONE byte with bit 7 set that is not part of a well   
   formed UTF-8 string, the entire text is considered legacy encoded. Notepad is   
   very strict in that. And it isn't the only one. Winvi does the same.   
   Fortunately the manual overrride to UTF-8 in Winvi is just one mouse click   
   away.   
      
   Still... when used for Fidonet I say this behaviour is too stricht. The "CHRS   
   UTF-8 ?" in the quoted message should be leading IMNSHO. If the quoted message   
   is in UTF, the respons should also be in UTF whenever possible. Even if the   
   quoted message contains a few bytes legacy encoding.   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: Nieuw Schnøørd (2:280/5555)   
   SEEN-BY: 106/201 114/705 123/120 124/5016 153/757 7715 154/10 203/0   
   SEEN-BY: 218/700 840 220/70 221/0 6 226/17 30 227/114 229/111 112   
   SEEN-BY: 229/113 307 317 426 428 470 700 240/1120 5832 250/5 8 267/800   
   SEEN-BY: 280/464 5003 5555 292/854 8125 298/25 301/1 305/3 310/31   
   SEEN-BY: 317/3 320/219 341/66 234 410/9 423/120 460/58 712/848 770/1   
   SEEN-BY: 770/100 340 772/210 220 230 5019/40 5020/1042 12000   
   PATH: 280/5555 464 770/1 317/3 229/426