• src/xpdev/unicode.c

    From Deucе@VERT to Git commit to main/sbbs/master on Thu Feb 13 13:12:13 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/bcdc57167cc4af52a69f3e9e
    Modified Files:
    src/xpdev/unicode.c
    Log Message:
    Convert UNICODE_VIEWDATA_SQUARE to # for CP437.

    Since we do Mode7

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Wed Feb 19 21:46:43 2025
    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".

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Wed Feb 19 22:47:08 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/469ebb1efa390e2b1e5a7464
    Modified Files:
    src/xpdev/unicode.c
    Log Message:
    Add explicit | to | mapping.

    It's not clear exactly what will happen if I don't, so add it just
    in case.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net