TID: FMail-W32 2.2.0.0   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 4   
   MSGID: 2:280/5555 640651dc   
   REPLY: 331.fidoutf8@1:103/705 286a2761   
   Hello Rob,   
      
   On Sunday March 05 2023 11:40, you wrote to me:   
      
    >> I see... So it is the terminal - or whatever functions as its   
    >> equivalent - and only the terminal that determines the encoding of the   
    >> message at hand.   
      
    RS> Or rather, the message content created with that terminal. If the   
    RS> content is just plain ASCII, regardless of the terminal that created   
    RS> it, then the message will fly the ASCII charset flag. In Synchronet, a   
    RS> CP437 terminal cannot be used to created UTF-8 content, so messages   
    RS> created by such a terminal will either be ASCII or CP437 encoded.   
      
   Understood.   
      
    >>  RS> The only encodings Synchronet supports for message text are   
    >>  RS> ASCII, CP437, and UTF-8.   
    >>   
    >> Hmmm... That leaves out a big part of Fidonet. These days the   
    >> majority, maybe the vast majority is writen in a language that uses   
    >> the Cyrillic alfabet and the encoding is CP866.   
      
    RS> True, that's the state of things.   
      
   Well, at least those needing more that CP437 can use UTF-8.   
      
    >>  >> So what happens in that case if the terminal does not support   
    >>  >> UTF-8?   
    >>   
    >>  RS> The message text would be converted to CP437 before being   
    >>  RS> quoted and the response would be in CP437.   
    >>   
    >> And now I come back to my previous question: what happens if it   
    >> does not fit into CP437? That can easely happen. A Euro sign '¿'   
    >> can be composed in UTF-8 but it  does not fit into CP437.   
      
   I see that the EURO sign is translated into an inverted question mark.   
      
    RS> When a CP437 terminal user quotes a UTF-8 message that contains   
    RS> untranslatable UNICODE codepoints without a CP437 equivalent, they're   
    RS> translated to character that indiciates it was untranslatable. By   
    RS> default, that character is the upside down question mark.   
      
   Check.   
      
   Next question: Can Synchonet deal with a UTF-8 encoded nodelist?   
      
   Here is where to find one: http://www.vlist.eu/downloads/fidolist/z2daily.065   
      
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: Nieuw Schnøørd (2:280/5555)   
   SEEN-BY: 106/201 114/705 123/120 153/7715 154/10 203/0 218/700 840   
   SEEN-BY: 220/70 221/6 226/17 30 227/114 229/111 112 113 307 317 426   
   SEEN-BY: 229/428 470 700 240/5832 250/5 8 267/800 280/464 5003 5555   
   SEEN-BY: 298/25 301/1 305/3 310/31 317/3 320/219 341/66 410/9 460/58   
   SEEN-BY: 712/848 770/1 100 340 772/210 220 230 5019/40 5020/1042 12000   
   PATH: 280/5555 310/31 770/1 317/3 229/426