TID: FMail-W32 2.3.0.1-B20240319   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 4   
   MSGID: 2:280/5555 67d02060   
   REPLY: 1:154/10 67cf7cdd   
   Hello Nicholas,   
      
   On Monday March 10 2025 18:28, you wrote to me:   
      
    >> Then again here in The Netherlands we are used to dealing with   
    >> accents and diaresis. They are part of our language.   
      
    NB> Very true, and it's the complete opposite here. Not only my name, but   
    NB> I've seen plenty of words that should have an accent or diaeresis and   
    NB> is quite often typed without.   
      
   How was that before the computer age? How is it written on your birth   
   certificate? Your father's?   
      
   [..]   
      
    NB>>> I also believe I was getting the DAILYUTF from you at some   
    NB>>> point, but possibly when your system went down, and stayed down   
    NB>>> for some time, it was stopped for some reason (I don't think I   
    NB>>> ever turned it off).   
      
    >> You want me to turn it on again?   
      
    NB> Sure, please. I still have all the same config in place here to   
    NB> receive it.   
      
   Done. You should receive the next dailyutf tomorrow. (Later today for you)   
      
    NB> I believe I was also receiving this echo from you before you went down   
    NB> as well. It doesn't look like I paused or disabled anything with our   
    NB> link (I just linked with someone else at the time), so it must have   
    NB> stopped at your end when you reconfigured.   
      
    > PATH: 154/10 280/5555   
      
   Hmmm....   
      
    >> At the moment no one in Z1 participates in de dailyutf,   
      
    NB> That's a bummer. I figured Andrew, at the very least, would have been   
    NB> interested.. as he was the only one from Z1 that jumped on the IPV6   
    NB> bandwagon before I did.   
      
   So you could be the first...   
      
    >> Yes. When I was RC I also did it. It is not hard, the UTF part is   
    >> mostly a copy of the ASCII setup. Except for the file names and the   
    >> ALLOW8BIT setting.   
      
    NB> Got it. I'll take a look at it when I have some free time this   
    NB> weekend.   
      
   Naming conventions here in Z2 for Region and net segments are UTFRxx and   
   UTFNyyy. You can follow that or - as you would be the first in Z1 - create you   
   own naming scheme. ;-)   
      
   After you have created UTFR11.xyz the next logical step would be to persuade   
   your ZC to also set it up for Z1 to create an UTFZ1 and send that to Ward to   
   incorpoate it into the DAILYUTF. A little bird tells me that it will be better   
   it I stay out of that part of the process.   
      
   If Z1C does not want to cooperate we have to look for other ways to get your   
   UTF region segment into the DAILYUTF.   
      
    >> No. Here in Western Europe the default code page for DOS was 850.   
    >> That is still the case in the Windows CLI. In the Linux community   
    >> Latin-1 is popular.   
      
    NB> I think most of my Windows applications are now either ISO8859-1 or   
    NB> UTF-8. But I'm on Windows 11, so it probably started to change some   
    NB> time ago.   
      
   There is a difference between Windows in general and the Windows Command Line   
   Inerface. In the CLI of Windows 10, the default is still CP850.   
      
    NB>  As for Linux, ISO-8859-1 may have been popular at some   
    NB> point, but these days most distributions are installed with UTF-8 as   
    NB> the default (which is a good thing, IMO).   
      
   Also for he CLI? That is relevant since most Fidonet sowwtare is still CLI   
   based.   
      
    >> ASCII is a subset of nearly all charactersets in use, with the   
    >> exception of the obsolete national 7 bit character sets.   
      
    NB> I imagine we probably won't see much of those national 7 bit sets any   
    NB> more, unless someone comes online with some very vintage hardware. ;)   
      
   I for one have not seen any of it for over a quarter of a century. That's why   
   I labelled them as "obsolete".   
      
    >> I recall Björn mentioning that is is Latin-1. But does it mnatter?   
    >> The point is that it is NOT UTF-8 and therefore an error in he UTF   
    >> nodelist.   
      
    NB> True, and let's not forget that it's an error in the original   
    NB> nodelist, as well.   
      
   Indeed.   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: Nieuw Schnøørd (2:280/5555)   
   SEEN-BY: 4/0 90/0 105/81 106/201 128/187 153/7715 154/10 110 203/0   
   SEEN-BY: 218/700 221/6 226/30 227/114 229/110 114 317 426 428 470   
   SEEN-BY: 229/700 705 240/5832 280/464 5555 291/111 292/789 301/1 310/31   
   SEEN-BY: 320/219 341/66 234 460/58 900/0 902/0 26 905/0 5019/40 5020/1042   
   SEEN-BY: 5075/35   
   PATH: 280/5555 341/66 902/26 229/426