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 291 of 382   
   Nicholas Boel to Michiel van der Vlist   
   UTF-8 nodelist report   
   11 Mar 25 17:56:12   
   
   REPLY: 2:280/5555 67d02060   
   MSGID: 1:154/10 67d0c430   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2024-03-02   
   Hey Michiel!   
      
   On Tue, 11 Mar 2025 12:10:08 +0100, you wrote:   
      
    > How was that before the computer age? How is it written on your birth   
    > certificate? Your father's?   
      
   You sparked my interest, so I dug it up from the bottom of a drawer in my   
   bedroom, and no. None of the names on my birth certificate have it (they all   
   look to be typed with a typewriter), except for my mother's signature. :)   
      
    > Done. You should receive the next dailyutf tomorrow. (Later today for   
    > you)   
      
   Thanks!   
      
    >> @PATH: 154/10 280/5555   
      
   Perfect. I guess I never turned that off, either. I just set up another link   
   to it at some point when your system went down.   
      
    > So you could be the first...   
      
   Maybe. If I can figure out a good way to send it up the chain of clerks. :)   
      
    > 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. ;-)   
      
   Noted.   
      
    > If Z1C does not want to cooperate we have to look for other ways to get   
    > your UTF region segment into the DAILYUTF.   
      
   I'll see what happens, I suppose.   
      
    > 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.   
      
   Understood. Here it still looks like it is CP437.   
      
    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   
    NB>> as the default (which is a good thing, IMO).   
      
    > Also for he CLI? That is relevant since most Fidonet sowwtare is still   
    > CLI based.   
      
   Mainly for the CLI, yes. And that is why I chose what I did so that most, if   
   not all of my CLI based Fidonet software works with UTF-8 and IPv6. If it   
   didn't at first, it definitely does now! ;)   
      
   Regards,   
   Nick   
      
   ... Sarcasm: because beating people up is illegal.   
   --- GoldED+/LNX 1.1.5-b20240309   
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)   
   SEEN-BY: 4/0 90/0 104/119 105/81 106/201 124/5016 128/187 153/757   
   SEEN-BY: 153/7715 154/10 30 50 110 700 701 203/0 218/700 220/20 221/0   
   SEEN-BY: 221/6 226/30 44 50 227/114 229/110 114 310 317 426 428 470   
   SEEN-BY: 229/700 705 240/1120 5832 280/464 5003 5006 5555 291/111   
   SEEN-BY: 292/854 8125 301/1 310/31 320/219 341/66 234 423/120 460/58   
   SEEN-BY: 467/888 712/848 770/1 900/0 902/0 26 905/0 5020/400   
   PATH: 154/10 280/464 341/66 902/26 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca