TID: FMail-W32 2.3.0.1-B20240319   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 4   
   MSGID: 2:280/5555 67cdcb8d   
   REPLY: 1:154/10 67cd954c   
   Hello Nicholas,   
      
   On Sunday March 09 2025 08:13, you wrote to me:   
      
    >> Nah, as far as the nodelist goes, it is either just ASCII or UTF-8.   
    >> No more codepage shit.   
      
    NB> Agreed.   
      
   Thank you.   
      
   My notoriously unreliable memory tells me that you name should actually be   
   spelled "Boël" with two dots on the 'e'. Is that correct?   
      
    NB> As an aside, one could simply run the UTF-8 generated nodelist through   
    NB> a conversion utility (like iconv or similar) to ensure that it is   
    NB> proper UTF-8, before being distributed to the rest of the world,   
    NB> rather than having a weekly report that shows an error that you say   
    NB> will most likely never be fixed (due to someone being stubborn and/or   
    NB> proud that they are the one creating the error on purpose?).   
      
   This particular problem could indeed be easely fixed at the ZC's side. But it   
   should not be needed. Plus that it is hard to fight against someone knwowingly   
   and willingly looking for loopholes to derail the system. If this particular   
   loophole were blocked it could easely turn into an arms race that benefits no   
   one. The weekly error may be the lesser evil...   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: Nieuw Schnøørd (2:280/5555)   
   SEEN-BY: 1/19 16/0 19/37 105/81 106/201 123/130 128/187 142/104 153/7715   
   SEEN-BY: 154/10 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/317 426 428 470 700 705 240/2411 5824 5832 5853 5854   
   SEEN-BY: 280/464 5555 291/111 292/789 301/1 310/31 320/119 219 319   
   SEEN-BY: 320/2119 322/762 341/66 460/58 902/26 5019/40 5020/1042 5075/35   
   PATH: 280/5555 240/5832 320/219 229/426