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.

   TUXPOWER      Advocacy for the Linux operating system      1,237 messages   

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

   Message 993 of 1,237   
   Nick Boel to Maurice Kinal   
   Re: 40 Cups of Coffee   
   05 Apr 25 23:27:02   
   
   TZUTC: -0500   
   MSGID: 336.tuxpower@1:154/700 2c5739e6   
   REPLY: 1:153/7001 67f1eaf4   
   PID: Synchronet 3.21a-Linux master/e2e350d1d Apr 04 2025 GCC 14.2.1   
   TID: SBBSecho 3.24-Linux master/e2e350d1d Apr 04 2025 GCC 14.2.1   
   BBSID: PHARCYDE   
   CHRS: UTF-8 4   
   NOTE: slrn/pre1.0.4-9 (Linux)   
   Hey Maurice!   
      
   On Fri, Apr 06 1900 20:46:12 -0600, you wrote:   
      
    > It's varied over the last year from internal bleeding to potential    
    > cancerous polyps.  The latest scan (ultrasound) showed a polyp on my    
    > gall bladder which will need to be checked out.  So far anything    
    > they've found has proved to be benign or cauterized in the case of    
    > internal bleeding.  No real fix yet and I have to get blood    
    > transfusions far too often.  :-(   
      
   Are the transfusions for blood loss, or that it's not getting filtered   
   properly? I take it they've already looked at your liver and kidneys?   
      
    > Whoa!  Seems to me that they were recommending UTF-8 adoption further    
    > back than 2019.  Not having anything to do with MS products I can    
    > only account for what I've heard through the grapevine over the    
    > years.   
      
   Seems as though it has always been UTF-16 after UCS 2, although since WinXP   
   they introduced code page 65001, which was designated for UTF-8.. so maybe   
   that's about the time the issues started to decrease. It wasn't until 2019   
   that MS started recommending programmers use UTF-8, and only now in Windows 11   
   some system files are required to use UTF-8 and do not require a Byte Order   
   Mark. Seems as though they had slapped in a workaround back in 2005-ish, and   
   hadn't really done anything about it for some 14 years, or so.   
      
   Regards,   
   Nick   
      
   ... Sarcasm: because beating people up is illegal.   
   --- SBBSecho 3.24-Linux   
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)   
   SEEN-BY: 19/25 105/81 106/201 987 124/5014 5016 128/187 153/7715 154/110   
   SEEN-BY: 218/700 226/30 227/114 229/110 114 206 300 317 400 426 428   
   SEEN-BY: 229/470 664 700 705 266/512 280/464 291/111 320/219 322/757   
   SEEN-BY: 342/200 387/18 25 396/45 460/58 633/280 712/848 902/26 5075/35   
   PATH: 154/700 10 280/464 396/45 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca