1. Forum
  2. DOVE-Net
  3. Synchronet Programming

  • src/sbbs3/qwktomsg.cpp

    From rswindell@VERT to CVS commit on Saturday, February 16, 2019 20:22:40
    src/sbbs3 qwktomsg.cpp 1.69 1.70
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/home/rswindell/sbbs/src/sbbs3

    Modified Files:
    qwktomsg.cpp
    Log Message:
    Add add_msg_ids() call when creating local msgs from QWK packets.



    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Wednesday, July 31, 2019 22:25:09
    src/sbbs3 qwktomsg.cpp 1.74 1.75
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv1965

    Modified Files:
    qwktomsg.cpp
    Log Message:
    Don't treat 0xE3 as a UTF-8 char unless the message buffer is valid UTF-8.
    This should solve the problem of non-UTF-8 messages posted on non-up-to-date systems (no UTF-8 support), yet the message has a "charset=utf-8" in a MIME content-type header.



    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thursday, April 04, 2024 18:06:02
    https://gitlab.synchro.net/main/sbbs/-/commit/fa91e9074a14a892557b7606
    Modified Files:
    src/sbbs3/qwktomsg.cpp
    Log Message:
    Default FTN charset to CP437 (not ASCII) for QWK-imported messages

    A QWKnet tagline usually contains CP437 character 254 and if/when appended to
    a message during export, would "convert" the message to CP437 thus making the "ASCII" charset advertisement incorrect.

    If a FIDO CHARSET value was already specified (e.g. in HEADERS.DAT), that
    value will (still) not be overridden. So the *original* import via QWK (before it gets exported to a QWKnet) is where this change will take effect.

    Fix for issue #741

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