TZUTC: -0800   
   MSGID: 51818.syncprog@1:103/705 2c1cc22d   
   PID: Synchronet 3.20c-Linux master/64352121b Feb 09 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/4b0ef40fa Feb 16 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: UTF-8 4   
   https://gitlab.synchro.net/main/sbbs/-/commit/7a220e78f18c03f187e0766e   
   Modified Files:   
   	src/xpdev/unicode.c   
   Log Message:   
   CP437 0x7C is UNICODE_BROKEN_BAR (U+00A6)   
      
   Contrary to pouplar belief CP437 does not encode US-ASCII.   
   US-ASCII has UNICODE_VERTICAL_LINE (U+007C) there (which does match   
   Unicode)   
      
   Aren't you glad your C compiler didn't use CP437?   
   if (x ??!??! y) is so much uglier than if (x || y)   
      
   Of course, with C99 (or C90 with the 1995 ammendment), we would have   
   seen a lot of iso646.h and the use of the or, bitor, and or_eq macros,   
   and maybe that would have gotten that whole list of 11 macros promoted   
   to keywords eventually (Likely in C23) since it's hard to eat just one   
   peanut.   
      
   Of course, that's all alternate history... it's unlikely that any   
   compiler vendor would actually care, and | and ¦ (or | and ³ for those   
   using CP437) would be "the same".   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 105/81 106/201 124/5014 5016 128/187 130/330 153/7715 154/110   
   SEEN-BY: 218/700 226/30 227/114 229/110 114 206 317 400 426 428 470   
   SEEN-BY: 229/550 700 705 266/512 280/464 291/111 320/219 322/757 342/200   
   SEEN-BY: 387/18 21 25 396/45 460/58 633/280 712/848 902/26 5075/35   
   PATH: 103/705 280/464 396/45 229/426