home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   UTF-8      UTF-8 encoded messages      382 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 130 of 382   
   Michiel van der Vlist to Rob Swindell   
   codepage   
   04 Mar 23 11:00:48   
   
   TID: FMail-W32 2.2.0.0   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 4   
   MSGID: 2:280/5555 640319a0   
   REPLY: 327.fidoutf8@1:103/705 28667e7f   
   Hello Rob,   
      
   On Thursday March 02 2023 17:02, you wrote to me:   
      
    >> All three of your messages have non-ASCCI characters. They all have   
    >> the degree character '°' in the sign off, or whatver you call it.   
    >> In the last message it is also present in the message test before   
    >> the "--" (two dashes).   
      
    RS> Ah, true. But in the message I posted using a UTF-8 terminal, that   
    RS> would have been a UTF-8 encoded "degree" symbol instead of a   
    RS> CP437-encoded one (as would have been in the other messages, including   
    RS> this one).   
      
   The message I am respondig to, is indeed encoded in CP437.   
      
   So let me get this straight:   
      
   1) If the message that is responded to, is encoded in CP437, Synchronet   
   answers in CP437. Yes?   
      
   So what happens if the response does not fit into CP437?   
      
   What happens if the original message is encoded in a one byte encoding other   
   than CP437?   
      
   2) If the message that is responded to is encoded in UTF-8, Synchronet answers   
   in UTF-8 if the terminal theis used supports UTF-8. Yes?   
      
   So what happens in that case if the terminal does not support UTF-8?   
      
    >>  RS> Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15   
    >> inches RS> rain/24hrs   
      
   My software translates the CP437 encoded degree sign into UTF-8 as you can see.   
      
    >> Considering that the CHRS kludge applies to the entire message, I   
    >> think it is more logical to look at the entire message including   
    >> header, footer en origin lines to determine the encoding.   
      
    RS> Synchronet does exactly that.   
      
   OK. :-)   
      
      
   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   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca